Getting started
Taking Rollout live takes seven steps. You set up a database, let engineers sign in with Microsoft, connect your clients' tenants and put the app online at your own address.
- 1DatabaseSupabase + migrations
- 2Sign-inRollout – Login
- 3Client tenantsRollout – Readiness
- 4HostingVercel, Frankfurt region
- 5Server gatewaysecret key
- 6Domainrollout.company.com
- 7Checklistall green
What you need
| What | Why | Tip |
|---|---|---|
| Supabase account, Pro plan | Database, sign-in and daily backups | The free plan has no backups and pauses the project after a quiet week |
| Vercel account, Pro plan | Hosting the app | Hobby isn't meant for commercial use |
| Admin rights in Entra of your own MSP | Creating two app registrations | Application Administrator is enough; granting permissions needs a Global Administrator |
| A domain you manage | For example rollout.yourmsp.com | Can also be a subdomain of ours, see step 6 |
| An hour to an hour and a half | To go through all steps | Keep the checklist open |
The demo works without a database or Microsoft account: everything stays in your own browser. Only put real client data into Rollout once the go-live checklist is all green.
How it fits together
Rollout consists of three parts that each do something different. It helps to know this before you start, because each step sets up one part.
Scroll here or press play.
| Part | What it does | You set it up in |
|---|---|---|
| Database (Supabase) | Stores planning, employees and the audit log. Every organization only sees its own data (Row Level Security). | Step 1 |
| Sign-in (Entra app Rollout – Login) | Engineers sign in with their work account, with your MFA and Conditional Access. | Step 2 |
| Reading client tenants (Entra app Rollout – Readiness) | Reads at the client whether everything is ready. Without a secret or password. | Step 3 |
| The app (Vercel) | The website at your address. | Step 4 to 6 |
Signing in and reading client tenants are deliberately two separate app registrations. Who may sign in to Rollout has nothing to do with what Rollout may read at a client. That way each part only has the rights it actually needs.
Roles in Rollout
| Role | Can |
|---|---|
| Administrator | Everything, including inviting team members, connecting tenants, the security center and approvals |
| Engineer | Manage projects, planning and employees |
| Read-only | Look along, change nothing. Handy for a team lead or project manager |
The first person to sign in (the address you record in step 1) becomes administrator. Colleagues join with a one-time invitation code.