pikkustudio.config.json
All supported fields in the project config file.
pikkustudio.config.json is the file that controls how Pikku Studio Cloud deploys your project. In practice you rarely open it — the platform and the AI builder manage it for you. This page is here for the moments you want to understand or override what it's doing, especially the one field most worth knowing about: deploy.
Do I edit this by hand?
Usually no. Pikku Studio Cloud (and the AI builder) keep this file in sync with your project automatically, so the common path is to never touch it. You'd edit it only to deliberately override a default — and even then, auto is a safe place to leave things.
If you do get a field wrong, you'll find out before anything goes live: a deploy plan previews the change and surfaces problems first, so a bad config doesn't quietly break production.
Supported fields
| Field | What it does | Default |
|---|---|---|
deploy | Controls where each function runs — 'auto', 'worker', or 'server'. See below. | 'auto' |
The deploy field
This is the field that matters. It tells Pikku Studio Cloud where your code should run:
'auto'(default, recommended). Pikku Studio Cloud decides per function. Pure, lightweight functions go to Cloudflare Workers, which scale to zero — meaning they cost nothing when idle. Heavy work (think Playwright or ffmpeg) goes to Cloudflare Containers, which have the muscle for it. You don't have to know which is which; Pikku Studio Cloud routes each function to the right place.'worker'. Forces everything to the edge (Workers). Use only if you know your functions are all lightweight.'server'. Forces everything into a container. Use only if you know you need the heavier environment everywhere.
For almost everyone, 'auto' is the correct answer — it gives you scale-to-zero savings where possible and the heavier environment only where it's actually needed.
The takeaway
One config file governs how Pikku Studio Cloud deploys your project, the platform usually manages it for you, and auto is a safe default that picks the right place for each function automatically.
Where to go next
- CLI reference — preview config changes safely with
deploy plan. - Deploying functions — how Workers and Containers differ in practice.
- FAQ — what your app costs to run and how usage billing works.