DocKosha
Open source and Cloud

Read the source, or use Cloud

DocKosha’s application is open source under AGPL-3.0-or-later for inspection and contribution. External self-hosting is not currently available because the mandatory DocYantra dependency is private; DocKosha Cloud is the available hosted product.

Start on DocKosha CloudRead the announcement

The short version

The source is public for reading and contribution, but external self-hosting is not currently available. DocKosha Cloud is the supported way to use the product today.

Read and contribute to the public source if

  • You want to inspect the public DocKosha source under the AGPL-3.0-or-later license.
  • You want to review the architecture and contribute improvements.
  • You understand that external self-hosting is not currently available.
  • You do not need external access to the private DocYantra dependency.

Use DocKosha Cloud if

  • Operating the stack is not how your team wants to spend its week.
  • You want upgrades, backups, deliverability, and custom-domain certificates handled for you.
  • You want the DocYantra processing path already operated inside Cloud.
  • You would rather pay a subscription than carry an on-call rotation.

What a future self-hosting path would involve

These are maintainer reference notes for a possible future self-hosting path, not instructions or an offer available today.

Upgrades and migrations

Releases ship with database migrations. Taking a version means reading the release notes, applying migrations in the same change, and having a way back. It is a recurring calendar item, not a one-time install.

Backups you have actually restored

Provisioning Postgres is the easy half. The half that matters is a restore you have rehearsed into a scratch environment on a schedule you trust, because a data room is the wrong place to discover an untested backup.

Object storage and its bill

A bucket, its CORS configuration, credentials, lifecycle rules, and its own backups. Document storage grows in one direction, so someone owns retention policy and cost as the room count climbs.

Email deliverability

Access gates that mail one-time passcodes are exactly as reliable as your SMTP path. SPF, DKIM, DMARC, and the sending domain's reputation are yours. This is the duty operators underestimate most often, not because it is hard but because it fails quietly.

Custom-domain infrastructure

Serving rooms on a customer's own domain needs wildcard DNS, automated certificate issuance, and a router in front of the app. DocKosha ships that router as a Cloudflare Worker; a future operator would need to account for that infrastructure.

Secrets and transport security

Generating, storing, and rotating the cookie secret, service-role keys, and SMTP credentials, plus TLS termination and the proxy in front of the Node process. Nothing in the repository generates or escrows a secret for you.

Availability and monitoring

Process supervision, log capture, alerting, and capacity planning would be future operator considerations. No external self-hosting support is currently available.

Legal and regulatory duties

Retention, data-subject requests, and regulatory obligations for the documents your users store would be future operator considerations if an external deployment becomes available.

The repository ships public source and maintainer reference material. It does not currently ship an externally runnable deployment or DocYantra access.

What is available today

There is one supported route today: DocKosha Cloud. The source is public for review and contribution; a runnable external route is not currently available.

ConcernPublic source (runtime unavailable)DocKosha Cloud
Upgrades and migrationsFuture operator reference only; external runtime unavailable today.Applied by DocKosha; nothing for you to schedule.
Database and backupsFuture operator reference only; external runtime unavailable today.Managed and backed up as part of the service.
Object storageFuture operator reference only; external runtime unavailable today.Included in the plan's storage allowance.
Email deliverabilityFuture operator reference only; external runtime unavailable today.Sent over DocKosha's sending domain, which we maintain.
Custom domainsFuture operator reference only; external runtime unavailable today.Configured in the app on paid plans.
TLS and secret rotationFuture operator reference only; external runtime unavailable today.Managed by DocKosha.
Monitoring and on-callFuture operator reference only; external runtime unavailable today.DocKosha's.
SupportNo external self-hosting support is currently available.Commercial support and service-level agreements are paid artifacts, available through Cloud or a separate agreement.
DocYantra engineUnavailable to external users while the private DocYantra dependency remains internal.Already running; no separate key to buy.
What it costsFuture operator reference only; no external runtime is available today.A subscription; the plan tiers are on the pricing page.

What the Cloud product provides

These are the product guarantees available through DocKosha Cloud.

Safety-critical capability stays in the DocKosha application

Link gates (password, one-time passcode, expiry, revocation, open-once, allowlists and blocklists), data rooms with room, folder, and document access lists, static and dynamic burned-in watermarking, the NDA gate, DocYantra-backed redaction, the audit log, analytics, and version history are all part of the DocKosha application. Authorization, security, and evidence quality do not depend on a separate edition. That is a design rule, not a promotion.

Watermarks are burned into the delivered bytes

Watermarking runs server-side in the current DocKosha Cloud product and is burned into the PDF bytes that get delivered. It is not an overlay drawn on top of the page in the browser, so it survives the file leaving the viewer.

Screenshot protection is a deterrent, and we say so

No browser can block an operating system's screen capture, and none can stop a phone camera pointed at the monitor. The screenshot controls raise the effort and leave a trail; they do not make a document uncopyable. We would rather you know that before the deal than after it.

Conversion fails closed, never degraded

In the current DocKosha Cloud product, work outside the validated format, size, and fidelity envelope fails with a typed reason and the viewer serves the original file unchanged. It never renders a partial approximation and calls it a success.

What the public source and Cloud product include

DocKosha source is published under AGPL-3.0-or-later. The Cloud product provides the hosted feature set, including:

  • Custom domains and white-label branding
  • User groups and group-based access rules
  • Advanced analytics: per-page dwell, country, media sections, exports
  • Versioning retention policies

The capability matrix also names later roadmap items such as SSO/SAML and MFA enforcement; those are not shipped, so treat them as roadmap rather than as something you are buying.

DocYantra is the private mandatory direct `0.0.26` dependency for the validated Office and PDF path. Enterprise terms require a separate signed agreement and do not imply engine access; see pricing for that path.

Source publication does not create a deployment

The public repository is available for review and contribution, but it is not currently an externally runnable deployment.

What source publication does and does not provide

  • Telemetry and marketing analytics are opt-in and environment-gated. Leave their variables unset and those integrations are inert.
  • External users do not receive private DocYantra package access, tokens, SDKs, APIs, or engine licenses.
  • The public repository is not an externally runnable distribution today; there is no external installation to count.
  • The claim is meant to be checked rather than trusted: grep the source for DocKosha-owned endpoints, then read env.example for every configurable network boundary.

Cloud is different, and here is exactly how

DocKosha Cloud is a hosted service we operate, so it runs viewer and product analytics under consent:

  • Consent is regional. Visitors in the EU, EEA, and UK — and any visitor whose region cannot be determined — get nothing until they explicitly opt in.
  • Elsewhere, analytics default to granted with a straightforward opt-out.
  • A Global Privacy Control signal always wins, whatever the region says.
  • Raw IP addresses are never stored by the current application.

The security page covers the rest of what Cloud does with data.

Pick the path that fits your week

Read and contribute to the repository under AGPL-3.0-or-later, or use DocKosha Cloud for the available hosted product. Enterprise terms require a separate signed agreement and do not grant DocYantra engine access.

Start on DocKosha CloudAsk about Enterprise licensing