Pricing and CLI source code¶

Short doc. Honest answer.

The three tiers¶

Free — $0

• 1 workspace
• Up to 3 members
• Up to 10 published docs
• Public publishing, CLI + API access, full version history
• Unlimited PDF exports (with a small "Made with OpenDocs" footer)
• Default branding — our font, our purple accent

Enough for a personal publishing setup, a side project, or a tiny team kicking the tires.

Pro — $8/month (or $6/month billed yearly — $72/year, 25% off)

• 2 workspaces
• Up to 5 members per workspace
• Extra Pro workspaces available for $4/month each
• Unlimited documents
• PDF and DOCX export
• Custom brand color, font, footer, logo
• Hide the OpenDocs wordmark on exports
• Email support

The usual upgrade point is "I want client-ready branded exports" or "we've passed 10 docs."

Team — $4/user/month (or $3/user/month billed yearly, 3-seat minimum)

• Unlimited workspaces
• Unlimited members, billed by unique team member across the workspaces you own
• Everything in Pro, plus:
• Role-based access control
• Priority support

This is the "we run our company on it" tier.

Full comparison table lives at opendocs.cc/pricing.

What is open source today¶

People keep asking, so here's the straight answer:

OpenDocs is not fully open source today. We're starting by open-sourcing the part developers and agents touch directly: the CLI.

The CLI (@opendocs.cc/cli) is MIT. The tool you install with npm install -g @opendocs.cc/cli is fully open source — forkable, inspectable, auditable.

That matters because the CLI is the trust boundary on your machine. It's the thing reading local Markdown files, talking to the API, uploading images, pulling documents back down, and handing URLs to agents. You should be able to inspect the code that does that.

The hosted platform is closed source for now. The web app, API, document converter, and infrastructure are not public at launch. We may open source more of the stack later, but we don't want to promise that before the product and business have settled.

Why that model¶

We need to fund the platform while it's young. Open-sourcing the CLI gives users transparency where it matters most day to day, without forcing the whole hosted service to be public before we know exactly what kind of company OpenDocs needs to become.

If you're evaluating OpenDocs for a company and the source-code boundary matters to your legal or security team: the CLI is MIT on GitHub; the hosted platform is proprietary for now. If that leaves a question unanswered, drop us a line.

Get started¶

npm install -g @opendocs.cc/cli
opendocs login --key <your-key>
opendocs publish hello.md

Full manual: docs.opendocs.cc. Thanks for reading.