Flexprice pricing

About

Flexprice is open-source usage metering and billing infrastructure for AI-native and SaaS teams — a developer-first engine that handles custom usage events (API calls, compute, queries), prepaid credits and wallets, entitlements, invoicing, and subscription/usage-based/hybrid pricing models without forcing teams to build billing logic from scratch. Its tagline is “The Billing Infrastructure for AI Revenue,” and the homepage claims it is trusted by 100+ AI and agentic teams.

The product is open-core: roughly 99% of the codebase is AGPLv3 (the engine is 94.9% Go), fully self-hostable for free, with a commercial Enterprise Edition and a managed cloud layered on top. The public GitHub repo shows about 3.6k stars, 168 forks and 63 releases. Flexprice was built by three co-founders — Manish Choudhary (CEO), Nikhil Mishra (CTO) and Koshima Satija (COO) — and positions itself on developer experience: multi-SDK support, sub-60ms latency, SOC 2 Type II, and the ability to “close deals with custom pricing and add-ons without waiting on engineering.”

For the most current information, visit Flexprice.

Pricing summary : How Flexprice’s pricing model works

Flexprice has two ways in. You can self-host the AGPLv3 open-source edition for free — you run the infrastructure, you get the full billing engine. Or you can use the managed cloud, which has four public tiers metered by monthly events and a cumulative-billings cap:

• Free — 100k events per month, 1 Month Validity, with the full pricing-model toolkit (subscription, usage-based, hybrid), add-ons, coupons, tax, PDF invoices, prepaid credits and community Slack support.
• Build — $500/month — 1 million events per month, 99.9% SLA, 99.99% HA Options, real-time metering, Stripe integration, API keys, and a 1 Business Day P0 response. Capped at Up to $250K cumulative billings (or) $20K monthly.
• Scale — $1000/month — 5 million events per month, adding prepaid credits/wallets, a customer portal, pricing experiments, plan overrides, custom SQL metrics, multi-currency billing, 50+ integrations, Google SSO and audit logs, with a 2 business Hour P0 response. Capped at Up to $1.2M cumulative billings (or) $100K monthly.
• Mission Critical — Custom — Custom events per month, unlimited billing, SAML SSO/SCIM, SOC 2 Type 2, on-prem/air-gap deployment, dunning, a forward-deployed engineer and a 15-minute P0, 24/7 response.

What makes this different: unlike most billing infra (Stripe Billing, Chargebee, Lago’s hosted plans), Flexprice’s tiers don’t just meter usage events — they also cap the cumulative billings the platform will process ($250K on Build, $1.2M on Scale). It is metering how much revenue you run through it, and you graduate tiers when either the events allowance or the billings cap is hit. And because the core is AGPLv3, the “free tier” is, in the truest sense, the entire product — if you’re willing to operate it.

Pricing by product

Sales motions across products: self-serve PLG for Open Source (deploy it yourself) and the Free / Build / Scale cloud tiers (the page has “Get Started” buttons and published prices) — and sales-led for Mission Critical (on-prem, SOC 2, SSO, custom integrations and a 4-to-6-week technical onboarding go through “Contact Us”).

Hidden costs : What Flexprice users actually pay

Flexprice’s cloud bill is mostly predictable — a flat monthly tier — but two gates can move you up unexpectedly. The first is the events allowance (100k → 1M → 5M); the second, less obvious one, is the cumulative-billings cap. A team on Build that crosses $250K cumulative (or $20K/month) billings is over the cap even if it is under 1M events, and must move to Scale. The other real cost is self-hosting: the OSS is free as software, but you pay in infrastructure and engineering time to operate an event-ingestion pipeline, database and uptime yourself.

Want to estimate your own Flexprice bill? Use the Flexprice pricing calculator to model your costs based on monthly events and billings volume.

Pricing evolution : Flexprice pricing history and changes

Cadence

Tracked range: 2024–present. Flexprice publishes its cloud tiers openly on flexprice.io/pricing (captured 2026-06-10); the open-source repo dates the engine and releases. Exact tier-introduction dates are approximate — anchored on the live capture and the GitHub release history.

Notable changes

• 2024 — Flexprice ships as an open-source (AGPLv3) billing engine — self-hostable for free, establishing the open-core model with community Slack support.
• 2025 — A managed cloud is added on top of the OSS, with public tiers (Free, Build $500/mo, Scale $1000/mo, Mission Critical) pricing the hosted platform, SLAs and support.
• 2026 — Tiers are gated by both monthly events and a cumulative-billings cap ($250K on Build, $1.2M on Scale); Mission Critical formalizes SOC 2 Type 2, SAML SSO/SCIM and on-prem/air-gap deployment.

What’s unique : Flexprice’s distinctive pricing mechanics

1. Open-core where the “free tier” is the whole product.

Roughly 99% of the code is AGPLv3 and fully self-hostable, so a team that runs its own infrastructure gets the entire billing engine for $0 in license cost. The managed cloud sells operations, SLAs, support and a handful of enterprise features — not the core capability. That is a sharply different bargain from closed billing infra.

2. Tiers metered by cumulative billings, not just events.

Most usage-billed infra meters one thing. Flexprice meters two: a monthly events allowance (100k / 1M / 5M) and a cumulative-billings cap ($250K on Build, $1.2M on Scale). It is, in effect, taking a position on how much revenue you process through it — and graduating you when either ceiling is hit.

3. A billing tool priced like the billing it sells.

Flexprice’s own plans run subscription + usage + hybrid logic, prepaid credits, coupons, tax and PDF invoices — the exact mechanics it gives customers. The pricing page is a live demo of the product, which doubles as a credibility signal for a developer audience.

4. Support response time is an explicit, tiered SKU.

The ladder from 1 Business Day (Build) → 2 business Hour (Scale) → 15-minute, 24/7 (Mission Critical) P0 response makes responsiveness a named, escalating feature — a sign Flexprice expects to sit on a revenue-critical path where downtime is expensive.

Strengths & weaknesses

Billing UX : Flexprice billing controls and transparency

• Billing controls — Cloud tiers are self-serve with “Get Started” buttons and published prices; Mission Critical routes to “Contact Us.” The two levers that matter are your monthly events and cumulative billings, since crossing either cap (Build’s $250K / $20K monthly, Scale’s $1.2M / $100K monthly) is what moves you up a tier.
• Usage visibility — Build and above include real-time metering and reporting plus customer usage views; Scale adds a customer portal, pricing experiments and custom SQL metrics, so usage is observable both for the operator and end customers. Yearly billing carries a -20% discount toggle.
• Payment options — Self-serve sign-up and Stripe Payments Integration (from Build) handle card billing; Scale adds multi-currency and multi-timezone billing and HubSpot/Stripe Tax among 50+ integrations. Mission Critical moves to a custom contract with dunning and payment retries.

Strategic wins : Why Flexprice’s pricing decisions worked

1. Open source as a developer wedge.

Making the engine AGPLv3 and self-hostable lets developers adopt Flexprice with zero procurement — clone, deploy, evaluate — which seeds the managed cloud and enterprise conversations later. See how AI companies structure pricing.

2. Public, simple cloud tiers.

Posting $500 and $1000 list prices (rare among billing-infra vendors, which often hide everything behind sales) lets a team self-qualify in minutes — a fast path from “interested” to “Get Started” that matches a developer buying motion. Related: choosing the right usage metric.

3. Metering revenue, not just volume.

By capping cumulative billings alongside events, Flexprice ties its price to how much value flows through the platform — so a customer that processes more revenue pays more, aligning Flexprice’s revenue with the customer’s. See outcome-based pricing trends.

Areas to improve : Gaps in Flexprice’s pricing approach

1. The billings cap is easy to miss.

A team can sit comfortably under Build’s 1M-event allowance yet blow past $250K cumulative billings and be forced to upgrade — a second meter that is less visible than events. Clearer in-product warnings would reduce surprise. See bill shock and cost unpredictability.

2. Free’s 1-month validity makes it a trial.

The cloud Free plan expires after a month, so it functions as an evaluation rather than a durable free tier. A persistent (if smaller) always-free cloud allowance would better match the open-source ethos.

3. No published price between Scale and custom.

The jump from $1000/mo to a fully custom Mission Critical quote leaves mid-to-large teams (above $1.2M billings but not yet enterprise) without a self-serve price — pushing them into a sales cycle earlier than necessary.

Key takeaways

1. Open-core can make the free tier the whole product. With ~99% AGPLv3, Flexprice gives away the full engine to self-hosters and monetizes operations, SLAs and enterprise features via the cloud.
2. Meter two things, not one. Flexprice caps both monthly events and cumulative billings ($250K on Build, $1.2M on Scale), tying price to how much revenue flows through the platform.
3. Public list prices speed developer adoption. Posting $500 and $1000 tiers lets engineers self-qualify in minutes — a contrast to the sales-gated norm in billing infrastructure.
4. Flat tiers buy predictability. Within an allowance, the cloud bill is a fixed monthly number, avoiding the per-event bill-shock that consumption metering can cause.
5. Enterprise sells responsiveness and compliance. The ladder to a 15-minute 24/7 P0, SOC 2 Type 2 and on-prem/air-gap shows Flexprice expects to live on a revenue-critical path.

UBP implications

1. Cumulative billings is a value metric, not just a volume meter. Pricing on the revenue a customer processes (not only raw events) aligns vendor and customer growth — a clean example of metering value. See usage-based pricing strategy.
2. Open source plus a metered cloud is a viable UBP funnel. Free self-host seeds adoption; the managed cloud captures revenue once usage and billings scale — a structure other infra vendors can copy.
3. A capped tier with two gates needs transparent telemetry. When upgrades can be triggered by either events or billings, clear usage visibility is essential to avoid surprise — a lesson for anyone designing multi-dimensional UBP.

Sources

• Flexprice pricing page (accessed 2026-06-10) — Free 100k events, Build $500/mo (1M events, $250K cap), Scale $1000/mo (5M events, $1.2M cap), Mission Critical custom
• Flexprice homepage (accessed 2026-06-10) — “The Billing Infrastructure for AI Revenue”; founders; 100+ AI/agentic teams
• Flexprice GitHub repository (accessed 2026-06-10) — AGPLv3 open-core (~99%), Go (94.9%), ~3.6k stars, self-hostable
• Flexprice documentation (accessed 2026-06-10) — usage metering, credits/wallets, pricing models
• Browse the pricing blueprint for more fully-researched company profiles.

Bottom line

Flexprice is open-core billing infrastructure for AI/SaaS — a fully self-hostable AGPLv3 engine (free) plus a managed cloud with public, predictable tiers: Free (100k events/month, 1-month validity), Build at $500/month (1 million events, up to $250K cumulative billings), Scale at $1000/month (5 million events, up to $1.2M cumulative billings), and a custom Mission Critical enterprise plan. What stands out is the double meter — Flexprice gates each tier by both monthly events and the cumulative billings it will process, tying its price to the revenue a customer runs through it — and the open-source path, where self-hosters get the entire product for the cost of running it. The trade-off is a 1-month Free validity, a billings cap that can force an upgrade before events run out, and compliance/on-prem gated to a custom quote.

Want to compare Flexprice against other billing and monetization-infrastructure companies? Browse the pricing blueprint.

Pricing timeline : Major events on a vertical axis

Each milestone below corresponds to a public pricing change, product launch, or material adjustment. Major events use a filled marker; minor adjustments use a faded one.

Public cloud pricing: events + billings caps, SOC 2, on-prem

Jun 2026

Current shape: free AGPLv3 self-host + four public cloud tiers metered by monthly events and a cumulative-billings cap (Build $250K, Scale $1.2M). Mission Critical adds SAML SSO/SCIM, SOC 2 Type 2, on-prem/air-gap deployment, dunning and a 15-minute 24/7 P0 response.

Managed cloud tiers: Free, Build $500, Scale $1000, Mission Critical

Jun 2025

Flexprice layers a managed cloud on top of the OSS: a Free plan (100k events/mo), Build at $500/mo (1M events, up to $250K billings), Scale at $1000/mo (5M events, up to $1.2M billings) and a custom Mission Critical enterprise tier — pricing the platform, SLAs, support and enterprise features.

Open-source usage-metering & billing engine (AGPLv3)

Jan 2024

Flexprice ships as an open-source (AGPLv3) Go billing engine — usage metering, credits/wallets, subscriptions, and usage/hybrid pricing — self-hostable for free with community Slack support, establishing the open-core foundation.