Quickstart: Studio

The Studio is a browser client over the public routes. It holds only your session and the keys you paste into it; it has no server-side state and cannot widen what the control plane accepts.

1. Open /studio/ and choose Sign up — an email, a password of at least 8 characters and, on the hosted deployment, the invite code you were given (request access if you have none). Sessions last 24 hours and live in this browser tab only.
2. Create a project. You land on its overview: state stopped, the engine pin (3.0.0), and a checklist titled Get started.
3. Click Wake up. The Cloud starts this project’s hyphae serve process on a loopback port; the head card now shows a live probe with the engine’s own fields (engine_version, native_directory_format, product_api_version).
4. Go to API keys and Create key. The full hyp1_… key is shown once in a dialog that ignores Escape and clicks outside; copy it. The list shows only the key_id.
5. Go to Engine and Probe. The Studio calls GET /v2/capabilities with your key and decodes Native’s HYPRSP01 answer; the raw bytes are one click away.
6. Try Storage (create a bucket, upload a file), Realtime (Listen, then Publish) and Functions (deploy the example, invoke it).
7. Click Sleep, then Snapshots → Create snapshot. Creating one while the engine runs is refused with 409 tenant_running — the engine holds the directory lock — and the Studio explains why.

Every section ends with Do the same from your terminal or code: the equivalent curl, hcloud and JavaScript for what you just clicked. Every (i) opens a short explanation with a link into these docs.

Next: the Studio guide or what it is not.