Bolt.new vs Meku

Bolt.new supports Figma and screenshot import, letting a beginner fix a bad result without touching code, while Meku's own pages state it does not support design import. Both tools run an autonomous build agent. Bolt.new's starting plan caps usage at 300,000 tokens per day and 1,000,000 tokens per month before any charge applies. Meku's starting plan caps usage at 100 credits per month before any charge applies, a much tighter monthly allowance with no daily figure. Once you do pay, Meku's plan costs $22/mo and Bolt.new's plan costs $25/mo. That small price gap does not offset the missing design import or the tighter starting allowance.

Both tools export the full project as code, satisfying one hard filter equally. The other, real GitHub sync, favors Bolt.new: it states bidirectional sync plainly, while Meku's own pages give conflicting claims about whether the feature is live, leaving developers unable to rely on it. Both let you self-hostself-host - Run the software on your own servers instead of the vendor’s cloud. the generated output. On the backend, Bolt.new documents a native Supabase integration alongside the bring-your-own database, while Meku documents a plainer bring-your-own Supabase setup. With code export tied and GitHub sync clouded by Meku's own inconsistent documentation, Bolt.new is the safer pick for engineers who want the AI to scaffold and get out of the way.

Bolt.new's free plan caps at 300,000 tokens per day and 1,000,000 tokens per month, and Bolt.new's unused credits roll over. Meku's free plan caps at a flat 100 credits per month, and Meku confirms unused credits do not roll over. That gives Bolt.new more room to actually build before hitting a wall, the biggest factor for trying a tool before paying. Meku's cheapest paid plan costs $22/mo, or $12/mo when Meku is billed annually, undercutting Bolt.new's cheapest paid plan at $25/mo. Meku also includes a custom domain on every plan including Free, where Bolt.new reserves that for Pro and above. Close on the secondary points, but the free tier itself favors Bolt.new.

For a real data backend, both rely on a bring-your-own Supabase setup, with Bolt.new's documentation adding a native integration for auth on top, which matters for the role-gated access an internal tool needs. Bolt.new also offers SSO on its Enterprise plan, a fact Meku does not have on record. Meku counters with a named integrations list, GitHub, Figma, and Supabase, giving ops teams a documented way to reach systems the business already runs, something Bolt.new has no equivalent fact for. Both support team collaboration. With SSO and a more detailed backend integration tipping it, Bolt.new edges out Meku's documented integrations here.

Neither tool is built for mobile. Meku explicitly states it has no mobile output, and Bolt.new does not claim any mobile output either, its documented stack is full-stack JS/TS web projects, the same web-only shape as Meku's React and Tailwind output. Both let you self-hostself-host - Run the software on your own servers instead of the vendor’s cloud. the generated output and both run an autonomous build agent, but those points do not help a builder targeting a phone rather than a browser tab. With one tool outright confirming no mobile output and the other simply having nothing to show for it, this is a wash for anyone who needs a native app.

Builders who want to run the app builder itself need facts about running offline, the license, and paying through their own API keys instead of a subscription. Neither Bolt.new nor Meku publishes any of those: both are hosted products with no local-first mode, no open license, and no bring-your-own-key billing on record. The one fact both share is that you can self-hostself-host - Run the software on your own servers instead of the vendor’s cloud. the generated output, which both Bolt.new and Meku confirm as yes. With no vendor facts separating them on the core requirement of running the builder itself, this comes down even.

Figma and screenshot import is the core requirement for going from a design file straight to a front end, and Bolt.new supports it while Meku's own vendor pages state it does not. Output stack differs too: Bolt.new produces full-stack JS/TS web projects while Meku is built specifically on React and Tailwind, a narrower but still web-focused stack. Both tools support collaboration and versioning with rollback, so a team can work together and step back from a bad change either way. But those shared strengths do not close the gap on the one capability this use case is built around, and only Bolt.new has it.