5-day biscuit beta: what to try in Orca Cockpit

v0.0.1 is named biscuit and it is Beta. The $50 plan includes your first Project. That is enough calendar to design, code, and (if your tenant allows) deploy a small Mule project. Buy Orca credits for Cursor-backed usage. Card checkout is not live — operators set balances in Clerk.

Day 1 — Account and vault

Accept your Clerk invite, set a password, open Vault, paste Cursor + Anypoint. Add Salesforce, GitHub, or Postman if those are in your week. Confirm Account shows the keys as set. Values will not be shown again.

Day 2 — Desktop Sign in and Ask

Download Cockpit. Sign in. Spend the day in Ask: inventory, unpoliced APIs, vCores, “what would break if I add an Experience API.” You should never feel stranded — Connections tells you what the bot can see.

Day 3 — Project + hello-world

Open the 1:1 Project created on first account visit. Scaffold hello-api. Use the VM if Maven or a JDK dance is required. The laptop stays the companion, not the build host.

Day 4 — Salesforce or GitHub loop

Pick one: a Salesforce sync stub (OAuth on the VM) or clone a real Mule repo from GitHub. Keep Postman collections next to the flows if you vaulted a key. Stay generic — banking or government patterns, not a named agency.

Day 5 — Plan a deploy, then decide

Ask what CloudHub or Runtime Fabric targets the Connected App can see. Plan a deploy. Only Agent-push if you confirm the environment. The $50 plan already covers the first Project; Orca credits meter Cursor usage.