Base44 review 2026: the honest UK indie hacker take on the all-in-one builder and the platform lock-in trap

Base44 has spent the last twelve months doing the rounds on every UK indie hacker timeline. A CRM in under ten minutes. An internal tool ready before lunch. 250,000 users at the start of 2025, two million by spring 2026, $100M ARR by early 2026, and an $80M cash acquisition by Wix to top it off. The hype is real. The traction is real. So is the lock-in. This is the honest UK take on Base44 in 2026 - what it does brilliantly, what it costs in GBP, the platform trap nobody flags loudly enough, and a clean verdict on when to use it.

The hook: Base44's real claim

It is genuinely fast. The headline demo - prompt your way to a working CRM in under ten minutes - is not marketing-speak. People reproduce it daily. You describe the data model in English, name the integrations you want, and the platform spits out a deployed app at a real URL with a database, auth, and a usable admin UI. That is a different shape of speed from Cursor, Claude Code, Lovable, Bolt, or Replit, because none of those wire your hosting and database for you in the same gesture.

The traction backs the demo. 250k users at the start of 2025 to two million by spring 2026. ARR crossed $100M by early 2026. Wix acquired the company for $80M cash. For a tool that launched in late 2024, those are the kind of numbers you see when a product genuinely fits a moment. Credit where it is due - Base44 has solved the "I just want a working app today" problem better than almost anything else in the AI builder market.

What Base44 includes that you would otherwise wire up

This is the second reason it feels fast. Base44 is not just a code generator - it is a managed runtime. A typical SaaS MVP normally means stitching together six or seven services. Base44 ships them in the box:

• Hosting (your app is live the moment it generates)
• Database (managed, no schema ceremony)
• User authentication (sign up, sign in, password reset)
• Email sending (transactional and basic broadcasts)
• File upload (with managed storage)
• Image generation (LLM-driven)
• SMS (for notifications and verifications)
• LLM calls (for AI features inside your own app)

For a quick internal tool, client portal, or validation MVP, that is a serious amount of plumbing skipped. The half-day you would normally spend on auth setup, image config, email keys, and a hosting target is gone. You start with a deployed app and iterate from there.

GBP pricing for UK indie hackers

Base44 prices in USD. Converted at the working 2026 rate of GBP 1 = USD 1.27 (so each USD is roughly GBP 0.79):

Tier	USD/month	GBP/month (approx)	What you actually get
Free	0	0	Try the builder, limited app count, Base44 branding
Starter	20	16	Personal projects, more apps, your own domain
Builder	50	40	Higher limits, more integrations, more team-friendly
Pro	100	79	Heavier daily use, larger app footprint
Elite	200	158	Power users, biggest quotas, priority support

For most UK solo founders the working choice is Starter at GBP 16/month or Builder at GBP 40/month. Pro and Elite only justify themselves once you have a real, paying app on the platform.

The platform lock-in trap, named upfront

Here is the line you need to internalise before you commit a real project to Base44: you cannot export the backend.

You can prompt your way into a deployed app in an hour. You cannot prompt your way out of one. The frontend you could rebuild if pushed. The data lives in Base44's managed database. The auth lives in Base44's managed auth layer. The integrations are wired through Base44's plumbing. There is no "give me the Next.js + Supabase repo" button and no zip-export-and-host-it-yourself path. Once your app is live and your users are logging in, your business is sitting on infrastructure you do not own.

For a UK indie hacker shipping an MVP they expect to grow, this is the single biggest trade-off in the entire stack. Not a deal-breaker - plenty of products run on rented backends and do fine - but a decision, and most of the demos on Twitter / X are not framing it as one. The honest version: speed today, portability later. You buy ten minutes to a CRM. You sell the option to take that CRM elsewhere without rebuilding from scratch.

When Base44 is the right call

There is a real lane here. The lock-in matters less - sometimes not at all - in these cases:

• Internal tools. Team dashboard, ops console, bookings tracker. Operational data, small audience, "what if Base44 disappears?" answered by "we rebuild it next month."
• Client portals. A bespoke portal for a single client engagement. Project ends, portal retires. Lock-in is irrelevant if the lifetime is six months.
• Throwaway prototypes. Something you are demoing on Friday. Speed wins, infrastructure does not.
• Validation MVPs. You have an idea. You want to know if anyone wants it. Build the cheapest thing that proves demand. If it works, rebuild on portable infrastructure with validated requirements in hand. If not, you killed it for almost nothing.

In all four cases, Base44's speed-to-deployed is the right tool for the job. The lock-in is a non-issue because you never planned to be on the platform long-term.

When Base44 is the wrong call

The same lock-in becomes the central problem in these cases:

• Anything you expect to scale. A product you are betting your time and savings on. The day traction is real is the day you find yourself sat on someone else's database, with no migration path, hoping pricing and product direction stay aligned with yours forever.
• Anything that needs a custom backend. Heavy background jobs. Integrations the platform does not officially support. Performance-sensitive logic. The all-in-one offer assumes you are happy inside the box.
• Anything where data ownership matters. UK regulated industries - financial services, health, legal, anything touching sensitive PII - and GDPR-sensitive flows where you need to control where data lives, who processes it, and how it gets deleted on request. A managed black-box backend does not survive a serious DPIA.
• Anything you want to control end-to-end. Custom auth, bring-your-own database, self-hosted on your own infra. None of that is on the menu.

The pattern: the more your product looks like a real, growing business with sensitive data and custom requirements, the worse Base44 fits.

The post-Wix-acquisition question (flagged openly as speculation)

Wix acquired Base44 for $80M in cash. Worth flagging, because it changes the trajectory question for any UK indie hacker thinking about a multi-year bet on the platform.

Honest framing: nobody outside Base44 and Wix knows what the next 24 months look like. Optimistic read - Wix's distribution and infrastructure muscle accelerates Base44's roadmap. Pessimistic read - the usual acquisition pattern of pricing changes, feature deprecation, and founder departures on a 24-month vesting cliff.

This is speculation, openly. But the prudent posture is to not bet on Base44 being the same product, with the same pricing or independence, in 2028. Every platform you build on is a bet on the platform - it just becomes a sharper question after a cash acquisition.

The honest UK indie hacker verdict

Base44 is a brilliant validation tool and a risky long-term host.

If you are using it to prove an idea has demand before you commit real engineering time, it is one of the best tools in the AI builder market for that single job. Ten minutes to a deployed app, all the plumbing handled, a URL you can put in front of real users this week. At GBP 16/month on Starter, that is a ridiculous deal.

If you are using it to host the production version of an idea you have already validated, you are buying speed today by selling portability tomorrow. It can still be the right call, but it has to be a deliberate, eyes-open decision - not a default that snuck in because the prototype shipped fast.

The boring middle path most UK indie hackers should follow: use Base44 for validation, plan the rebuild for traction. Build the MVP on Base44. Get it in front of users. If the signal is there, take what you learned about the data model, the auth flow, and the user requirements, and rebuild on portable infrastructure - Next.js, Supabase, Vercel - using Cursor or Claude Code. The validation phase costs you GBP 16/month. The rebuild costs you a weekend. The lock-in trap is sprung only if you skip the rebuild.

What this means for your IdeaStack picks

IdeaStack's weekly UK opportunity reports ship a builder prompt written for a portable, AI-native stack - Next.js, Supabase, Stripe, Vercel, built with Cursor or Claude Code. That is deliberate. The builder prompts are designed for the version of the project you keep.

A sensible Base44 path layers on top of that: use Base44 for the validation phase. Stand up a quick, working version of the idea this weekend. Get it in front of the audience the report identified. If demand is there, run the canonical builder prompt on portable infrastructure. If not, you are out one weekend and a month of Starter - GBP 16 plus a Saturday. That is the cleanest way to use Base44 without falling into the lock-in trap: a validation accelerator, not a long-term home.