Documentation Index
Fetch the complete documentation index at: https://docs.getmuster.io/llms.txt
Use this file to discover all available pages before exploring further.
This guide is for Elitery engineers onboarding a new Professional or Enterprise customer. It assumes the customer has already deployed the muster backend and dashboard on their own AWS infrastructure.
Prerequisites
The customer’s environment must have:- muster backend running and accessible (e.g.
https://api.acmebank.com/healthreturns 200) - muster dashboard deployed and accessible
- PostgreSQL database provisioned and connected
- Direct database access for Elitery (for the onboarding script)
Step 1 — Set required env vars on the backend
Confirm these are set on the customer’s backend service:| Variable | Description |
|---|---|
DATABASE_URL | postgresql+asyncpg://user:pass@host:5432/muster |
JWT_SECRET_KEY | Strong 256-bit random string |
CUSTOMER_NAME | Customer company name (shown in dashboard) |
RESEND_API_KEY | From resend.com — for alert emails |
EMAIL_FROM | e.g. muster@acmebank.com |
ANTHROPIC_API_KEY | For AI insights and weekly report narratives |
INTERNAL_ADMIN_SECRET | Strong secret for muster-central proxy |
| Variable | For |
|---|---|
AWS_ACCESS_KEY_ID + AWS_SECRET_ACCESS_KEY | Cost Explorer + DNS scanning |
N8N_API_KEY + N8N_BASE_URL | n8n workflow scanning |
OPENAI_SCANNER_KEYS | OpenAI Assistants scanning |
GITHUB_TOKEN | Git repo scanning |
Step 2 — Run the onboarding script
From a machine with database access to the customer’s instance:- Create or update
instance_config(company name, plan, agent limit) - Create the admin user with a temporary password (must change on first login)
- Set up model pricing
- Print the tenant ID and next steps
Step 3 — Send the customer their credentials
Send the customer:- Their dashboard URL
- Admin email address
- Temporary password
- Instruction to change password on first login
Step 4 — Configure alert contacts
After the customer logs in, ask them to go to Settings → Alert contacts and add up to 3 email addresses. These receive:- Weekly health reports (sent by Elitery every Friday)
- Anomaly alerts (within 2 business hours of detection)
Step 5 — Run baseline discovery scan
In the muster dashboard → Discovery, trigger a manual scan to establish a baseline of what’s in their environment. You can also trigger scans via API:Step 6 — Configure agent integration
Share the integration guide with the customer’s developers. Recommend OTel for any coded agents:Step 7 — Book kickoff call
Book a 30-minute call with the customer to:- Walk through the discovery findings
- Confirm agents in the Discovery queue
- Confirm OTel integration is sending traces (check
/api/v1/otel/status) - Set expectations on the weekly report cadence
Checklist
- Env vars set on backend
- Onboarding script run successfully
- Customer has logged in and changed password
- Alert contacts configured in Settings
- Baseline discovery scan complete
- OTel env vars shared with customer dev team
- OTel status endpoint confirms traces arriving (
/api/v1/otel/status) - Platform connectors deployed for any no-code tools (n8n, Flowise, etc.)
- Kickoff call booked
- Customer added to muster-central admin portal (Trial Users tab)