From signup to a running sprinkle in six steps.

The six steps

1. 1

   Sign up for a Yarrow workspace

   No account

   The quickest entry point is the live demo on /trial — it runs a real drift end-to-end without an account. When you are ready to keep what you built, sign up.

   • No card. Free tier runs 12 sprinkles across a single workspace.
   • Email + password. SSO is available on the Autopilot tier.
   • Migrate the demo workspace into your signup on the next page.

   Run the live demo first →
2. 2

   Claim your first workspace

   Sign-in required

   Workspaces are the unit of isolation. Each one owns its own connector bundles, sprinkles, agent feed, and audit log.

   • Workspace slug becomes your dashboard URL: /workspaces/<slug>/…
   • Invite teammates from Settings → Members after the first run.
   • One workspace per environment for clean blast-radius recovery.

   Continue to login →
3. 3

   Connect a cloud account

   Cloud creds

   Yarrow reads from your cloud only via the connector you paste in. Each provider has its own permission scope — the four guides under Connectors walk through the grants and the live-form fields, byte-for-byte.

   • Use a least-privilege IAM role or service principal — Yarrow never asks for org admin.
   • Yarrow runs a reachability probe before saving the encrypted bundle.
   • Add more providers any time. Each shows up on the workspace connector list with its last probe status.

   AWS guide →
4. 4

   Write your first sprinkle

   Yarrow

   A sprinkle is an intent declaration: what should be true, and which actions may the agents take to keep it true. The exact field set lives in the YAML reference; the editor validates it on submit.

   • Pick a provider that matches the resource you want to govern.
   • Pick an approval mode — AUTO heals without a human; NOTIFY pings; MANUAL waits.
   • Approve + save. The sprinkle appears on the workspace sprinkles list immediately.

   YAML reference →
5. 5

   Watch the agent run

   Yarrow

   The /agents page is the live feed. Each tick of the recon loop runs the sprinkles that match the resources it sees, and emits an entry per run.

   • A green PASS means live state matches the declared intent.
   • A yellow DRIFT means the agent saw something to fix — usually a heal follows within seconds.
   • A red HARD-FAIL surfaces the underlying error in the row expand.
6. 6

   Tune the loop

   Yarrow

   After your first run, tune two switches: approval mode (AUTO → NOTIFY) and allowed actions. Move AUTO last once you trust the heal.

   • Edits save as a new version. The previous version is preserved for rollback.
   • Connectors can be reprobed at any time from the connectors dialog.
   • Audit log entries are immutable — every change, every run, every probe.