Creating a sandbox

Requesting and configuring a sandbox for your project.

Creating a sandbox spins up a fresh, private copy of your whole app to experiment in. It takes a few clicks, it matches your project automatically, and you can make as many as you want. There's no setup to wrestle with and nothing to configure by hand unless you want to.

Annotated screenshot of the "Create sandbox" flow showing the name/options form and a prominent Create button, callout: "Spin up a fresh isolated environment in a click."

How to get one

From your project, open the Sandboxes area and choose to create a new sandbox. Give it a name so you can tell your sandboxes apart later, then confirm. Pikku Studio Cloud does the rest — it builds the environment for you and lets you know when it's ready.

You don't have to configure anything

A sandbox is created to match your project automatically. It mirrors your app's frontend, backend, and data setup, so it behaves like the real thing from the moment it starts. You can rename a sandbox or manage it later, but there's no required configuration to fill out just to get going.

Does it cost anything?

No — sandboxes are free to create on every plan. Make a fresh one for each experiment, spin up several in parallel, throw them away when you're done. You're never penalized for creating sandboxes.

Sandboxes are free to create on all plans. The only thing you ever pay for is the usage your live app actually consumes — see the FAQ for how billing works.

How long until it's ready?

A new sandbox takes a short moment to build and start. Once it's running you can open it, work in it, and watch your changes in the live preview. (Later on, sandboxes can sleep when idle and may take a moment to wake — that's covered next.)

The takeaway

You can create your own full-stack test environment in a few clicks, it configures itself to match your project, and it never costs you anything to spin one up.

Where to go next