DataTwin is priced to support real production workloads, not vanity signups. Clear platform fees, clear limits, and clear overage rules so you can scale without burning margin.
Every paid plan carries a real software fee before usage. That protects the business from subsidizing heavy AI workloads.
Included token pools are generous for the plan tier, with overages priced explicitly instead of hidden in vague fair-use language.
Solo for experimentation, Pro for working analysts, Business for governed teams, Enterprise for multi-department rollouts and SSO.
The page below reflects the actual plan pricing used by checkout and billing. No fake annual toggle, no hidden math.
Best for testing the product shape before you connect a real team or real business workflow.
For an individual operator or founder who needs real usage room, but not team governance yet.
For working analyst teams that need enough usage to run daily workflows without giving away the platform economics.
For organizations that need governance, security boundaries, auditability, and enough room for serious internal adoption.
For multi-team deployments that need SSO, commercial support, implementation help, and pricing that stays sustainable at scale.
The goal is not to look cheap on a screenshot. The goal is to support a durable software business while keeping customers confident about what they will pay.
LLM-backed query systems carry real variable cost. The plan design below keeps entry friction reasonable, but avoids the trap of underpricing serious usage.
It proves the product without turning your infrastructure into a subsidy program.
Founders and independent analysts can pay early instead of jumping directly from free to a team plan.
Token pools and question limits are generous enough to be useful, but disciplined enough to preserve margin.
Base fee plus usage components means large deployments expand revenue with actual adoption.
Billing is backed by actual logs, not loose estimates.
Every NL, SQL, and agent execution is tracked against the organization plan.
Prompt and completion usage is measured transparently with included allowances and published overage rates.
Per-key visibility makes internal chargeback and abuse detection much easier.
Base fee, token cost, and enterprise usage components all show up in organization billing endpoints and invoices.
Overages are intentional and explicit. That keeps the plans predictable for customers and viable for the business.
For one serious operator.
For high-frequency analyst work.
For governed internal teams.
For custom deployments and SSO.
The right tier depends on whether you need single-user speed, team collaboration, or governance and compliance controls.
| Capability | Free | Solo | Pro | Business | Enterprise |
|---|---|---|---|---|---|
| Monthly platform fee | ₹0 | ₹999 | ₹4,999 | ₹14,999 | ₹59,000+ |
| Users included | 1 | 1 | 5 | 20 | Commercial |
| Database connections | 1 | 2 | 5 | 10 | 10 |
| Questions per month | 10 | 600 | 3,000 | 20,000 | Commercial |
| Included tokens | 500 | 80K | 350K | 2.5M | Metered |
| Saved dashboards | — | ✓ | ✓ | ✓ | ✓ |
| AI agents | — | ✓ | ✓ | ✓ | ✓ |
| Advanced agents | — | — | — | ✓ | ✓ |
| RBAC and audit logs | — | — | — | ✓ | ✓ |
| Data masking | — | — | — | ✓ | ✓ |
| Microsoft / Google SSO | — | — | — | — | ✓ |
| Token overage policy | Hard limit | ₹1.20 / 1K | ₹0.85 / 1K | ₹0.45 / 1K | ₹0.10 / 1K |
Because it was not tied to a distinct annual checkout flow. This version is more trustworthy: it shows the actual monthly commercial plans used by billing and Razorpay. If you want annual contracts, Business and Enterprise can be handled through invoicing and sales-led agreements.
The answer is disciplined entry tiers and explicit usage rules. Free is intentionally small, Solo monetizes serious individuals, Pro is priced for team value rather than vanity adoption, and Business and Enterprise carry governance value plus enough base fee to cover platform cost.
For Free, Solo, Pro, and Business, the main commercial pieces are the monthly platform fee plus token overage if you exceed the included pool. Enterprise adds commercial expansion through user, query, and token usage components.
Paid self-serve upgrades use Razorpay Checkout. When an organization admin clicks upgrade, DataTwin creates a server-side order, opens Razorpay, verifies the payment, and activates the plan immediately.
Yes. That is the intended path. Start on Free, move to Solo or Pro when the workflow becomes useful, and move to Business once more people, governance, or audit requirements show up.
Usage is tracked per organization and API key. Billing endpoints and invoices reflect the underlying plan rules, token usage, and commercial components so the total is explainable, not mysterious.
DataTwin is not a brochure feature. It is an AI-backed operational product. The pricing now reflects that reality and gives you room to grow revenue without undercutting yourself on every active account.