Building with Pikku

This page is for the technically curious — if you're not a developer, you can safely skip it. The one thing worth taking away is this: Pikku Studio Cloud is built on Pikku, an open-source framework, which is what guarantees you're never locked in. If you ever bring in a developer, this is where they'll start.

Simple diagram: a "Pikku Studio Cloud" box sitting on top of an "Open-source Pikku (pikku.dev)" foundation box, with a side arrow labeled "Nothing to eject — your code is already standard Pikku you can take and run yourself."

What Pikku is

Pikku is an open-source TypeScript framework. Its defining idea: you write one function, and it works across every transport — HTTP, CLI, internal RPC — with no rewiring. You don't reimplement the same logic three times for three entry points; you write it once and wire it wherever you need it.

Pikku Studio Cloud is the hosted platform built on top of that framework. Pikku Studio Cloud adds the deployment, the console, the AI builder, and the monitoring — but the code underneath is plain Pikku.

You own everything — there is nothing to eject

Because Pikku Studio Cloud sits on an open-source foundation, your project is never trapped inside it.

If you ever leave Pikku Studio Cloud, you keep your functions, workflows, agents, credentials, and data. The only thing you give up is the pretty Pikku Studio Cloud UI. Everything else is standard Pikku code you can run yourself, anywhere.

That's the whole no-lock-in promise, made concrete. There is no eject command, because there is nothing to eject: the repo is plain Pikku from the first commit. Clone it and host it on your own. Nothing about your app depends on Pikku Studio Cloud being in the picture.

Where developers learn the framework

This page intentionally doesn't re-document the framework. The full Pikku docs — wiring, runtimes, middleware, workflows, agents, everything — live at pikku.dev. That's the right starting point for any developer joining your project.

The takeaway

Pikku Studio Cloud sits on open-source Pikku. You're never locked in — the repo is ordinary code you can clone and run without us — and your developer learns the framework at pikku.dev.

Where to go next

• Pikku framework docs — the complete reference for the open-source framework.
• CLI reference — the optional command-line tool for developers and CI.
• FAQ — straight answers on lock-in, exporting, and self-hosting.