Every example lives in examples/ and deploys with pnpm tiny deploy --cwd examples/<name>. They are ordered by what the target has to have configured before they work.

hello-private

The smallest app that proves identity, routing, and lifecycle work. Private visibility, login required, no resources. Start here — walked through in Deploy your first app.

perf-probe

A microbenchmark of guest primitives. Useful when you want to know what the runtime costs on your host — particularly on nested KVM, where the serial console is expensive enough to matter.
The long requestTimeout and sleepAfter are deliberate: a benchmark that sleeps mid-run measures the wrong thing. See Observability for the serial-telemetry trade-off it exists to measure.

notes-with-sqlite

Shared notes with a database and per-user attribution — the smallest app with durable state. Demonstrates migrations and a group binding with a non-default role.

smb-ops-dashboard

A placeholder operations dashboard for a small business — revenue, invoices, and this week’s tasks. Same infrastructure as notes-with-sqlite, but it looks like the kind of thing someone actually asks an assistant for.

file-vault

A file drop backed by a platform object namespace. The quota is set small on purpose so it is reachable in a test rather than theoretical.
The app calls context.storage('vault') and never holds a bucket, a path, or a credential. maxSize is measured against the namespace after the write, so replacing an object does not charge for the copy it replaces.

stripe-read-dashboard

SQLite plus a brokered capability grant. The app calls stripe.payments.read; the Stripe key lives in an organization connection and never enters the microVM.
A production capability request requires approval under the default policy. Requesting a capability never approves it, even for an admin.

support-inbox

The one that exercises everything optional at once: a build.command running in a throwaway build microVM, a Postgres database on an operator cluster, and approved Slack and OpenAI connections. Before deploying it, confirm the target has all three:
If the build image, the Postgres cluster, or a connection is missing, plan refuses upfront and names which one — see Target compatibility.