Onboarding
The six onboarding questions, what each one changes, and how to change your answers later.
New workspaces start with a six-step onboarding flow. Every answer changes the workspace in the live preview on the right, so you can see the effect before you commit. You can change any answer later in Settings.
Returning from OpsLyft v1? You'll see a shorter, three-step flow instead. See Migrating from v1.
Step 1: About you
Enter what OpsLyft should call you, your company, and your work email. OpsLyft creates a workspace for your email domain (for example acme.com). Teammates on that domain can join without an invite.
Step 2: Your role
Your role decides your home page, which views are pinned, and how Iris phrases answers.
| Role | Best for | What changes |
|---|---|---|
| FinOps lead | People who own the practice: allocation, savings, and reporting. | Optimisation and allocation views are pinned. |
| Engineering / Platform | People who run infrastructure. | Cost per service and waste your team can fix. Engineering lens by default. |
| Finance & procurement | People who own the number. | Budgets, forecasts, commitments, and chargeback. Finance lens by default. |
| Leadership | CTO, CFO, or VP. | The trend, the big levers, and how you compare. CXO lens by default. |
Step 3: Your stack
Pick every provider you pay for: AWS, Azure, Google Cloud, Snowflake, Databricks, Kubernetes, OpenAI, and Anthropic. Then pick your rough monthly cloud bill (Under $50K, $50K–250K, $250K–1M, $1M–5M, or $5M+). The bill range sets your initial savings estimate.
Step 4: Goals
Pick up to three goals, in order. Your first pick leads the home page and the first week's plan, and each pick adds a widget to your home canvas.
| Goal | What OpsLyft sets up |
|---|---|
| Cut idle and oversized resources | Right-sizing, orphan clean-up, and non-prod scheduling in Optimisation. |
| Allocate cost to teams | A Cost by team widget grouped by your team tag. Showback or chargeback by team, product, or customer. |
| Forecast and hit budget | A Forecast vs budget widget and budgets per team with alerts before month-end. |
| Catch spikes early | Anomaly alerts within hours of a jump, with the reason. |
| Get commitments right | A Commitment coverage widget for Savings Plans, reservations, and CUDs. |
| Control AI and GPU spend | Cost by model, team, and token, plus GPU utilisation. |
Step 5: Your workflow
Tell OpsLyft where findings should land:
- Tools your team already uses: Slack, Jira, Microsoft Teams, Linear, ServiceNow, or Email only. OpsLyft offers to connect them.
- How you tell teams apart in the bill: Resource tags, Accounts and projects, Kubernetes namespaces, or Not sure, let Iris suggest. This becomes your first allocation key.
- How often to update you: Daily digest, Weekly digest, or Only when something spikes.
Step 6: Connect
Connect your first provider. Start with one; the others can follow later. Each provider shows its own read-only method, the time it takes, and the steps. See Integrations for full instructions.
If you can't connect it yourself, copy the join link under Don't have access? and send it to the provider's owner. You get a Slack message when they finish.
Skip or use sample data
- Explore with sample data (top right of every step) opens the workspace on a sample estate.
- Use sample data instead on the connect step does the same thing after you've answered the questions.
Change your answers later
| Answer | Where to change it |
|---|---|
| Name, company | Profile |
| Role and lens | The Lens menu in Cost Explorer and canvases, or your profile |
| Providers | Integrations |
| Digest frequency | Notifications |
| Slack, Jira, and other tools | Tickets → Integrations |