Open core. Managed when you need it.
The clinical backend core is planned as open source (pre-release today) and is designed to run in your own AWS — no Business Associate relationship with us. When you’d rather not operate it yourself, the managed tier carries the BAA and the on-call pager.
Open Source
Apache-2.0 planned · pre-release
- The full clinical backend — every primitive, nothing held back
- Runs entirely in your own AWS
- App-native primitives, operational read models, reactive queries
- Canonical FHIR R4 / core profiles (JSONB), typed reads on top; clean Bundle export — roadmap
- Agent context tools — typed functions become SDK + MCP tools; complete HTTP surface — building
- Community support (Discord + GitHub)
- You operate it: backups, monitoring, upgrades are yours
Managed Cloud
Hosted · we sign a BAA
- Hosted and operated by us — we sign the BAA, backed by our AWS BAA
- Everything in Open Source
- Automated backups and point-in-time recovery
- Audit-log retention
- Managed hybrid-search indexing (production embeddings — building)
- Monitoring and alerting
- Team management
Enterprise / BYOC
Single-tenant · bring-your-own-cloud
- Single-tenant or bring-your-own-cloud deployment
- SLAs on uptime and response
- Dedicated support
- Advanced compliance and security review
- Everything in Managed Cloud
bonfireDB is early-stage. The core — planned as open source, pre-release today — is where the product lives; the managed and enterprise tiers are in early access and are listed to describe direction, not a fully shipped, generally-available offering. Pricing for paid tiers is not yet finalized — talk to us and we’ll be straight about what exists and what’s still being built.
Where your team lands depends on who holds the pager.
Same backend underneath. The line between tiers is who runs it and the BAA — not features withheld.
Building & exploring
Hackathon, prototype, or a team comfortable in its own AWS. Start with Open Source — it’s the whole thing.
Going to production with PHI
You want a partner who carries the BAA and runs the backups. Managed Cloud early access.
Procurement & isolation
Single-tenant, BYOC, contractual SLAs. Enterprise / BYOC — let’s scope it together.
Shipping agents
The agent context tools are planned across tiers. Propose-only writes, citations, and ABAC scoping are design defaults, not bolted-on promises.
You build the app. Bonfire is the clinical data layer underneath.
Start with early access to the core and move to managed when you’re ready for us to carry the BAA.
Frequently asked questions
How much does bonfireDB cost?
The core is planned as free open source under Apache-2.0 (pre-release today) and runs entirely in your own AWS. The Managed Cloud tier is in early access and the Enterprise/BYOC tier is talk-to-us. Paid-tier pricing is not yet finalized.
What’s the difference between bonfireDB open source and managed?
Same backend underneath — the line is operational responsibility and the BAA, not features. Open source gives you every primitive but you operate backups, monitoring, and upgrades; Managed Cloud (early access) means we host it, sign the BAA, and carry the pager.
Does bonfireDB sign a BAA?
On the open-source tier you self-host in your own AWS, so there’s no Business Associate relationship with us. On the Managed Cloud tier we sign the BAA, backed by our AWS BAA. bonfireDB is pre-launch, so the managed tier is early access.
Is bonfireDB cheaper than AWS HealthLake or Aidbox?
We can’t give a verified head-to-head — HealthLake and Aidbox pricing change, so check their current terms. bonfireDB’s core is planned as $0-to-license open source, designed to run in your own AWS; you pay only your AWS infrastructure. Managed pricing isn’t finalized yet.
Can I self-host bonfireDB for free in production?
Once the Apache-2.0 core is published — it is pre-release today — yes: it runs in your own AWS with nothing held back, and you’re responsible for backups, monitoring, and upgrades. Until then, access is via early access.