Getting started
Create your account, get your first Teammate hired and deployed, and send your first message — start to finish.
Create your account
Signing up creates a personal organization for you — everything you do is scoped to your own org at first, though you can invite team members later.
No credit card required: signup starts your free trial immediately, with full platform access from the first click.
What your trial includes
Your trial gives you the full platform, not a limited demo:
| Included | Detail |
|---|---|
| Agent server | 1 (Standard Small — 2 vCPU / 4 GB) |
| Models | Pick from ~600 models |
| Payment | No credit card required |
You can add more agent servers and bigger sizes once you upgrade — Enterprise plans can also bring their own provider keys. See Team & billing and pricing for what changes at that point.
Your first agent server is already there
You don't need to provision anything. Your account comes with one agent server already created — this is the workstation your Teammates will live on. Head to Agent servers later if you want to understand sizing, disk, or what happens when you delete one; for now, just use the one you've got.
Hire your first Teammate
Your first Teammate on an agent server must be named main — the dashboard fills this in for you automatically, since every server needs at least one baseline Teammate before it can do anything.
From there:
- Pick a template — choose from the Teammates catalog (roles for ops, sales, support, engineering, and more), pick one of your org's own saved templates, or start from scratch with Custom.
- Confirm the default model — the dashboard pre-selects the strongest model your plan can currently run, picked from your allowed list. Every new conversation starts on this model; you can switch a single conversation on the fly with the
/modelcommand. You can change the default before saving. - Save. Your Teammate now exists — but nothing it does is live yet. See Core concepts for why.
Wire up a messaging channel
Before anything else, add your channel user ID to your profile — on your profile's Channel Accounts section, fill in the ID for whichever channel you'll use. Telegram and Discord Teammates won't respond to you at all until your ID is on the allowlist; Slack is the one exception, and only when its access is set to "Everyone in your company."
To actually talk to your Teammate, give it somewhere to receive messages: Telegram, Discord, or Slack, one channel per Teammate. Each channel needs its own bot credentials and, for most channels, an allowlist of who's permitted to talk to it. Full walkthrough (including the Slack app-install wizard) is in Messaging channels.
Click Deploy
Everything above — the Teammate, its model, its channel — is staged as a pending change until you deploy. Deploying builds your workstation with that configuration and starts your Teammates running on it.
Note: Your first deploy takes about five minutes. It's provisioning a full agent server from scratch, not a quick edit — later changes to workspace files or skills reload quickly; changes to models, secrets, or channels trigger the same full rebuild as a first deploy.
Say hello
Once the deploy finishes, message your Teammate on the channel you wired up. That's it — you're talking to a running agent on infrastructure you didn't have to touch.
When you're ready to upgrade
Moving off the trial follows a fixed order: add a payment method, then the dashboard activates the plan your seat count calls for (a single member lands on Pro Solo, two or more on Pro Team), then you're walked through a mandatory messaging-identity step — confirming which channel platform you personally use, so team invitations and allowlists can reference you correctly. See Team & billing.
Where to go next
- Core concepts — the vocabulary and mental model behind Teammates, agent servers, and deploys.
- Agent servers — sizing, disk, and server-level settings.
- Slash commands — the in-chat command cheatsheet for talking to a Teammate day-to-day.