
Four building blocks
Omni
Omni is where a team describes a business outcome and turns it into an Agentic Application: a backend agent paired with a live frontend (chat, live surfaces, reports, dashboards) that teammates can open, share, and act on. Omni is available in the channels where work already happens, including Slack, WhatsApp, Telegram, and email. When a request needs an enterprise system, Omni delegates to a Custom Agent with the right permissions.
Custom Agents
Powered by Agno Agents scoped to one system or one job. xpander ships pre-built Custom Agents for systems like Salesforce, Jira, Snowflake, and GitHub, and you can configure your own. Each one is limited to the operations you approve. A raw API connector relies on the prompt to hold the model back. A Custom Agent enforces access structurally: operations you did not approve are not in its tool surface.
Agentic Automation
Powered by Agno Workflows Backend workflow automation where AI handles data mapping between systems at runtime. Traditional automations (Zapier, n8n, Power Automate) break when an API changes because every field is manually wired. Agentic automation describes what each step should do in natural language, so it adapts to schema changes instead of breaking. Build on a no-code canvas or with the Python/JS SDK. When to use: Backend automation triggered by events (webhooks, schedules, emails) across multiple systems. Learn more →Agent Studio
Powered by Agno A visual builder for your own agents. When the pre-built options don’t cover your use case, Agent Studio lets you pick from the connector catalog, add your own documents as knowledge bases, and deploy to any channel. A connector covers one service, such as Slack or Jira, and each operation that service exposes is a tool the agent can call. When to use: The pre-built agents don’t cover your use case, and you need a custom mix of tools, knowledge, and behavior. Learn more →How it fits together
Agent Studio is where you configure everything: agent instructions, tool connections, knowledge bases, safety controls, and deployment channels. Once deployed, Omni handles conversations and delegates to Custom Agents for governed system access. Agentic Automations run separately in the background, triggered by events, handling multi-step processes that don’t need a conversation. Everything is also accessible through the Python SDK and REST API.
How the four building blocks connect: Agent Studio configures, Omni converses, Custom Agents govern system access, and Agentic Automations handle backend processes.
Deployment
All three options run identical software.xpander Cloud
Managed, SOC 2, auto-scaling. Free tier available.
Bring Your Own Cloud
Your AWS, GCP, or Azure. Self-hosted Kubernetes with Helm.
xpander Box
On-prem hardware. Air-gapped, rack-mountable, pre-loaded models.
What’s next
Omni
Turn business outcomes into Agentic Applications.
Custom Agents
Governed agents for enterprise systems.
Agent Studio
Build your own agents.
Agentic Automation
AI-native workflow automation.

