Open source. No software subscription.

Free. Open source. Yours to run.

The software costs $0 — not a trial, not a freemium tier, not “free up to N rows”. You bring the infrastructure, your databases and your AI client. Here’s what that means in practice, including the costs nobody else puts on their pricing page.

Plan for the whole cost

What your team provides.

Infrastructure

A server to run the image on, the Postgres metadata database and Redis beside it, storage, network access and the databases you query. Your existing provider’s charges still apply.

AI access

A compatible client and model for authoring and analysis. Their fees depend on your provider. Running an existing pipeline does not require an AI authoring call.

Operations and review

Someone to deploy, secure, back up and update the server — with a restore drill you have actually run — and someone to verify that the answers match your business definitions. The runbooks are in deployment.md, the same docs that ship inside the product.

What free means here

Every feature, every row, every deployment

No seat count

Your whole company, your contractors, your agents — everyone who can reach the server may use it. Licences are counted in obligations, not people.

No feature gate

Federated joins, dp-lake, promotion between environments, the MCP tools — there is no paid tier that unlocks more, because there is no paid tier.

No account with us

Nothing you do is reported anywhere: the app reaches only what you configure, and the docs state there is no phoning-home telemetry. Your deployment is nobody's data point.

There is no paid tier today; if a hosted version ever exists it will be announced on the roadmap first.

Human help

You can talk to the person building it.

There is no support contract to buy. The owner answers this address personally and will help you connect your first datasource.

Contact the founder
  • Community supportAsk questions and share feedback in GitHub Discussions; bugs go to the issue form.
  • Transparent developmentBrowse the source, the packaged specs under /docs, and follow the public roadmap.
  • No paid support contract todayThere is no support SLA or managed hosting plan included.

The licence, plainly

AGPL-3.0, in two sentences

Running it inside your company

  • Asks nothing of you — internal use at any scale carries no obligation to share anything.
  • Custom pipelines, agents and integrations you write against the server are yours; the AGPL reaches the server's code, not your data or your SQL.

Offering it to others as a service

  • Publish your changes: if you modify the server and offer it over a network, the licence asks for those modifications under the AGPL.
  • Unmodified self-hosting for customers asks nothing — that is what "AGPL is fine for a self-hosting business" means in practice.

The full text is the repository's LICENSE; contributions take the one-time CLA described in CONTRIBUTING.md.

Before you decide

Clear expectations from the start

Is it really free?

Yes — free to run, for yourself or your customers, with every feature on every deployment. There is no seat count, no feature gate and no account with us, because the licence is AGPL-3.0 and you host it. (Licence and packaging: docs/deployment.md §10.)

What does AGPL require of me?

Running it inside your company — even at scale, even commercially — asks nothing of you. If you modify the server and offer it to others over a network, you publish your modifications under the same licence; that is the whole obligation. (The licence: docs/deployment.md §10.)

Will there be a hosted version?

There is no paid tier today, and nothing hosted is planned; if a hosted version ever exists it will be announced on the roadmap page first — never launched quietly. What is deliberately not planned lives on the roadmap's later band. (Source: docs/ROADMAP.md §3.)

Can I pay for support?

Not today — there is nothing to buy. Help is GitHub Discussions and Issues, the docs under /docs, and the owner answers the contact address on the pricing page personally. You also own the ops: the upgrade runbook is docs/deployment.md §8.

What about the demo data's licences?

The sample families are real public data, each under its own terms — NYC Open Data's no-restrictions statement, US Government public-domain works, the Census API terms — and the demo-data page quotes the operative sentence per family. (The demo and its gates: docs/deployment.md Appendix B.)

More on the full FAQ; what ships next is on the roadmap; the security posture is on security.

Start with one question your team needs answered.

Explore the sample data first. Connect your own databases when you’re ready.