From signup to your first bot app in minutes

Most "AI platform" trials end in a sandbox that has nothing to do with how you would actually run agents in production. Botmanor starts you in the real thing: a multi-tenant workspace with role-based access control, activity audit, billing, and file management already wired in, because Botmanor is a module of the Burdenoff Workspaces platform — not a standalone toy.

Onboarding is concrete. You sign up, your workspace is bootstrapped, and you create your first bot app — say, a "Customer Support Bot". A bot app is the user-facing front door: it has a type (assistant, automation, analyst, or specialist), a lifecycle status that moves from draft to active to paused to archived, and a visibility setting (private, workspace, or public) that controls who in your organisation can see it.

That bot app is the anchor for everything that follows. Specialist agents attach to it through routing links. Knowledge bases ground it in your documents. Channel routes carry its conversations to Slack or Teams. Because the app exists first, every later decision — which model, which knowledge, which channel — happens in context rather than in the abstract.

And because the workspace is the tenancy boundary, nothing leaks. Every Botmanor entity is workspace-scoped, and every API operation is protected by an RBAC rule enforced on every request. The five-minute onboarding path and the enterprise security model are the same path.

Create the bot, refresh the page, and it is still there — persisted, listed, and ready for its first agent. That is the whole first session: no credit card, no infrastructure to provision, no config files.