Closure
Open-source, MIT-licensed pricing, metering, entitlements, and billing infrastructure for AI products.
At a Glance
MIT-licensed core Closure product that can be self-hosted using Docker. The alpha/guided hosted offering is separate and has no published pricing.
Engagement
Available On
Listed Nov 2026
About Closure
Closure is an open-source pricing and metering system from Disjoint, Inc. for AI products. Your app sends meter events and balance checks to the Closure API, which checks and records them in Redis so users don't wait on the database, and usage thresholds can trigger tasks in tools like Slack, Teams, Linear, Jira, or webhooks. The code is MIT licensed and can be self-hosted with Docker.
What It Is
Closure provides primitives for metering, entitlements, credit wallets, and billing so that pricing can be managed in code and changed often. Resources are versioned and immutable, so changes can be reversed and history replayed. Payment processing and tax calculation are meant to be handled by third-party providers, and sensitive payment information is not stored on your servers.
How the architecture works
Meter events and balance checks are validated and recorded in Redis for hot-path access decisions. Events are flushed in batches to Postgres, which keeps a full record and can rebuild Redis if it is lost. Hatchet queues, rate-limits, and retries notification tasks, while Nango stores the logins for Slack, Teams, Linear, and Jira and makes calls to them.
Use cases across teams
The README lists patterns such as credit wallets, sliding-scale top-up packs, soft limits, reserved action pools, discounts, and referral bonuses. Finance can send invoices and reconcile revenue with usage costs, growth can run promotions, coupons, and referrals, and sales and customer success can build custom deals and get notified about customer activity. Engineering can implement blocks before charges happen.
Setup path
The project offers a guided route through an alpha program, or a self-hosted hobby instance deployed with a one-line Docker script on Linux. Self-hosting runs Closure, Postgres, Redis, Hatchet, and Nango on one machine, with optional HTTPS on your own domains. The README notes that Linux ARM servers need an emulation package because Nango publishes only an Intel/AMD build.
Why the founders built it
The founders' launch posts argue that billing carries heavy tech debt and that changes should be reversible and legible. They also argue that metering should be fast enough for real-time allow or reject decisions, and they say they migrate existing billing into Closure incrementally using agentic skills files.
Community Discussions
Be the first to start a conversation about Closure
Share your experience with Closure, ask questions, or help others learn from your insights.
Pricing
Open Source (Self-hosted)
MIT-licensed core Closure product that can be self-hosted using Docker. The alpha/guided hosted offering is separate and has no published pricing.
- MIT License
- Self-hosted hobby instance deployable in one line on Linux using Docker
- Runs Closure with Postgres, Redis, Hatchet and Nango
- Meter events and balance checks via Closure API
- Task notifications to Slack, Teams, Linear, Jira, or webhook
Capabilities
Key Features
- Metering with real-time balance checks in the hot path
- Entitlements and credit wallets
- Versioned, immutable resources with replayable history
- Usage-threshold task notifications to Slack, Teams, Linear, Jira, or webhooks
- Support for top-up packs, soft limits, reserved action pools, discounts, and referral bonuses
- Redis-backed checks with batched flush to Postgres
- Self-hosted deployment via Docker one-liner
- Optional HTTPS gateway for custom domains
- Agent skills file for setup assistance
- MIT licensed
