What would change

Compare your sandbox against any deployed stage, field by field, before you ship.

Before you deploy, it's fair to ask: what exactly is different? The Changes view answers that with a structured comparison between your sandbox as it is right now and any stage you've already deployed — not as a wall of code, but as the pieces of your app that were added, removed, or modified.

Annotated screenshot of the Changes view: a "Compare to stage" dropdown set to "main (production)", a summary bar reading "7 changes — 3 added, 3 modified, 1 removed", and tabs for Functions, HTTP, and Schedulers with +/~/− count badges. An expanded row shows a field-level table with Stage and Sandbox columns, one differing row highlighted amber. Callout: "Exactly what deploying this sandbox would change."

How it reads

  1. Pick a base. The Compare to stage dropdown lists every stage with an active deployment. The comparison is: that stage's live app versus this sandbox's current state.
  2. Scan the summary. A summary bar totals the changes — how many pieces were added, modified, or removed.
  3. Drill into categories. Changes are grouped by kind — functions, HTTP routes, schedulers, queues, channels, triggers, MCP tools, agents, CLI commands, middleware, variables, and secrets — and only categories with changes show a tab.
  4. Expand a row. Each changed piece opens into a field-by-field table with the stage's value on one side and the sandbox's on the other, differences highlighted. For an HTTP route that means method, path, and the function it calls; for a function, its wrapper and whether it needs a session.

Pikku Studio Cloud's own plumbing is filtered out of the comparison, so nothing shows up as a "change" unless it's genuinely part of your app.

What it is — and isn't

This view compares your app's structure: the functions, wires, and configuration that make up its surface. It's the deploy-shaped answer to "what did the builder actually do?" It is read-only — deploying still happens through a deployment, and saving your work still happens through publishing.

A useful habit: glance at Changes before every deploy. Added pieces you expected, nothing removed that surprises you — that's a thirty-second check that catches a whole class of "wait, why is that gone?" moments.

Where to go next