Three plans. Different levels of control.
Start with one system, manage multiple teams, or add dedicated engineering and audit oversight. Scope and pricing are agreed with our team — no card required.
Starter
Start using AI with data from one core system.
- Basic admin console — up to 5 free user accounts
- Connect up to 1 core system — API or direct database
- Free custom MCP tool development — up to 50 tools
- Standard read-only MCP tools
- Automatic masking of personal data before it reaches AI
- Basic usage view — call counts per tool, without individual call details
- Agreed Golden Period for UAT and handover
- Email support
For multi-team businesses
Growth
Manage multiple teams and control the data each can access.
- Full admin console — People & Access and per-user tool control, with up to 20 free accounts
- Data-scoped access — each branch, team or department sees only its authorized data
- Connect up to 3 core systems — API, direct database, or hot folder (with sync manager)
- Free custom MCP tool development — up to 200 tools
- Tool usage log in the console — who called which tool, and when (Audit Detail)
- Configurable personal-data masking per endpoint
- Optional Organizational Learning / Re-learn Add-on
- Ticket support
Enterprise
Govern a business group with audit evidence and a dedicated team.
- Enterprise audit log — hash-chained to make later changes detectable
- Audit exports by user, tool and period, with retention agreed in your SLA
- Dedicated integration engineer and account manager
- Connect core systems across your group within the agreed integration scope
- Includes Organizational Learning / Re-learn entitlement (configured via SOW)
- Local / on-premise AI model support and Tool Override
- Everything in Growth, including per-team data scope and tool usage logs
Every plan operates read-only with role-based access control and security audit logging · Final pricing is evaluated after system discovery and agreed scope. Infrastructure, AI accounts, and add-on services are quoted separately in proposal.
What the support on each plan actually commits us to
Each plan above names a channel, and a channel is not a promise. This is the promise: how long you wait for a first response from a person who has read what you sent. It is a response time, not a repair time.
Starter — email support
A first response within 2 business days.
Growth — ticket support
A first response within 1 business day, and a ticket reference you can quote in anything you send us later about the same problem.
Enterprise — dedicated account manager
A first response within 4 business hours, from the account manager who already knows your systems.
The conditions, stated up front
- Business hours are Monday to Friday, 09:00–18:00 Thailand time, excluding Thai public holidays, and the clock runs only inside them. Enterprise's four hours are four business hours, not four hours on the wall clock — a request sent at 17:00 on Friday is answered by 12:00 on Monday. We write it this way because we do not staff a night shift, and a number that implies one is a number we would break.
- A first response is a person who has read your request telling you what we have found and what happens next — not an automated acknowledgement, and not the work being finished. We publish no repair time, because how long a fix takes depends on what broke; the first response is where we tell you what we expect it to take.
- What follows that response depends on what you asked for. If a tool we built returns the wrong answer or stops working, fixing it is covered by your plan. A new tool, or a change to what an existing tool answers, is development work — scoped and quoted before anyone starts.
- These times cover our side: the MCP layer, the Admin Console, and the connections we operate. They do not cover your source systems or the AI assistant you chose, neither of which is ours to answer for.
- Enterprise runs on a custom SLA. Where a signed Enterprise agreement sets different terms, that agreement governs; until it does, the figure above is what we hold ourselves to.
- Tickets are kept on our side. There is no customer login today, so you raise a request the way you already talk to us and every update comes back on that same thread — the ticket is how we track your problem, not a place you visit. A view of your own tickets is something we intend to build, and we will not call it available until it is.