Priced by what you actually use.
Two products, two pricing models. Applications are sold per user, per app — or as the All-Apps suite. The platform is sold per user, with a distinct developer tier for engineers who author on it. Three deployment models : AWS Marketplace AMI, SAAS or on-prem.
Per user, per app
One simple unit — the user. Four packaged applications, with one rate for ERP standalone and one for the All-Apps suite.
Platform is its own line
The platform fee shows up only when you license the platform to build your own applications alongside (or instead of) the packaged ones.
Three deployment models
AWS Marketplace AMI · SAAS · On-prem. On-prem requires the Platform licence in addition to any apps.
No plan ladder
No Starter / Growth / Enterprise tiers. One rate per surface ; volume and term-length adjustments are scoped in the engagement, not in a marketing table.
Four applications. Sold per user.
ERP standalone for the customers who only need the operational backbone. All-Apps for the customers running more than one module.
ERP
One application
- ERP — finance, sales, procurement, inventory, manufacturing, reporting
- Native compliance for the regimes we support today
- Audit trail, multi-entity and multi-currency built in
All Apps
The packaged suite
- ERP — finance, sales, procurement, inventory, manufacturing, reporting
- CRM — pipeline, accounts, support, revenue analytics
- HR — workforce, time, onboarding, people analytics
- PM — projects, budgets, milestone billing
- Source-available licence — use the suite as a working starter and extend it on the Platform
Start from an Apps suite. Build out from there.
Solutions and the Platform are not either-or. The most common enterprise engagement licenses an Apps suite — ERP, or All Apps — as a working starter and adds the Platform on top : a custom module on the same data model, a vertical-specific workflow on top of procurement, a buyer portal that shares the customer master with CRM. The source-available licence on Apps means the suite is also a reference architecture the customer can read, fork and extend.
Because every capability the Apps inherit — supervised execution, multi-tenancy, audit, observability, AI inside the perimeter — is the platform's, the custom modules inherit them automatically. No integration tax, no second security perimeter, no parallel observability tier. The custom code lives in the same dictionary the suite lives in.
For teams building their own applications on Airtool.
The application is normalised metadata — every form, screen, role, query and batch is a database record, not a file. The platform compiles SQL and stored-procedure logic from XDBL, an XML grammar agents target by construction. AI does not parse a file tree ; AI authors the same graph your team authors. Both tiers include every capability — no per-engine licensing, no per-module surcharges, no premium-feature paywalls. Minimum engagement is 10 application users plus 2 developers.
Application user
A user of any application your team built on the platform
- Run every application your team has deployed — no per-app limit, no per-module surcharge
- Native SQL across all 10 supported engines and interactive analytics — dashboards, drill-down, drill-across, cross-filtering — inside every app
- AI business agents — financial, sales, operations — work in natural language on the data your role can already read, inside the user's permission perimeter, every invocation audit-traced
- Authentication, audit, observability and document generation — included, not premium add-ons
Platform developer
An engineer authoring on the platform — build, administer, operate
- Everything in the Application user tier, plus the full build, administer and operate surface — same platform, no premium edition
- Build · Application Editor with 100+ components for forms, dashboards, reports, server scripts and batch jobs — hot-reloaded across the cluster
- Code · server-side scripting in JavaScript and Python, native SQL compiler across all 10 engines, 40+ namespace standard library
- AI development agents — natural-language instructions compile to XDBL; agents scaffold forms, author stored procedures, refactor workflows, propose schema migrations. Because the application is metadata, agents read and write the same graph you do
- Administer · the AWS-console-equivalent — users, roles, MFA, certificates, cron, integrations, replica routing, AI budget caps
Deployment
AWS Marketplace AMI — launch the AMI on your AWS account ; minutes to first run ; ideal for proof of concept and small production deployments. SAAS — we host the apps and the platform on infrastructure we operate ; predictable, no infra to run. On-prem — customer infrastructure, customer operations ; on-prem requires the Platform licence in addition to any apps.
Implementation services are scoped separately and quoted phase by phase. The pricing surface is the licence ; the implementation surface is the engagement. Both sides see the trade-offs explicitly.