necodoc / Open source and pricing

Open source and pricing

MIT-licensed. No licence fee for workers, users or documents.

Every feature ships in one build, and you run it on your own infrastructure. There's no paid tier and no usage meter.

$0
Per worker
Workers are a replica count.
$0
Per user
Sign people in through your IdP; add as many as you need.
$0
Per document
A renewal run of ten thousand costs what the compute costs.
MIT
Licence
Use, change and redistribute it, commercially too.
ItemWhat it isMore
API and render workersContainers on your Kubernetes cluster or VMs, scaled to the load.Roles and scaling ↗
PostgresOne database, managed or your own. It holds templates, versions, logs, audit and the job queue.Self-hosting
Object storageAn S3-compatible bucket, an Azure Blob container, or a shared disk for generated PDFs.Storage ↗
MonitoringYour existing Prometheus, OpenTelemetry collector and log shipper.Observability
AI, if you turn it onYour Anthropic API usage, billed to your key. Field detection measured about 1.5 cents a page.PDF overlay templates
E-signature, if you use itYour own DocuSign, Dropbox Sign or Adobe Acrobat Sign account. necodoc builds the envelope.Signing packages
Your team's timeRunning, patching, backing up and upgrading it.Upgrades ↗

You can

Use, change, fork and redistribute it

In production, commercially, inside your own products. Keep the copyright and licence notice with copies of the code.

It comes

As is, with no warranty

Test it against your own forms and volumes before you depend on it. The benchmark and the specs show how.

Vendor risk · OSFI B-10

Your exit plan is your own copy

Standard Postgres, PDFs in your storage, templates as data, and the source. No licence server.

Proof

Read it before you agree to it

The licence is one short file at the root of the repository.

Read the LICENSE fileHow self-hosting bears on B-10 and B-13 →

Contributing

Issues, pull requests and questions on GitHub.

We write down each behaviour before we build it. Each feature has a spec in docs/, and a pull request that changes behaviour must update its spec.
Report a bug or a form that won't open.

Open an issue with the PDF if you can share it, or the error from the generation log if you can't.

Send a pull request.

Read the spec for the area first, and update it with the change. Make sure pnpm check, pnpm typecheck and pnpm test pass.

Ask a question.

Use GitHub Discussions.

Read the decisions.

Architecture decisions are numbered ADRs in docs/adrs, linked from each spec.

Source on GitHubGitHub Discussions ↗

Support

Support is coming soon.