Molecule.dev

FAQ

Questions about molecule.dev — pricing, code ownership, exporting, privacy, and where to get help.

Is there a free tier?

Yes — you can start building for free, including real sandbox time, and scale as the app grows. Current limits and paid tiers are on Pricing.

Who owns the code?

You do. The output is a conventional TypeScript monorepo in your project, written to your account. The @molecule/* packages it builds on are Apache-2.0 open source. Details: Licensing.

Can I leave / self-host?

Yes. Download the project, push it to your own git (npx mlcl git push works platform-mediated; your own remote is always allowed), and run it anywhere Node runs — the scaffold is standard npm workspaces. A full export bundle (source, database dump, env files, run instructions) is available per project, and the CLI’s local workflow never needed molecule servers in the first place.

Can I bring an existing app?

Yes — npx mlcl import repos --project <id> (or the IDE’s import) brings a repo into a project sandbox, npx mlcl sync <dir> keeps a local tree mirrored in, and npx mlcl agent init makes any coding agent molecule-aware in your own checkout without moving anything.

Is my code private?

Your projects are yours; molecule does not train models on private content. What the platform does and doesn’t do with data is stated plainly on Security, with the legal side in Privacy and the DPA.

Which AI models does it use?

Molecule is provider-swappable by design and runs frontier models from several hosts (the catalog is public: npx mlcl models). You don’t need your own API keys for the IDE’s built-in AI; paid plans can bring their own for app code through the AI bonds.

Where do I get help?