DocKosha is now open source: secure document sharing and data rooms

Update (October 27, 2026): DocYantra is now open source under AGPL-3.0-or-later at github.com/samarthmn/doc-yantra, and you can self-host DocKosha at your own risk without official support. This post has been updated to reflect both public repositories and the current self-hosting guide.

Almost a year ago, I got tired of checking which subscription unlocked the document controls I needed. That frustration became DocKosha, a platform for secure document sharing and virtual data rooms.

Today, we're publishing the application source under AGPL-3.0-or-later. You can read the code, review how document access works, and contribute to the product. DocKosha Cloud remains the managed service you can use today.

Both parts are now open: DocKosha’s application and DocYantra’s PDF and Office engine. You can inspect, contribute to, or run the application yourself under the repository licenses.

I'm proud to share this, and I want to explain the choices behind it.

Why I built DocKosha

I spent time looking at document-sharing tools such as Dropbox DocSend and Papermark. I wanted secure links, useful document analytics, and a data room with sensible access controls. I kept returning to pricing tables to work out which subscription covered the workflow.

What kept me building was the small team on the other side of the pricing page. A founder preparing investor documents. An adviser sharing confidential information. Someone who needs control over a file, even if they don't need much storage.

Their documents matter just as much.

One open-source application, with managed Cloud plans

DocKosha has one public application source edition. That includes the code for secure document sharing, virtual data rooms, document analytics, granular access permissions, NDA gates, and watermarking.

Source availability and hosted subscriptions answer different questions. The public repository lets you inspect and contribute to the application. Cloud plans determine the capacity and features available in the managed service.

Today, Free includes 250 MB of storage, 2 GB of monthly public bandwidth, PDF-only uploads, and one workspace member. Custom domains, branding removal, and retained previous versions require a paid plan. The pricing page lists the current allowances and differences.

Running the service costs money. Storage, document processing, maintenance, and support need funding. I want DocKosha to be sustainable because people find it useful and reasonably priced. I want customers to feel good about paying us.

If you're looking for a DocSend alternative for document sharing or a virtual data room for fundraising, start with the workflow you need, review the plan details, and inspect the code behind the product.

Why open the source?

When someone uploads a pitch deck, a contract, or confidential diligence material, they're placing real trust in the software handling it.

Publishing the application code gives developers and security reviewers something concrete to examine: how access checks work, how sharing rules are applied, and how the application handles analytics. Our security page explains the current security and privacy boundaries.

Code visibility doesn't prove how a hosted service operates or replace security reviews. It does make more of our work open to scrutiny. That matters in a product built around sensitive documents.

I also want people to challenge our assumptions. Contributors may notice a confusing permission setting, a missing accessibility detail, or a document workflow we haven't considered. There's a limit to what one founder can see from inside their own application.

DocKosha's public application source is licensed under AGPL-3.0-or-later. The repository includes the license and contribution guidance so you can review the terms alongside the code. Enterprise licensing requires a separate signed agreement.

Can you self-host DocKosha today?

Yes. DocKosha and DocYantra are both open source under AGPL-3.0-or-later. DocYantra runs inside the application through its versioned Rust and WebAssembly packages; it does not require a separate conversion server.

The self-hosting guide explains the prerequisites and links to the complete repository walkthrough. Installation uses GitHub Packages, which requires a classic GitHub token with read:packages access even for public packages. The DocYantra deployment guide covers embedding the engine and offline fonts.

Self-hosting is not officially supported. You maintain the database, object storage, email delivery, backups, security updates, and monitoring. Community help is best effort, without an SLA. Some teams want that responsibility and control; others want the managed service. Our Cloud and self-hosting comparison describes the tradeoffs.

DocKosha Cloud is the managed service available now. We handle the operational work so you can prepare your data room, share your documents, and get back to the work around them. My ambition is to make that experience good enough that people choose it because it saves them time.

Help shape what comes next

After almost a year, opening the application feels personal. I hope the open-source community welcomes us, questions us, and helps make DocKosha better.

If you use document-sharing tools, tell us where they get in your way. If you build software, our contribution guide explains how to get involved.

I started DocKosha with my own frustrations. I want the next chapter to include yours.

Try DocKosha Cloud · DocKosha source · DocYantra source · Self-hosting guide