FAQ
Common questions and answers.
Short, straight answers to the questions people ask before they commit. If yours isn't here, jump to the relevant doc from any answer below — or reach out, see the bottom of this page.
What will this cost me — could I get a surprise bill?
No surprises. Pikku Studio itself is free. You pay only when you deploy to Pikku Studio Cloud, and the amounts are always in credits. Signing up puts free credit in your account; after that you pay as you go, or choose a plan with monthly credit, which is used first. You can watch what your app costs as it runs, and the rate for each thing is shown to you up front. The AI is the one part you bring: your own provider key, or a model on your own computer. See the quick start to get going.
Is there a free plan?
The Free plan is pay as you go on Pikku Studio Cloud: the sign-up credit, then top-ups, up to five projects and every feature except teams. Indie adds teams, your own domain and monthly credit. Business adds company sign-in (SSO), and Enterprise will run inside your own cloud account, coming soon. Pikku Studio itself is free whatever you choose, and the Pikku framework underneath is MIT-licensed, so you can run what it builds on your own servers at no cost to us.
Am I locked in? Can I export my data or host it myself?
You're never locked in, and there is nothing to eject — your functions, workflows, agents, credentials, and data are already standard open-source Pikku code in your own repository, from the first commit. Export your data whenever you like, and self-host if you ever want to leave. The only thing you give up by leaving is the Pikku Studio Cloud UI.
Does the AI ship code without my approval?
No. Work happens in a private sandbox that has no route to your live app, and putting it in front of customers is a separate step that waits for your approval. You can hand that decision over — turning on auto-deploy for a stage lets releases go out without stopping — but that is a choice you make, and the riskiest releases keep asking anyway. See Publishing.
What if the AI writes bad code — can I undo it?
Yes — one-click rollback to any previous version, with zero downtime. Pikku Studio Cloud redeploys the previous version for you; since it's already built, there's nothing to rebuild, so the switch is quick. See Deployments.
Are my secrets and data safe?
Yes. Secrets are encrypted and kept private — they're never exposed in your project's code or to other tenants. See Secrets.
Do I need to know how to code?
No. You can build and deploy entirely through the browser console by describing what you want. Developers can drop down to the CLI or the underlying framework if they want to, but it's not required. See the Builder.
Where does my code run — and what does it cost to run?
Pikku Studio Cloud auto-routes each function to the right place. Pure, lightweight functions run on Cloudflare Workers that scale to zero — meaning they cost nothing when nobody's using them. Heavier work runs on Containers. You don't choose; Pikku Studio Cloud decides per function. See pikkustudio.config.json.
Do I have to use the terminal?
No. Everything is available in the browser console. The CLI is optional, for people who prefer the terminal or want to script CI. See the CLI reference.
What's the "Labs" section in my project?
Labs is where new, experimental features show up before they're final. It's opt-in — nothing there affects your live app unless you choose to use it — and what's inside changes as we try things out. Treat it as a preview: handy to explore, but not yet covered by the rest of these docs.
Still stuck? If your question isn't answered here, reach out via the contact page — we're happy to help.