Getting started
From nothing to a working agent in an afternoon. We do the first one with you on a call; this is what happens.
1. Create a workspace
Go to app.olsie.ai/signup. Your name, work email, a password, and the name of your company or workspace. That workspace is your tenant: everything below belongs to it and to nobody else.
2. Pick a plan and a region
On the same page you choose the Olsie Cloud region your team runs in: Germany (Frankfurt) or United Kingdom (London). Your agents, their memory and your vault stay in that region. We run the servers; you never deal with a hosting provider.
| Plan | Who | Price |
|---|---|---|
| Start small | Tilde, chief of staff | £49 a month |
| One agent | Heimdall, Gro or Sol | £79 a month |
| The team | All four | £199 a month |
Founding prices for the first twenty-five customers. If you were given a licence code, enter it here. Card payment is set up with you on the first call; nothing is charged on sign-up.
Our promise: first month, we set it up with you. Not useful by day 30, full refund. Cancel any time.
3. Connect a channel
Discord first. Add the Olsie bot to your server with the link on the Channels page, copy your server id (Discord → Settings → Advanced → Developer Mode, then right-click the server → Copy Server ID) and paste it in. Slack and Teams arrive next.
4. Add your Anthropic key
On Keys & secrets, add ANTHROPIC_KEY with a monthly cap. Create the key in a dedicated workspace in your Anthropic console with its own spend limit, so the cap is enforced on both sides. You see the value once; from then on you see its name and when it was last used.
Add the tools the agents need the same way: CLOUDFLARE_TOKEN, GITHUB_TOKEN, GOOGLE_ADS_TOKEN and so on. Use scoped tokens, never account passwords.
5. Say hello
Within a minute of steps 3 and 4 your agents start: the Team page shows each one go from provisioning to active. In your channel: @Olsie status, or name one, @Olsie heimdall what would you fix first?; a request that names nobody goes to Tilde. Then give an agent a real job. Anything that would cost money or change a system comes back as an approval card in the channel and in the pane. Read-only work, like diagnosing a slow server or reading your search terms, needs no approval and is still logged.
What you can see, always
- Team: which agents are on and where each lives.
- Approvals: what is waiting, what was decided, by whom.
- Jobs and Spend: everything that ran, and what it cost on your key.
- Audit: the full trail, exportable as CSV.