Plans, Princing and Usage Limits
⚠️ Disclaimer: This page explains the logic behind Zaia's pricing model. For current plan details, limits, and pricing, always refer to the Plans page inside the platform — that's where you'll find the most up-to-date information.
Zaia's plans are designed to scale with your usage. Instead of charging per feature, the platform measures how much work your agents are doing — and your plan defines the boundaries of that work.
📐 How Plans Work
Plans are structured as a progression: as your usage grows, you move to a higher tier. Each tier unlocks higher limits across the three main usage pillars and adjusts the secondary limits accordingly.
There is also a Custom plan for teams with enterprise-level needs or specific requirements that don't fit standard tiers.
🔑 The Three Main Pillars
Your plan is primarily determined by three types of usage:
1. External Executions
The core metric. This counts every interaction your agents have with real users across active channels — WhatsApp, Instagram, Widget, and any other connected channel.
Each conversation turn with a real user counts as an execution. The higher your plan, the more external executions your workspace can handle per month.
Important: External executions measure platform usage only — they do not include LLM costs. AI model costs (OpenAI, Anthropic, Google Gemini, etc.) are billed directly by your LLM provider and depend on the model you configure. To deploy agents on external channels, you must have a valid LLM provider connected to your workspace. Learn how to set up your provider →
This is full cost transparency: you pay Zaia for what Zaia provides, and you pay your LLM provider directly for what the model consumes — no markup, no intermediary.
Note on legacy plans: Zaia previously offered built-in AI credits as part of the platform. This model no longer exists in current plans. If you are on a legacy plan, you may still see credit-based usage — but all current plans require you to connect your own LLM provider to enable agents on external channels.
2. Internal Test Usage
Interactions made through the Internal Chat — the private testing environment inside the platform — are counted separately from external executions.
This allows you to test, iterate, and debug your agents without consuming your production quota.
Internal usage has its own limit, independent of external executions.
3. Vibe Agent Usage
Every time you use Vibe Agent (the AI agent builder) to create, configure, or diagnose agents through natural language, that also counts toward a usage limit.
The more you use Vibe Agent to build, the more this meter moves.
This pillar scales with how actively you're building — not just deploying.
⚙️ Secondary Limits
Beyond the three main pillars, each plan also defines limits on platform resources. These are less likely to drive an upgrade decision, but they still define the boundaries of your workspace:
Members — how many team members can access the workspace
Connections — integrations with external services (used by MCPs and Channels)
Tables — number of structured data tables available
Table rows — total rows across all tables
Knowledge Bases — number of KBs available
Knowledge Base characters — total content volume across all KBs
Workflow concurrent executions — how many workflows can run simultaneously
Rollback versions — how many previous Agent versions can be restored
🔄 Billing Cycles
Plans are available on monthly or annual billing. Annual billing typically offers a discount compared to the monthly equivalent.
📊 Choosing the Right Plan
Start by estimating your external executions per month — that's the clearest indicator of which plan fits your operation.
From there, consider:
How actively your team will be building and testing agents (internal usage + Vibe Agent)
How many integrations, knowledge bases, and tables your workspace needs
How many team members need access
If your needs exceed the top standard tier, reach out to discuss a Custom plan.
✅ Key Takeaway
Zaia's pricing reflects usage, not features. Every plan gives you access to the full platform — what changes is how much your agents can do, how actively you can build, and how large your workspace can grow.
Last updated