Replit Pricing 2026: Plans, Credits and Real Cost
Oct 29, 202616 min read
Replit pricing today: direct answer and plan table
Direct answer
You are not buying an unlimited seat with Replit's monthly plan fee. You are buying a credit allowance.
Core at $20 covers light users, and you only move up to Pro at $100 when overage charges on Core would cost more than that jump, which means you'll stay on Core until the cost cliff forces an upgrade, much as you would when comparing usage-based automation tools like Activepieces.
Replit is an AI app builder with hosting: you describe an app, an agent writes it, and Replit runs it for you. Each agent run draws from your credits.
Think of a support queue where every reply costs a token. A quiet week fits the plan, and a week of back-and-forth on one stubborn bug doesn't.
Stay on Core while overage quietly stacks up, and that is the wrong call. The right call is the cheaper plan until your own usage proves otherwise.
Think of a support queue where every reply costs a token. A quiet week fits the plan, and a week of back-and-forth on one stubborn bug doesn't.
Plan table checked against replit.com/pricing
The table below was checked against replit.com/pricing on 2026-10-29. It shows what each tier costs and how the allowance is framed. Read the credits column as the thing you're really buying, and the price column as what it costs to hold that allowance.
| Plan | Monthly price | Annual-billed monthly price | Included credits | Key limits |
|---|---|---|---|---|
| Starter (free) | $0 | $0 | Small free allowance | Agent use is capped by the allowance, so it suits trying the tool, not building daily |
| Core | $20 | $18 | Monthly credit allowance | Agent runs draw down the allowance; overage is billed once it is used up |
| Pro | $100 | $90 | Larger monthly credit allowance | Same credit model at a higher ceiling, aimed at heavy or shared use |
| Enterprise | Quoted individually | Quoted individually | Set by contract | Terms are negotiated, not published |
Pay yearly and Core saves $2 a month, so $24 a year, while Pro saves $10 a month, so $120 a year.
Only pay yearly once you've kept a plan through a few normal months, because a prepaid year on the wrong tier is a refund ticket you won't enjoy writing.
Because a credit pays for agent work, a short, clear request costs little and a vague one that needs five rounds of fixes costs far more.
Activepieces meters differently: its Free plan includes 1,000 credits a month and unlimited flows, and unlimited flows apply on every paid plan too.
Count runs, not months, and the next section shows where that count crosses the line.
If you are running this arithmetic for your own team, see what the same workload costs on Activepieces.
Which Replit plan fits three everyday uses
Count your runs against these three builds. The cheapest paid plan covers a solo prototype and a small hosted app at light use, and a two-person team build is where the next plan up starts to win.
The table shows each build's recommended plan and what the bill does as runs climb. Take from it that the fee barely moves while the overage column does, so the plan is only right until overage passes the fee gap.
| Build | Recommended plan | Light bill | Moderate bill | Heavy bill | Next plan up is cheaper when |
|---|---|---|---|---|---|
| Solo prototype | Cheapest paid plan | Fee only | Fee, small overage | Fee plus overage close to the next plan's fee | Overage alone matches the fee gap |
| Small hosted app | Cheapest paid plan | Fee only | Fee, noticeable overage | Fee plus overage above the fee gap | Overage alone matches the fee gap, usually in a busy launch week |
| Two-person team build | Next plan up | Fee only | Fee only | Fee, small overage | Overage on the cheaper plan matches the fee gap, which comes sooner because two people share one allowance |
Why each build gets its plan
Each row below says why, and what a wrong pick costs.
For a solo prototype or internal tool, stay on the cheapest paid plan. A wrong upgrade here means paying a higher fee every month for runs you never make.
Picture someone building an internal form that routes support tickets: a few long sessions, then days of nothing. The allowance covers that, and one bad afternoon of retries costs less than the fee gap.
For a small hosted business app, the cheapest paid plan also fits, but watch your busiest week. Fixing a customer-reported bug means many short agent runs in a row, and an angry email makes that worse because you retry fast.
A wrong downgrade shows up as a surprise overage bill in the very week the customer is waiting.
For a two- or three-person team, start one plan up. Two people drawing on one allowance burn it roughly twice as fast, and you won't notice until a teammate gets stuck mid-task.
Paying the larger fee early costs you a known amount. Hitting overage mid-sprint costs an unknown one, plus the lost time.
When to move up a plan
Upgrade when your overage in a typical month equals the fee difference between the two plans, so your monthly bill becomes identical whether you switch or stay. Below that, stay put. Above it, every extra run is a payment you could've avoided.
Check this against your last full month of runs, not your best or worst week.
Replit's strong case for cheap and predictable pricing
For a light user, Replit is cheap and predictable because the plan fee's flat, credits're included, and a spending cap stops the bill at a number you chose. Run your last full month through that and see if it holds.
Think of the angry email you most want to avoid: "Why is this bill three times what I expected?" The pro-Replit case is that the plan's built so you rarely have to answer it. These are the strongest points in its favour:
- The plan fee's flat, so the first part of your bill's the same every month and you can budget it like any other subscription.
- Credits're included in that fee, so a light user who stays inside the allowance never sees a usage charge at all.
- A spending cap turns overage from an open-ended risk into a limit you set yourself. The worst case is the number you picked, which matters more than the average case if you're the one explaining the invoice.
- Agent time's priced against a developer at $75 to $110 an hour. If one agent run replaces an hour of that work, the credits it used are small next to what you would otherwise pay, so the comparison favours Replit even when you pay some overage.
- The figure that would disprove all of this is the overage rate per agent run, set against the price gap to the next plan up. If your monthly overage regularly exceeds that gap, you're paying more to stay on the cheaper plan than you'd on the dearer one, and the predictability argument no longer saves you.
Get this wrong and it costs you money every month until you notice. Get it right and you save very little in any single month, so the check is worth doing before you commit to a plan rather than after the first surprising invoice.
Put your own run count against that test next.
Watch for hidden Replit costs and limits
Count your runs and you have only half the bill, because four extras sit outside the plan fee: agent usage past included credits, deployment compute, databases and storage, and seats.
Once credits run out, you pay per token, and writing costs several times more than reading. Dataku's price chart shows the pattern across older frontier models, as input then output per million tokens.
Per Dataku, GPT-4 Turbo was priced at $10 to $30, Claude 3 Opus at $15 to $75, and GPT-4o at $2.50 to $10, meaning your invoice depends heavily on both your choice of model and the scale of your workload.
In Dataku's chart, Claude 3.5 Sonnet was $3 to $15, and DeepSeek R1 $0.55 to $2.19, so even at Sonnet's floor you were paying more than DeepSeek's ceiling.
In every case, output runs three to five times input. An agent that writes a lot of code per run therefore costs more than its prompt length suggests, and overage climbs faster than your run count.
Replit deployment, database and storage costs
Whether or not anyone visits it, a deployed app bills for compute. Replit's billing notes show Reserved VM rates before and after the cut, per hour: 0.5 vCPU, 2 GiB: $0.028 down to $0.0208, about $20 to $15 over a 730-hour month, saving roughly $60 per year on each always-on machine of this configuration.
- 1 vCPU, 4 GiB: $0.055 down to $0.0486, about $40 to $35, providing $5 in monthly savings per reserved machine on this tier.
- 2 vCPU, 8 GiB: $0.11 down to $0.0694, about $80 to $51.
On the biggest machine the cut's largest, so one always-on app can cost more than the plan fee.
Databases and storage are billed separately from the plan, so check them before you move a prototype into production. Seats add to this: each person you add is another user spending on the same account.
Spending limits and alerts
It is easy to read a settings page as a cost control when it's not.
A project dialog such as the one for Secret Gadget Labs has a Max Concurrent Jobs field set to Default (5). The field's described as the maximum number of flows that can run at the same time.
The concurrency cap limits how much work runs in parallel, not how many dollars it costs. Five jobs running slowly for a month still add up, so don't treat a concurrency cap as a budget.
A spending limit's the setting that stops overage at a figure you chose. Set it before the first heavy week, and set an alert below it so you see the bill approaching rather than reading it afterward.
Worth checking against a plan that does not meter every step: one credit covers a whole run on Activepieces.
Replit versus Lovable, Bolt and Cursor on price
Because Replit's overage keeps billing where the others're built around stopping or topping up, the cap you just set matters more here than on these three rivals. Compare what happens at the limit before you compare sticker prices.
Entry price and usage unit side by side
The table below shows what each cheapest paid plan actually meters. Read the usage column first: a wrong guess about the unit's how a 'cheap' plan turns into a surprise invoice.
I've mostly left dollar prices out because they change, so take them from each vendor's pricing page on the day you buy.
| Plan | Usage unit | Hosting | Behaviour at limit |
|---|---|---|---|
| Replit Core | Credits spent by agent runs | Built in on Replit | Overage is charged unless you set a cap |
| Lovable Pro (100 credits) | 100 credits | Publishing included | Buy more credits or move up a plan |
| Bolt Pro ($25, 10M tokens, rollover) | 10M tokens, unused ones carry over | Hosting built in | Buy more tokens or upgrade |
| Cursor Pro | Included usage inside an editor | None; you deploy elsewhere | Depends on your spending-limit setting |
Only a few features here reward a light month: rollover on Bolt and on Replit Pro, where unused credits carry over for two months. The others reset, so unused allowance is simply lost.
Replit hosting and overage costs compared
Hosting decides whether the plan fee's the whole bill. Replit, Lovable and Bolt run your app for you, so you're paying for one place.
Cursor edits code and hosts nothing, so a Cursor bill's only half the cost of a live app, and the other half arrives from whatever host you choose.
Guess wrong on overage and it costs you most. A tool that pauses at the limit costs you a stalled afternoon. A tool that keeps charging costs you money you didn't plan to spend.
Check the vendor's own page for how each handles it before a deadline week, not during one.
Which tool fits which buyer on price
If you build a few small apps a month and want one bill, Replit Core's enough, as long as the cap's set. If your usage is steady and you dislike metered surprises, Lovable's fixed credit count's easier to predict.
If your months swing between busy and quiet, Bolt's rollover suits you. If you already write code and deploy it yourself, Cursor fits, and hosting's a separate line in your budget.
Connect a Replit app to business tools with Activepieces
Once the app's built, send its data to your CRM, email or Slack through a webhook-fed Activepieces workflow, not through more agent runs. That keeps the repeat work off your Replit credit meter, since an Activepieces run costs 1 credit however many steps it has.
When agent credits are the wrong way to build integrations
Take a contact form on your Replit app. Every submission must reach the CRM and ping someone in Slack.
If you ask the agent to build and rebuild that wiring, each attempt spends credits, and a bug costs you twice: once in credits, once in a lead nobody saw. A customer who wrote in and got silence's the expensive mistake.
Every time, a workflow tool runs the same steps and bills by its own allowance. Activepieces gives 1,000 credits a month on Free and 10,000 on Plus at $20. Team has 50,000 at $200.
Its CRM, email and Slack steps come from the 746 integrations in its MIT-licensed open-source monorepo, counted directly from packages/pieces/community rather than quoted as a marketing figure.
So Free covers a small form, and Plus gives ten times the room for $20. Team costs $4 per 1,000 credits against Plus's $2, so move up only when Plus runs out, not before.
A webhook-to-workflow setup
Read those allowances against your expected submissions per month, because that count tells you which plan you need. The setup below's the same on every plan.
- Add a webhook call in the Replit app, so that each form submission sends its fields as a POST request to a URL.
- Create an Activepieces flow and choose Catch Webhook as the trigger. It gives you the URL for step 1.
- Map the incoming fields to the CRM step: name to name, email to email, message to notes.
- Add an email or Slack step that tells a named person a new lead arrived, with the message text included.
- Test with a sample payload. Use an ugly one, such as a long message with odd characters, because that's what a real angry customer sends.
- Publish the flow, then submit one real form and confirm the record and the alert both show up.
After that, the agent only touches the app when the app itself changes. Every later submission runs through the workflow, and your credit use follows the volume of leads, not the number of times you rework the wiring.
Frequently asked questions
Free tier and unused credits
Because credit use follows lead volume, the questions left are what you pay before the first run and how to cap it.
There is a free tier, but it limits how much the agent can do, so it suits testing one build and not handling real leads.
Treat it as a trial: if your workflow stalls mid-week because the allowance ran out, a customer's submission waits until you act. Check the pricing page for what the free tier includes today.
Don't plan around unused credits rolling over on Core; on Pro they carry over for two months., and assuming credits carry forward's the costly mistake: you size your plan for a quiet month, then find the allowance reset.
Read the credit terms on the pricing page before you rely on leftover credits.
Changing or cancelling your plan
You can change or cancel from your account's billing settings. Before switching from monthly to annual, check whether the change takes effect now or at your next renewal, and whether the annual price's refundable.
Paying a year up front for a plan you outgrow in a month costs more than the monthly premium you were avoiding.
Capping what Replit can charge
To stop Replit charging more than your plan, set a spending limit in your billing settings, then confirm it with a real test. A limit you've never tested's a guess. Work through these steps on Monday, in this order:
- Choose the cheapest paid plan that covers your expected lead volume. Move up only when overage would cost more than the next plan.
- Set a spending limit before you build anything, so a runaway task stops at a number you picked and not at your card's ceiling.
- Build one real workflow, such as your lead form, and note the credits it used from start to finish. That figure, multiplied by your weekly volume, tells you whether the plan fits. A guess from a demo doesn't.
- Re-check the pricing page against the date you wrote this down. Plans and credit terms change, and a month-old note can be wrong.
Repeat step four whenever your bill surprises you, and before every renewal.
Related reading
References
Running the numbers
See what the same workload costs here.
Free forever plan, and every paid plan self-hosts at no extra cost.
See pricing Talk to sales
