Platform pricing
For teams running the agent platform in their business: one AI system across voice, SMS and email, holding one conversation with one memory and taking action inside existing business systems.
One AI system across voice, SMS and email.
Outbound calling, qualification and booking run on one thread across calls, texts and emails.
Starter, Growth and Scale.
Billed monthly, per org. Seats are connected users. Larger platform builds, with custom systems and surfaces, are scoped and quoted directly.
| Plan | Base /mo | Base /mo (CAD) | Included users | Per extra user |
|---|---|---|---|---|
| Starter | $99 | C$129 | 3 | $12 / C$16 |
| Growth | $299 | C$399 | 10 | $12 / C$16 |
| Scale | $699 | C$929 | 25 | $10 / C$13 |
| Enterprise | Custom | Custom | — | — |
Starter auto-upgrades to Growth at 10 users; Growth auto-upgrades to Scale at 25 users.
What moves a platform quote
The quote follows the shape of the platform your team intends to run. These are the dimensions the conversation maps before a commercial proposal is prepared.
Which of voice, SMS and email the shared conversation runs across.
How conversation activity is shaped across the channels in scope.
Where the platform must take action inside the systems your team already uses.
Which agent surfaces the platform is expected to run.
Whether your team builds in Agent Builder Studio or builds with Alebex.
Outbound calling, qualification and booking run on one thread across calls, texts and emails.
Platform or Agents — which layer you need
The boundary is the difference between the system your team runs and the agents deployed on it. Many deployments need both; they remain separate layers.
Choose the platform layer for the channels, shared memory, tools, guardrails and action inside existing business systems.
Choose the agents layer for the agents that qualify, book, resolve, update records, trigger tools and hand off on that platform.
The platform surfaces, as the navigation lists them. An item marked coming soon is not part of what you would be running today.
Before the quote conversation
The layer boundary, the build path and the data location should be clear before anyone asks you to talk to sales.
Why is the platform quoted rather than listed?
The platform quote follows the channels in use, the shape of conversation activity, the business systems it acts inside, the agent surfaces it runs and the build path you choose.
What does a quote conversation cover?
It maps what your team intends to run, where the platform must act and whether your team builds the agents or builds with Alebex.
Can I start on a developer account?
Yes. A developer account is the self-serve route to API access. Running the platform or deploying agents is a separate layer conversation.
Where does my data live?
Recordings, transcripts and customer information are held in Canada.
What happens if I also need agents?
The platform and the agents are scoped as separate layers, then mapped together around the same runtime.