Self-host DocKosha with the source in your hands

What you need

Node.js 24.x, pnpm 11.25.0, Supabase for Postgres and authentication, S3-compatible object storage, and SMTP. Local development also needs Docker with Compose and the Supabase CLI. The repository Compose file starts local object storage; it is not a production app installer.

DocYantra 0.0.28 runs inside the application as Rust and WebAssembly packages. There is no separate document-processing server or fallback converter. GitHub Packages requires an expiring classic GitHub token with read:packages access, even for public packages. Store that token in user-level npm configuration or a CI secret.

From source to your first shared document

1. 1. Install the application

   Clone DocKosha, configure GitHub Packages authentication, and install with pnpm install --frozen-lockfile. Copy env.example to your private local environment file.

2. 2. Prepare the services

   Start local Supabase and MinIO with Docker, or provision your own production Supabase project and S3-compatible bucket. Apply the repository migrations to your own database.

3. 3. Configure access and email

   Set your app origin, Supabase keys, storage credentials, SMTP, sender addresses, and independent cookie secrets. Configure Auth redirect URLs and optional Google sign-in.

4. 4. Run and verify

   Start locally with pnpm dev. For production, build, verify the engine bundle, and run behind HTTPS. Sign in, upload a synthetic PDF, share a gated link, and test revocation and watermarking.

Exact commands and configuration are in the repository setup walkthrough, also published in the public documentation.

Your deployment, your operations

Self-hosting is not officially supported. You manage migrations, storage permissions and CORS, email delivery, secrets, HTTPS, monitoring, security updates, backups, and tested restores. Community help is best effort and has no SLA. Existing application plan rules still apply; an open-source license is separate from Cloud pricing.

Supported conversion depends on DocYantra’s documented envelope. Failed preview conversion leaves the original file available; required watermarking failures block delivery. Custom domains need additional Cloudflare infrastructure. Optional billing and analytics services need your own configuration.

Compare Cloud and self-hosting

Inspect both repositories

• DocKosha on GitHub — application, sharing controls, and operator docs.
• DocYantra on GitHub — PDF and Office engines and package source.
• DocYantra deployment guide — embedding, offline fonts, and source builds.

Both projects use AGPL-3.0-or-later; review each repository’s license and third-party notices. Enterprise licensing requires a separate signed agreement. Read why we opened the source.