Pricing

Start with your work.
Grow into a team.

A personal agent with room to grow. Bring your own model key, then bring your workflows, knowledge, and people together.

Prices in USD ($). Fixed rate: USD 1 = CNY 6.5; per-user prices are rounded to the nearest dollar before totals are calculated. Model provider usage is billed separately.
For individuals

Standalone

Your own agent, in your own workspace.

FreeSoftware, forever

Use your own model API key.
macOS Apple Silicon and Windows x64 previews are available.

Explore downloads
  • 10 personal knowledge spaces
  • 10 workflows and 5 scheduled tasks
  • 5 listeners and 5 triggers
  • Local workspace for files and deliverables
  • Drawing review and workspace file previews
  • MCP tools and external event connections

Unsigned previews · See download requirements and validation status.

For business systems

Enterprise

Build around the way your business works.

Let’s talkA plan for your deployment

A scoped proposal for your systems,
users, and delivery requirements.

Request a scoped proposal
  • Team Workflow rollout planning
  • Custom workflow, schedule, and event capacity
  • Private deployment assessment
  • PLM, order system, and internal API integration
  • Business knowledge and workflow setup
  • Training and support agreed in your proposal
Explore Team Workflow
Plan ahead

A clear starting point.

Estimate your Team Workflow software subscription.
We’ll scope your deployment together.

Minimum 5 users. Larger team? Let’s talk.
$9,120 billed annually for 5 users Equivalent to $760 / month

Software estimate only. Model API usage, hosting, custom integrations, and implementation are separate. Applicable taxes and final terms are confirmed in your proposal. No payment is collected on this site.

The right fit

Your work. Your setup.

Compare the room to build, as well as the tools you can use.

Compare Standalone, Team Workflow, and Enterprise
CapabilityStandaloneTeam WorkflowEnterprise
Knowledge spaces10UnlimitedUnlimited
Saved workflows10100Custom · 100+
Scheduled tasks550Custom · 50+
Listeners550Custom · 50+
Triggers550Custom · 50+
Allowance scopePer installationShared across your organizationAgreed deployment
Model accessYour API keyCentral setup plannedAgreed deployment
Knowledge managementPersonal spacesShared spaces & assignmentBusiness knowledge setup
Workspace files & drawingsIncludedIncludedIncluded
Event protocolsHTTP / MQTT / RabbitMQHTTP / MQTT / RabbitMQIntegration scope agreed
Users & feature allocationPersonal usePlanned · early accessRollout scope agreed
API usage visibilityProvider accountPlanned · early accessReporting scope agreed
Deployment & onboardingSelf-configuredGuided pilotScoped implementation

Counts refer to saved configurations, including disabled ones. Team allowances are shared across the organization, not multiplied by seats. Knowledge entries and workflow steps do not each count as spaces or workflows. “Unlimited” means no plan-level space count cap; model usage, storage, and execution capacity remain separate.

Launch plan allowances are being prepared for the licensed releases; preview builds may not enforce these quotas. Team management is in development. Existing workflow and event capabilities provide the foundation; a pilot confirms the features available for your deployment.

A few useful answers

Before you get started.

How do the capacity limits work?

Standalone includes 10 knowledge spaces, 10 saved workflows, 5 scheduled tasks, 5 listeners, and 5 triggers per installation. Team Workflow includes unlimited knowledge spaces, 100 workflows, 50 scheduled tasks, 50 listeners, and 50 triggers, shared by the organization. A scheduled task or event connection counts even when disabled. Removing an unused configuration frees that allowance. A workflow run does not use up a saved-workflow slot; model usage and infrastructure are billed separately. Enterprise capacity is agreed in your proposal.

Does “unlimited” include compute and storage?

No. Unlimited knowledge spaces means no plan-level limit on the number of spaces. File storage, model requests, and execution concurrency depend on your deployment and provider. These allowances describe the launch plans; quota enforcement is being prepared for the licensed releases.

Does “free” include model usage?

No. Standalone software is free. You configure an API key from your chosen model provider, and that provider bills you for usage. Team Workflow software pricing also excludes model usage.

Can I download Tubun Agent right now?

macOS Apple Silicon PKG and Windows x64 EXE previews are available on the download page. Both are unsigned previews. Mac notarization and Windows PC acceptance checks are still pending. For help getting started, request a demonstration.

What does Team Workflow early access mean?

We’re bringing existing workflows, knowledge spaces, and event connections into a managed team experience. User administration, feature allocation, and central usage reporting are planned capabilities. We agree on a pilot’s actual scope and delivery terms with you before purchase.

How is the subscription calculated?

Annual billing is $152 per user per month, charged for 12 months, with a minimum of 5 users: $9,120 per year. Monthly billing is $198 per user, with a minimum of 5 users: $990 per month. The calculator shows software pricing; model usage and implementation are separate.

Do employees need to understand agents or configure API keys?

The Team Workflow direction is a simpler experience for employees: an administrator prepares the model configuration, available features, and shared knowledge. Employees use the tools assigned to them. This management layer is being developed for early access.

Can we keep personal and company knowledge separate?

Yes, that is the intended Team Workflow setup: administrators maintain and assign company knowledge, while individuals can keep a personal space. Whether that personal space lives on a local device or in the team deployment is confirmed during rollout planning.

Can you connect to our PLM or order system?

We can assess systems with documented APIs or message interfaces. HTTP, MQTT, and RabbitMQ connections form the event foundation. Authentication, field mappings, file handling, and write-back behavior are scoped and tested against your environment; custom work is quoted separately.

Start with one useful workflow.

Bring a real task. We’ll help map the next step.

Discuss your use case