Open source

We take from the commons, so we give back.

Much of what we run was written by other people and shared freely. When we improve it, we publish the changes, credit the people who started it, and keep our forks close to the original.

Our forks What the community gets

Our forks

Three projects we maintain in public

Fork of Documenso · AGPL-3.0

Documenso fork

Signing with a key that never leaves the vault.

We run Documenso at sign.tdpdf.com. Our fork adds a signing transport for Azure Key Vault, so the private key stays inside a hardware security module. Sealed PDFs carry RFC 3161 timestamps and validate in Adobe Acrobat. It also fixes sealed field values that landed in the wrong place on pages with an offset box.

For the community: The patches, the build script, the Docker Compose stack and the backup runbook are all published. Read them, reuse them, or run your own copy.

View Documenso fork on GitHub

Fork of PocketBase · MIT

PocketBase fork

Passkey sign-in for PocketBase.

Our fork adds WebAuthn passkeys as a first-class sign-in method, next to password, OAuth2 and one-time codes. It also gives teams a practical path to run PocketBase in Docker and on Azure Container Apps.

For the community: We keep the changes small and stay close to upstream, so the fork follows each new PocketBase release.

View PocketBase fork on GitHub

Fork of KillerPDF by SteveTheKiller · GPL-3.0

TDPdf

A PDF editor anyone can inspect.

TDPdf began as a fork of KillerPDF. Credit for the original design and code belongs to its author, and our notice lists every change we made.

For the community: The full source is public, so you can see that the redaction really removes what it says it removes.

View TDPdf on GitHub

The community benefit

What you get from open work

You can check our work

The code is public. A claim about redaction, signing or sign-in is something you can read and test, not something you have to take on trust.

You can reuse it

Every fork keeps its original licence. Take a patch, copy a deploy recipe or run your own copy of the whole stack.

Your data stays yours

Self-hostable tools mean you can leave. You are not locked in to us, or to anyone else.

Credit goes to the authors

We name the projects we forked, keep their notices and say what we changed.

Build something better with us

We run and support these tools for people who would rather not. Ask us how.

Email us All our software