If your security review requires SSO, the standard paid plan won't pass it, and you move to the tier that includes it. Ask for the current price from Convex, since it's the one figure here that depends on your contract. ### Convex pricing for high-volume, API-heavy products When the product is high-volume or API-heavy, the usage meters dominate. If much of that traffic comes from automations, for example workflows that call your [Convex](https://www.convex.dev/pricing) functions on a schedule, each run adds function calls and bandwidth to the bill. Estimate calls per user per day, multiply by your user count, and set spending limits before launch. ## Convex plans, pricing and limits You choose from four tiers: Free/Starter, Professional, Business and Enterprise. All four meter the same three things (function calls, bandwidth and storage), so the plan you pick changes your allowance, your seats and your controls, not what gets counted.  ### The plan table, checked 3 November 2026 | Plan | Price | Per-member price | Function calls | Database and file storage | Bandwidth | Team limits | Support | SSO | |---|---|---|---|---|---|---|---|---| | Free/Starter | No monthly fee | None | Capped allowance | Capped allowance | Capped allowance | Solo builders and small projects | Community | No | | Professional | Monthly fee | Charged per seat | Larger allowance, metered beyond it | Larger allowance, metered beyond it | Larger allowance, metered beyond it | Teams with named members | Paid-tier support | No | | Business | Higher monthly fee | Charged per seat | Larger allowance, metered beyond it | Larger allowance, metered beyond it | Larger allowance, metered beyond it | Wider team and permission controls | Prioritized support | Yes | | Enterprise | Custom contract | Negotiated | Negotiated | Negotiated | Negotiated | Custom controls | Contracted support | Yes | ### How Convex overage and included usage work Past the allowance of function calls, storage and bandwidth that each paid tier includes, Convex bills usage by the unit. Your bill is therefore a base fee, plus seats, plus overage. Treat the included allowance as your break-even line: if your estimated calls per user per day times your user count lands well under it, overage is a rounding error. If it lands over, the per-unit rate matters more than the base fee. ### What the free tier does and does not allow You can build, test and launch a real product on the free tier. What it removes is headroom: Convex caps the allowances, there's no team structure beyond a small group, support comes from the community, and there's no SSO. At a moment you don't choose, the free tier fails: traffic outgrows a cap or a second developer needs access. Compare your function-call estimate against the cap now, and treat a hire or a first enterprise customer as the signal to move up.  ## What Convex costs at realistic usage **Start at $25 for a one-developer Professional bill**, which grows through whichever meter your app leans on hardest, so compute it in this order: 1. Multiply developers by $25, which gives you the monthly development team cost. 2. According to [Apis](https://apis.io/plans/convex/convex-plans-pricing/), function calls over 25M cost $2 per 1M, so exceeding the included tier brings additional charges. 3. Take storage over 50 GB and charge $0.20 per GB, meaning data growth requires payment beyond your base allocation. 4. Take action compute over 250 GB-hours and charge $0.30 per GB-hour, making compute-heavy workloads cost extra. 5. Add bandwidth last, at the published rate. A meter you stay under adds nothing, because each step has its own included allowance. On the free tier, a hobby app with one builder and a handful of testers costs $0, because none of the five steps produces a charge below the free caps. ### Small SaaS with a few thousand users Take one developer, 100 GB stored, and function calls under 25M, representing a small-team configuration. The seat is [$25 per month](https://makerkit.dev/pricing-calculator/convex), so team expansion increases your fixed monthly costs. [Makerkit](https://makerkit.dev/pricing-calculator/convex) calculates storage at 50 GB over the allowance at $0.20, which is a $10 storage overage. The bill is $35.  At 71% of that total, the seat outweighs everything else, so a second hire moves the bill more than doubling your stored data would. ### Convex cost for a real-time app Now assume one developer, 125M function calls a month, and storage inside the 50 GB allowance. Calls over the 25M allowance come to 100M. At $2 per 1M, that's $200. Add the $25 seat and the bill is $225.  89% of that total is function calls. A real-time app re-runs queries whenever the underlying data changes, so call volume tracks how many users are connected and how often data moves. Halving unnecessary subscriptions, such as queries on screens nobody is looking at, saves more than any storage cleanup. ## Hidden Convex costs and limits teams hit Not every cost is headlined on the pricing page: reactive queries, execution limits, document size, seats and SSO are the ones that catch teams out. - Reactive queries re-run whenever their data changes, and each re-run counts as a function call. - Execution limits cap how long a function can run, so heavy work must be split up. - Large documents are re-sent to every subscriber, which inflates bandwidth. - **Convex charges seats per developer**, so cost grows with headcount. - SSO sits behind higher tiers, so a security requirement can force an upgrade.  ### How Convex function calls add up A live query isn't one call. Every time a document it reads changes, Convex re-runs it, and that re-run is metered like any other function call. The unit to watch is **calls per write, not calls per page view**. Because each re-run sends the whole result again as bandwidth, large documents make it worse. Keep documents small and subscribe to narrow queries. To push Convex data into Slack, a CRM or email, Activepieces can call Convex's HTTP endpoints, and it bills the run, not the steps inside it: 1 credit per flow run, with 1,000 credits a month on the free plan. A ten-step flow costs what a two-step one does, so splitting the work into smaller, safer steps carries no penalty on that side. Convex's meter is unchanged, though: each endpoint call still lands on your Convex bill as a function call. ### Convex limits you hit before billing Expect concurrency to be the ceiling that shows up first. [Convex scalability research](https://github.com/MartinKalema/horizontal-scaling-convex/blob/dev/docs/convex-scalability-research.md) puts Free and Starter at 16 concurrent queries, so a **launch-day spike can return HTTP errors instead of costing money**. Professional allows 256, a sixteen-fold jump. Business and Enterprise allow 1024. ### Convex per-seat cost as your team grows Larger teams face larger bills, because Professional is priced per developer and [Convex's pricing page](https://www.convex.dev/pricing) shows $25 a month each. One developer pays $25. Three pay $75, five pay $125, ten pay $250, and twenty pay $500. The surprise isn't the rate, because the line is straight. It's that contractors and part-timers each add a full seat. Count who needs dashboard access before you invite everyone. **This week, set a hard spend limit in the team's billing settings, below what you could absorb in a bad month.** Add usage alerts at a lower threshold, so you hear about a runaway query before the limit stops the app. ## Convex pricing compared with Firebase and Supabase For small teams whose app is mostly reads and writes through functions, Convex can be cost-effective. It loses on cost when the team is large or the workload is heavy on files or raw database storage. | | Convex | Firebase | Supabase | |---|---|---|---| | Entry paid price | Per-member monthly fee on Pro | No base fee; pay as you go on Blaze | Flat monthly Pro fee with usage quotas included | | Free limits | Capped function calls, bandwidth and storage | Daily and monthly quotas per product | Capped database size, bandwidth and monthly active users | | Main billing meter | Function calls, then bandwidth and storage | Reads, writes and deletes, plus egress | Compute size, then egress and storage | | Seat charges | Yes, on paid plans | None for the core service | None on Pro; higher tiers add team controls | | Self-hosting | Open-source backend you can run yourself | None | Open-source stack you can run yourself | | Cheapest for | Small teams with function-heavy apps | Spiky or low-traffic apps | Teams that want a standard Postgres database |  Read the seat row first: Convex is the one that **multiplies its price by headcount**, so the dashboard-access count from above feeds straight into your bill. ### Convex vs Firebase On [Firebase](https://firebase.google.com/pricing), every refresh of a screen that re-queries often costs more, because it meters document reads, writes and deletes. Convex meters function calls, which are easier to forecast because you wrote every function. A ten-person team with modest traffic can pay less on Firebase, which has no per-person fee. For such a team, Firebase has no self-hosted option, so its pricing is the only exit path you control. ### Convex vs Supabase Cost stays flat on Supabase until you outgrow the database size you rent, then steps up, because it bills mainly on that size. Convex costs rise more smoothly with usage but add a seat charge. If your app is steady and your data model is already relational, Supabase's flat tier is the easier number to budget. If traffic is uneven and the team is small, Convex's meter tracks what you actually use. Because both Convex and Supabase publish open-source backends, your lock-in risk is capped. Running either yourself removes the vendor's usage meter but replaces it with servers, backups and an engineer's hours. ## What Activepieces does about this The automation traffic is the part of your Convex bill you can control. Activepieces runs the scheduled and event-driven flows that call your Convex endpoints, and it meters a flow run as 1 credit, with 1,000 credits a month on the free plan.  Before launch, count flow runs per day and multiply by the Convex calls each run makes. Batch a run to fetch many records in one call, and the Convex meter falls with it. Activepieces is MIT-licensed for the community edition, so you can self-host it and keep that cost off the usage meter. ## Frequently asked questions ### Is the Convex free tier only for hobby projects? No. The free tier isn't restricted to hobby projects, so a small production app can run on it. The catch is headroom. Function calls, bandwidth and storage are all metered, so a launch that goes well can outgrow the free allowance quickly. Treat it as a way to launch, and plan the move to a paid plan before real traffic arrives. ### Does Convex charge per seat? Yes, in part. Paid plans are priced partly by team member, with metered usage on top. That makes headcount a real cost line, not a rounding error. Check how your plan counts people who only look at the dashboard compared with people who deploy code. Convex's pricing page is the place to confirm that, because it decides whether stakeholders who only need to watch usage cost you anything. ### What happens if I exceed the free tier limits? Nobody silently bills you on the free plan. Going over means you either upgrade or accept restrictions on your deployment, and restrictions in production mean your app degrades for users. That's why the sensible move is to watch usage against the limits well before launch and decide in advance which side of that choice you'll take. On a paid plan, usage beyond what the plan includes is billed, so the limits you set are your protection against a surprise invoice. ### Can I self-host Convex to avoid usage fees? You can self-host, because the backend is open source. That doesn't make it cheaper by default. You stop paying Convex's metered rates and start paying for servers, backups, upgrades, monitoring and the engineer hours behind them. Run that comparison against your expected function calls, bandwidth and storage. For most small teams, self-hosting earns its place as an exit option if the hosted terms stop working for you, not as a way to cut the bill. How often does Convex change its pricing? There's no published schedule, so don't build a financial model on today's numbers staying fixed. Read the live pricing page before you commit, and re-check it whenever your usage grows or your plan renews. Setting spending limits and alerts also protects you if the rates or plan boundaries move. ## Related reading - [How to Choose a ClickUp Pricing Plan in 2026](https://www.activepieces.com/blog/how-to-choose-a-clickup-pricing-plan-in-2026) - [Activepieces vs Gumloop? Which to Choose in 2026](https://www.activepieces.com/blog/activepieces-vs-gumloop-which-to-choose-in-2026) - [Activepieces vs Langflow: Which to Choose (2026)](https://www.activepieces.com/blog/activepieces-vs-langflow-which-to-choose-2026) ## References - [Convex](https://www.convex.dev/pricing) - [Convex scalability research (GitHub)](https://github.com/MartinKalema/horizontal-scaling-convex/blob/dev/docs/convex-scalability-research.md) - [Makerkit](https://makerkit.dev/pricing-calculator/convex)Seats are predictable. Usage isn't, so a launch-day spike moves the bill more than a new hire does.