The free tier
The free tier is designed to let you try Base44 end-to-end without a credit card — build an app, iterate with prompts, and publish to a Base44 subdomain. Generation and deploy volume are rate-limited so heavy users hit the ceiling within a serious afternoon of work. That constraint is deliberate. The free tier answers 'does this platform work for what I'm trying to do', and the paid tiers answer 'now I want to actually ship'. Treat the free tier as an unlimited-duration trial rather than a production plan.
How generations are counted
A generation is one prompt-driven code change. When you type an instruction and Base44 edits files in response, that counts against your monthly budget. Purely conversational messages that do not modify code — asking Base44 to explain a piece of the generated app, for example — typically do not count. Editing a single file counts the same as editing several files inside the same prompt, so batching related changes into one clear prompt is more efficient than issuing many small ones. If you routinely find yourself close to the ceiling, the fix is usually prompt discipline rather than a tier upgrade.
What the paid tiers unlock
Paid tiers layer on four kinds of upgrade. First, a higher generation budget — more prompts per month before you hit a rate limit. Second, more concurrent apps in your workspace, which matters if you're building a portfolio of small tools rather than one big product. Third, custom domain support and richer hosting features. Fourth, team-oriented features like shared projects, per-seat billing, and priority generation queues that keep response times steady during peak hours when free-tier traffic slows down.
When to upgrade
- You've hit the free-tier generation cap partway through iterating and the ceiling is now blocking real work rather than exploration.
- You want to publish to a custom domain — this is almost always the first paid-tier feature people actually need.
- You're collaborating with a teammate on the same project and want shared access with sensible roles.
- You're building against Base44 during peak hours and need priority queueing to keep generation latency low.
- You're running multiple projects concurrently and the concurrent-app limit is forcing you to archive work you still want live.
Priority generation, in practice
The priority queue is the paid-tier benefit that surprises people the most. During peak hours — typically weekday afternoons US-time — free-tier generations queue behind paid ones, which can turn a 20-second generation into a two-minute wait. If you're using Base44 casually the delay is fine. If you're using it as part of a professional workflow, the queue difference alone often pays for the tier. Watch the live dashboard on base44.health during a busy afternoon to see the effect in real time.
Team seats and shared projects
Higher tiers add per-seat billing and shared project access. Each teammate gets their own login and their prompts count against the team budget rather than an individual one. Role controls let you scope who can Publish versus who can only iterate in preview. If two people are collaborating on the same app, this is dramatically less painful than sharing a single login — which was the informal workaround before team tiers existed.
Custom domains and hosting features
Custom domains, higher bandwidth allocations, and richer analytics ship on paid tiers. Custom domains alone are usually the trigger for upgrading because a base44.app subdomain feels fine for prototypes but not for a product you want to charge for. The upside of Base44 handling this rather than a separate host like Vercel or Netlify is that you get one bill and one dashboard for the whole stack.
Always check the source
Pricing changes. Every specific dollar figure or generation count in a third-party article is a snapshot in time and will be wrong at some point. Confirm current numbers at base44.com/pricing before committing to a tier — the framing above describes the shape of the tiers, not the exact numbers. When in doubt, start on the free tier, watch which limits you hit first, and upgrade to the smallest tier that comfortably covers your actual usage.
A monthly cost example for a small SaaS team
Consider a three-person SaaS team shipping an internal customer-portal app on Base44. Two builders iterate daily and consume roughly 400 to 600 generations each per month between UI tweaks, backend endpoints, and bugfixes. The third person is a product manager who mostly reviews the preview URL and occasionally requests small copy changes — call that another 100 generations. Storage sits around a few gigabytes of uploaded assets and the app's database holds tens of thousands of rows for user records, workflow definitions, and audit logs. In this shape a mid-tier paid plan usually lands well under a hundred dollars per month all-in, and the priority queue keeps generation latency predictable during weekday afternoons. Compare that to the loaded cost of having an engineer stitch together a hand-rolled auth service, a Postgres host, an object store, and a CI pipeline, and the paid tier looks like the cheap line item on the balance sheet rather than the expensive one.
A worked estimate for an agency running multiple client apps
An agency running five active client apps has a different cost profile than a single-product team. Each client app tends to be smaller in generation volume — say 150 to 300 generations per month once it's in maintenance mode — but the agency needs multiple concurrent projects live, per-project custom domains, and per-project secrets isolation so credentials from one client never leak into another. That combination pushes agencies toward the higher paid tiers or the team tier where the concurrent-app limit is generous and shared workspaces let a small team of builders swarm on any client at any time. The rough shape is: budget for a team seat per active builder plus a comfortable generation ceiling that covers a heavy client onboarding month, and treat custom-domain support as non-negotiable because client apps almost never ship on a base44.app subdomain. Agencies that skimp on tier here usually re-upgrade within a quarter once the concurrent-app limit forces them to archive a client's app the moment a new one starts.
How Base44 pricing compares to Replit, Lovable, and Bolt
Every AI app builder in this category — Replit Agent, Lovable, Bolt, and Base44 — sells roughly the same shape of plan: a free tier for evaluation, a solo paid tier for individual builders, and a team tier that adds shared workspaces and priority queueing. Prices at each rung tend to cluster within a similar band because they're all pricing against the same underlying LLM inference cost. Where they differ is what's bundled: Base44 leans harder on managed hosting and a full managed backend, so a paid tier tends to cover more of the deploy story than the equivalent Replit or Bolt tier where hosting is more of an à la carte add-on. Lovable sits closest to Base44 in shape but weighs the tiers slightly differently. The practical takeaway is that dollar-for-dollar comparisons between tiers are misleading — compare what's inside the tier, not just the sticker price, and re-check every few months because all four platforms iterate their pricing frequently.
When to upgrade from Free to Pro to Team to Enterprise
The upgrade path follows a predictable staircase. Move from Free to Pro the first time a generation cap blocks real work rather than exploration, or the first time you need a custom domain — whichever happens first, and for most builders those two events happen within days of each other. Move from Pro to Team when a second person joins the project full-time and you find yourself sharing a single login or Slacking screenshots of the preview URL back and forth. Move from Team to Enterprise only when you actually need the Enterprise-specific features: single sign-on with a corporate identity provider, audit logs surfaced for compliance, custom data-residency guarantees, or a signed contract with an SLA. Enterprise tiers are priced for procurement conversations rather than individual builders, so upgrading before those specific needs surface just burns budget you could put into generations or seats.
Hidden cost considerations
The sticker price on a tier is rarely the full monthly bill. Watch for: custom-domain add-ons if you're running many domains from one workspace, additional storage charges once uploaded assets or database rows push past the tier's included quota, per-row database limits that can force an upgrade before the generation ceiling does, file-size limits on individual uploads that surprise you the first time a user tries to attach a 100MB PDF, and AI generation credits for features inside your app that themselves call an LLM. That last one bites the hardest: if your generated app has a 'summarise this document' feature powered by Base44's LLM integration, each end-user invocation is billed separately from your builder-side generation budget. Model the app's expected LLM usage before launch, cap it if your business model doesn't recover the cost, and set alerting on the underlying usage counter so a runaway loop doesn't quietly rack up a five-figure bill overnight.
Which plan should I choose? A short checklist
- Stay on Free while you're evaluating — the free tier is generous enough to answer 'does Base44 fit my problem'.
- Upgrade to Pro the first month you hit the generation ceiling or the first time you need a custom domain, whichever comes first.
- Upgrade to Team when a second full-time collaborator joins, or when you're juggling more concurrent apps than the Pro tier allows.
- Consider Enterprise only for concrete Enterprise-only needs: SSO, audit logs, data-residency, or a contractual SLA.
- Re-evaluate every quarter. Usage shape changes as an app matures, and dropping to a smaller tier when you're consistently under quota is a completely legitimate move.
- Always confirm current numbers at base44.com/pricing before committing — this article describes the shape of the tiers, not the exact dollar figures on any given day.