Plans and AI usage
Before choosing a plan, estimate members, projects, storage, recording, and AI work. A plan name is not a substitute for actual entitlements and feature verification; use the active subscription and agreement.
Where to check your subscription
Open the Portal user menu and choose subscription management. Overview shows the plan, status, period, and resource usage. History provides records; Plans provides available comparisons.
Current principal plans
Checked against production plan information and the subscription page on 2026-09-10. Annual prices are not monthly-payment offers. Current subscriptions and individual agreements govern applicable terms.
| Plan | Annual price, NT$ | Needs to evaluate |
|---|---|---|
| Basic (Plus) | 6,000 | Small teams and limited projects |
| Growth | 30,000 | Concurrent projects and more shared material |
| Pro | 60,000 | More members, projects, and AI work |
| Flagship | 150,000 | Larger teams and resource requirements |
| Enterprise | By agreement | Individually scoped implementation and services |
Starter is a proposed packaging name; the current interface uses Basic. Flagship and custom Enterprise are different plans. A contact-sales Enterprise entry is not a free offer. Max is marked for internal testing and is not a general quotation plan.
Main resource allowances
| Resource | Basic | Growth | Pro | Flagship |
|---|---|---|---|---|
| Member seats | 6 | 10 | 20 | 100 |
| Projects | 5 | 20 | 50 | 100 |
| Websites | 6 | 10 | 20 | 100 |
| Storage, GB | 10 | 50 | 150 | 500 |
| Recording minutes per session | 60 | 120 | 180 | 300 |
| Recording minutes per month | 300 | 900 | 2,000 | 6,000 |
Do not assume archived projects are excluded from quotas. Feature flags do not establish complete governance workflows. External review rooms, cross-output version locking, full evidence packages, SSO, and SCIM require explicit scope confirmation.
Storage, knowledge processing, and AI outputs differ
Original files use storage. Parsing, OCR, transcription, and indexing are knowledge processing. Conversations, analysis, and file generation consume AI work resources. Different entries trigger different processing; neither universal free upload nor universal full analysis should be assumed.
Credits are platform usage units, not model tokens. Check available balance before large jobs and review estimates where provided. Some entries offer estimates; that does not establish an identical confirmation flow for every AI task.
Before purchasing additional usage
Determine whether the limit concerns storage, recording, entitlement, or Credits. For Credits, inspect the top-up entry and confirm workspace, currency, amount, and allowance before deciding. Available options are defined by the current screen.
If a task repeatedly fails, retain its error and status and ask an administrator to investigate rather than repeatedly retrying or purchasing more. See troubleshooting.
Estimate with representative work
Observe a representative week: files, recording minutes, report revisions, and active members. Validate a small batch before a large import instead of moving unnecessary historical material.
Public-information corrections and appeals are not gated by subscription payment. Distinguish platform fees from donation processing; see donations.
Estimate from work types
List typical summaries, long-document analysis, transcription, presentations, and file generation. Equal operation counts need not consume equal resources; input size, processing, and output matter.
Run a representative trial
Use permitted test material of realistic size and complete import, organization, and delivery. Record the operations and displayed usage, then compare with monthly workload. A short question cannot estimate extensive media processing.
| Estimate | Information needed |
|---|---|
| Membership | Active workers and roles |
| Storage | Types, sizes, retention scope |
| AI work | Typical tasks and frequency |
| Delivery | Actual files, websites, and output needs |
Read usage with the plan
Distinguish plan resources, current allowance, and per-operation reporting. Credits are neither fixed word counts nor uniform per-task prices. Where no estimate is shown, examples are not guaranteed pricing.
Reassess with actual work records when requirements change. Use current available plans and terms before purchase, distinguishing public options from internal tests.