Beta/open now, onboarded in batches
Get your department an AI team.
Tell us where it hurts and we will set up your first team with you — tools connected, guardrails written, and the log waiting in the morning. Eight teams, one signup.
TeamsAll eight in beta — start with one, add the rest later.
SetupOnboarded with you, not through a docs page.
GuardrailsSpend caps, approval thresholds, flagged accounts.
The logEvery action with its reason and evidence, from day one.
BillingNothing until your access starts.
Beta · batches weekly
01FAQ
Fair questions, straight answers.
+When does access start?
We onboard beta workspaces in small batches so each one gets attention. Most requests hear back within a few days with a start date, and setup happens with you, not through a docs page.
+What does the beta cost?
You pay nothing until your access starts, and beta testers help set the final price. The proposed license and usage figures are on the pricing page as estimates, never a quote.
+Which team should we start with?
The department that is furthest behind. One team is the whole onboarding: connect its tools, set what runs on its own, and read the log in the morning. Add the next when it earns it.
+What do you ask of beta testers?
Use it for real work, and tell us when something confuses you or the log. A short call in the first two weeks beats a hundred analytics events.
+Do our tools and data stay ours?
Yes. Connections run over OAuth or paste-token, you can disconnect any time, and the action log exports with you. Nothing trains on your data.