Get StartedSigning up and creating your tenant

4. Signing up and creating your tenant

From “I want to try Daalu” to a working tenant with you as its admin — in under a minute.

This chapter takes you from “I want to try Daalu” to “I’m logged in with a working tenant.” It’s the shortest chapter in the book — the sign-up flow is deliberately short — but it’s important to understand what’s happening so the rest of the system makes sense.

If you’ve already signed up and skipped ahead, jump to Chapter 5 for the home dashboard tour.


What you’ll create

By the end of this chapter you will have:

  1. A user account — an email/password identity associated with you personally.
  2. A tenant — the workspace that your user belongs to. Your integrations, your alerts, your data all live here. Everyone you later invite will share this same tenant.
  3. An admin role on that tenant — because you’re the first user, you start with full administrative permissions.

If your company already has a Daalu tenant and someone has invited you, you’ll receive an invite link instead. Use that link rather than the public sign-up — joining the right tenant matters and is hard to fix later.


Step-by-step: the public sign-up flow

Open a browser to https://ops.daalu.io.

You’ll land on the public marketing page. Click “Get started” in the top-right.

The sign-up form asks for:

  • Work email. Use a real, deliverable address. We send you a confirmation link there and any future password-reset requests.
  • Full name. Shown in the UI to your teammates and on change proposals you approve.
  • Password. At least 12 characters, with at least one digit and one symbol. Daalu hashes passwords with bcrypt — we never see the plaintext, even briefly.
  • Tenant name. Free-form. Use your company name (e.g., “Acme Robotics”). You can rename it later from Settings → Tenant.

Click “Create account”.

You’ll see a “Check your email” screen. The confirmation email arrives within ~30 seconds. Click the link in it; you’ll land back in the operator app, logged in.

That’s the whole sign-up.


Step-by-step: joining via invite

If someone in your company sends you an invite, you’ll get an email with a button labelled “Join Acme Robotics on Daalu.” Click it.

The form is similar to public sign-up but:

  • You can’t change the tenant name — you’re joining an existing tenant, not creating one.
  • Your role is set by whoever invited you — typically “user” rather than “admin.”

Fill in your name and password, click “Join.” You’re in.

The invite link is single-use and expires after 7 days. If it expires, ask the person who sent it to issue a new one from Settings → Team.


What you’ll see on first login

After your first login, the home page shows a getting-started checklist that runs along the top. It walks you through:

  1. Connect a notification channel. Slack or PagerDuty are the most common. You can use a personal Slack workspace if your company-wide one isn’t ready yet.
  2. Connect at least one source. A cloud account, an observability stack, or a Kubernetes cluster — anything that gives Daalu something to look at.
  3. Verify the AI Assistant works. Click the assistant panel and ask anything; it should respond.
  4. Invite a teammate. Daalu is much more useful with two people in the workflow than with one.

Each box gets a green checkmark as you complete it. The checklist disappears once everything is done, but you can bring it back from Settings → Onboarding.

Don’t worry if you can’t do all four right now — connecting a cloud account properly might require coordination with your IT team. The checklist is a guide, not a gate.


A note on tenants and signing up twice

Two situations come up that confuse people:

“I signed up but my colleague is already on Daalu”

If your colleague created the company’s tenant before you, you should have used their invite instead of public sign-up. The result is that you now own a separate tenant with just you in it.

The fix: ask your colleague to invite you to their tenant. Once you accept, your two-account situation resolves cleanly — you’ll have a personal one-user tenant (which you can leave abandoned) and a membership in the real company tenant. When you log in, you’ll be asked to pick which tenant to enter.

”I want to manage two different companies’ Daalu instances”

That works fine. Each company has its own tenant; you’ll have one user account that’s a member of both. When you log in, you’ll see a tenant picker.


What’s happening behind the scenes

For the technically curious — and because this affects how the rest of the book reads — here’s what just happened when you signed up:

  • Your user account is created — your email, a securely hashed password, and your name. We never store or see the plaintext.
  • A fresh tenant is created with the name you chose, and your user is made its first member.
  • You become the tenant admin. Because you’re the first user, you start with full administrative permissions over the tenant.
  • We email you a confirmation at the address you signed up with so you can verify it and log in.

Future signups to the same company use an invite instead of the public flow — a one-shot token that locks the new user to the correct tenant rather than creating a new one.

Why it matters: the first person to sign up defines the tenant. If your company should share one workspace, make sure the right person signs up first and invites everyone else — see Chapter 6.


What’s next

You’re now logged in with a fresh tenant.

Chapter 5 is a guided tour of the home page — the panels you’re looking at, what each one means, and what the system is showing you before you’ve connected anything.

Chapter 6 covers inviting your team, which you can do at any point. Inviting teammates early means they can investigate the first real incident with you instead of being onboarded mid-fire.

Chapter 7 walks you through connecting your first cloud account. This is the most common first integration and the one that lights up the most of the UI.

Next: Chapter 5 — Your first five minutes on the home dashboard