Pricing.
Your cloud, your bill.
polign_db runs in your own cloud, so there is no metered service to pay for. You pay your cloud provider for a bucket and the nodes you choose to run. While a collection sleeps, you pay nothing.
Self-hosted
Free while polign_db is in v0.x early access. No license key, no time limit on what you deploy.
- The full feature set, with no tiers and no add-ons
- One static binary; durable with a single
-storeflag - Your bucket: AWS S3, GCS, Azure Blob, MinIO, R2
- Go package and Python SDK included
- Community support on GitHub
Design Partner
Six-month term, rate locked. Limited to the first five teams; we will say on this page when the seats are gone.
- Everything in Production Support
- A direct line to the engineers building polign_db
- Your workload shapes the roadmap: features and tuning land against your use case first
- Hands-on help from first bucket to production traffic
- Renews at the then-current Production Support rate
Production Support
For teams running polign_db in production who want someone on the hook besides themselves.
- Priority support with a named contact
- Deployment and tuning guidance for your workload
- Upgrade planning and operational review
- Commercial terms for production use
Every tier runs in your cloud, on your bucket, under your keys. The prices above buy support and partnership, not access: the software itself stays free to self-host during early access. We are committed to reducing what this costs you and improving the experience as polign_db matures.
What running it actually costs
The infrastructure bill is yours, and it is small: these numbers were measured with polign_db's benchmark harness against same-region Amazon S3. Full methodology on the benchmarks page. For a live example, read the case study: 12.5M Wikipedia passages for about $4.60 a month.
Point it at your bucket.
Install the server and bring your own S3.