Questions about molecule.dev: pricing, code ownership, exporting, privacy, and where to get help.
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.
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.
Yes. Download the project, push it to your own git (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 does not need molecule servers.
Yes. mlcl import repos --project <id> (or the IDE’s import) brings a repo into a project sandbox, mlcl sync <dir> keeps a local tree mirrored in, and mlcl agent init writes the conventions into any coding agent’s setup in your own checkout without moving anything.
Your projects are yours; molecule does not train models on private content. The platform’s data practices are on Security, with the legal side in Privacy and the DPA.
Molecule is provider-swappable by design and runs frontier models from several hosts (the catalog is public: 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.