Bolt.new Clone App - White-Label AI Code Generation Platform

Yes. You launch under your own branding and commercial terms. The product replicates common AI-builder patterns rather than any protected asset, and you set your own pricing, model selection and policies.

The Miracuves Bolt.new Clone starts from $3,399 for a launch-ready white-label deployment. Final scope varies with provider strategy, credit pricing design, integrations and infrastructure.

Six days from our side. The platform is ready-made, so our work is rebranding it and deploying to your server – that is done in under six days. What extends the calendar is anything we need from you: brand assets, hosting access, provider API keys, and decisions on plan structure and credit pricing.

No. The platform is browser-first, with packaged Electron desktop builds for macOS, Windows and Linux. There is no Android or iOS application. Native mobile is available as custom development if your roadmap needs it, but we would rather be direct about what ships than let you find out later.

In the user’s browser. WebContainers provide a complete Node.js environment client-side, so npm installs, shell commands, builds and previews all execute locally. Your servers only relay AI requests and store platform data. For teams with IP or compliance constraints, this is usually the deciding factor.

Each model has input and output credit rates configurable per plan. After a generation completes, the platform computes cost from the actual token counts, validates the balance server-side, deducts, and writes an append-only ledger entry recording the amount, resulting balance, model and description. Enterprise accounts bypass metering entirely.

It handles the subscription model – tiers, entitlements, credit allocations and the full transaction ledger. It does not process payments. There is no built-in checkout, so connecting Stripe or another provider is operator work at deployment. The documentation states this plainly and so do we.

Yes. Use the Ollama provider for locally hosted models, configure any OpenAI-compatible endpoint through provider settings, or expose additional models through the OpenRouter integration. Adding an entirely new provider is two files – a class extending the base provider contract, and an entry in the registry.

A Content-Security-Policy header and HSTS, both of which are deployment additions rather than defaults. Demo accounts disabled. Your own provider API keys and a strong admin password. If you are billing, a payment provider with webhook verification. At scale you will also want Redis-backed rate limiting, database and key encryption at rest, and persistent audit logging. Every one of these is named in the documentation as configuration required.

It ships with a formal VAPT and compliance report mapping OWASP Top 10 (2021), NIST CSF 2.0 and SOC 2 control objectives, alongside a developer security handbook. The assessment identifies genuine strengths – parameterized queries throughout, SHA-256 hashed session tokens with 256 bits of entropy, timing-safe admin comparison, SSRF protection on the git proxy, server-side credit validation and separate admin sessions – and it is equally explicit about what remains configuration required. You get both halves, which is what a reviewer actually wants.

Yes. You receive the complete Remix and React web application, the Express authentication proxy, the Cloudflare workerd runtime, the PostgreSQL schema across six tables, the provider abstraction layer covering all 22 providers, the Electron desktop packaging and every integration service – with full ownership to modify and extend.