guides
Getting started
From signup to your first proven exploit in a few minutes. Follow the five steps below — the agent does the heavy lifting.
before you begin
- Nothing to install — Muster runs in your browser.
- Have one thing to point it at: a live app/API URL, a GitHub org or username, or read-only cloud credentials.
- You must own the target or be authorized to security-test it (you'll attest to this).
The path
Sign up
name your org
Connect
app, code, or cloud
Scan
agents attack
Fix
proof + one-line fix
Continuous
schedule + CI
Step by step
- 1
Create your account
Go to
/signupand fill in your name (optional), organization name (required), email, and a password of at least 8 characters. Click Create account.You become the owner of that organization. You can rename it, create more, and invite teammates later.
- 2
Connect your first asset with the agent
After signup you land on your organization. Click ✦ Set up with agent (or the Continue setup → nudge) to open the guided three-step wizard at
/orgs/<your-org>/onboard:- Web apps — add live app/API URLs (e.g.
https://app.acme.com) and tick “I own these assets, or I'm authorized to security-scan them.” - Code — enter a GitHub org or username, click Discover, and pick the repos to protect.
- Configure — the agent reads each asset, detects the stack, wires up the right scanners, then Lock it in & start scanning.
ℹPrefer to do it by hand, or adding a cloud account? Skip the wizard and add assets one at a time from the Assets page — same result. - Web apps — add live app/API URLs (e.g.
- 3
Watch the first scan
Scanning starts automatically at the end of setup. Follow it live under the org's scans tab (
/orgs/<your-org>/scans) — you'll see live activity, then a scan-history entry you can click into. First proven findings typically appear within minutes. - 4
Read and fix findings
Findings land under the alerts tab, each with a severity, the agent's assessment, the evidence, and a one-line fix. Ship the fix, then re-scan the asset to confirm it's gone. See the Findings guide for the full workflow.
- 5
Make it continuous
Open Settings → Scanning, turn on Scheduled scans, choose a frequency (every hour, every 6 hours, daily, or weekly, depending on your plan) and click Save. Wire the REST API into CI to re-test on every deploy. New holes surface the moment they appear — not at your next audit.
continue