English
Team edition

Plans, upgrades and enterprise capabilities

Updated 2026-09-04 · 1 min read · For desktop macOS 0.0.9 / Windows 0.0.7

What the team, business and enterprise tiers include, how they are billed and where their caps sit; and which tier SSO, audit logs, VPC deployment and bring-your-own object storage belong to.


Note

These are the hosted service's plans, sold in CNY through the Chinese site, where the subscription page is the authority on prices and inclusions. The desktop app's own pricing is on Free and paid and is a separate thing entirely.

Three tiers

Team Business Enterprise
Price from ¥6,588/year (about ¥549/month) from ¥23,988/year (about ¥1,999/month) to order
Starting size 40 people / 80 GB 100 people / 200 GB, up to 1,600 people / 3,200 GB No ceiling
Collaboration Several people at once, workspaces and projects Everything in Team Everything in Business
Permissions Admin / editor / viewer / user plus audit logs plus SSO, fine-grained permissions
Data Database connections, split-and-merge automation, shared dashboards plus an MQTT server, a higher connection quota, several workspaces plus VPC private deployment, bring-your-own object storage (OSS / S3)
Branding Your own logo Your own branding, dedicated support
Billing Annual Annual To order

Subscribing puts you straight into the hosted console; there is nothing to deploy.

Upgrading and renewing

The instance settings offer upgrading the tier, upgrading the capacity, and renewing. When you hit a cap the feature says so directly — projects, connections, collaborators, storage — and the message links to the upgrade page. An upgrade takes effect immediately and does not touch the data.

What the enterprise capabilities mean

  • SSO — connects to a company's own identity system, so staff sign in with one account and joining or leaving grants and revokes access through the directory.
  • Audit logs — every read, edit, export and permission change is recorded and can be traced.
  • VPC private deployment — the service runs inside your own network boundary.
  • Bring your own object storage — attachments and files land in your own OSS or S3 bucket rather than the platform's.
Did this page not answer your question? Browse the help centre, or write to support@tabledi.com — the inbox is read by the people who build TableDI.