The short answer
No. There is no team, workspace, organization or seat concept anywhere in Whizi: not in the data model, not in the routes, and not in the pricing path. Billing is per individual account, and a subscriber's tier is derived in exactly one place, from that user's own subscription. Everyone who wants to use Whizi needs their own account and their own subscription.
The three plans that exist are individual plans: Starter at $15.99/month, Pro at $29.99/month and Powerhouse at $49.99/month. Those three tier names are the only plans the pricing path will even parse, so no fourth paid tier exists to be a team tier.
| What people look for | What Whizi has |
|---|---|
| Team or workspace plan | Does not exist. Three individual tiers only |
| Per-seat pricing | Does not exist. No seat-based, enterprise, education or student tier |
| Admin console, invites, member management | Does not exist. Nothing represents more than one user on an account |
| Pooled credits across people | Does not exist. Allowances are per account |
| Shared chat library or shared prompt library | Does not exist. A conversation can be published as a read-only link |
| A developer API to build your own team layer on | Does not exist. No public API, no API keys, no personal access tokens |
For a buyer: Whizi is priced and built for one person per account. A team of five is five accounts and five subscriptions, bought separately.
What "billing is per individual account" actually means
Tier resolution happens once, on the server, from the subscription attached to the requesting user. Nothing reads a parent organization, a group, or a payer other than the account making the request. So one person paying does not lift anyone else, and a plan cannot be spread across two logins.
Every allowance follows the same rule. Credits, message limits, voice minutes and image generations are counted against the account that spent them, not against a pool. Starter carries 400 credits per monthly billing period, Pro 2,000 and Powerhouse 8,000, and those are one person's allowance each. There is no pool, no transfer and no rollover between accounts.
Projects do not change this. Projects are folders of conversations with pinned files and per-project instructions, and they are available to any signed-in account, but a project belongs to the account that created it. There is no member list on a project and no way to hand one to a colleague.
A colleague on their own free account is not blocked from trying Whizi first: a free account is not model-gated and can try any text model, but it has a lifetime allowance of 7 messages that never resets. After that the reply is Your free messages are used up. Start a subscription to keep chatting., HTTP 402 free_limit_reached.
Sharing one login instead: three things that happen
The first is an anti-abuse gate. When more than 3 distinct device or session keys have been seen on one account in the last 24 hours, the server answers Account sharing limit reached. Please use your own Whizi account., HTTP 403 account_sharing_limit. That is neither a billing refusal nor a tier refusal, and there is no seat concept to buy your way past it.
The second is the generation lock, which bites long before the sharing gate does. Only one generation can run per account at a time, enforced by a per-user lock, so two people on one login can never generate concurrently. The second person gets Generation already in progress. Please stop it or wait for it to finish., HTTP 409 generation_in_progress. On a shared login this is not an edge case, it is the normal state whenever two people are working at once.
The third is the terms. The Whizi Terms of Service grant "a non-exclusive, non-transferable, revocable license" to access the Services, "solely for your personal, non-commercial use or internal business purpose". On registration you also "agree to keep your password confidential and will be responsible for all use of your account and password". Handing the login round is on the account holder.
There is also nothing to gain from it privately. The chat history, memory and projects of one shared login are visible to everyone who holds that password.
What a group can actually do today
One account and one subscription per person. This is the supported shape. Each person subscribes from their own account, on whichever tier suits their work, and nothing about one account depends on another. Plans can differ per person: one Powerhouse and four Starters is a perfectly normal arrangement, because there is no group to keep consistent.
Share individual conversations read-only. A conversation can be published behind an unguessable public link that anyone can read in a browser without a Whizi account. The link is read-only, stripped of user ids, emails and internal fields, screened for safety before it goes public, and revocable at any time. Revoking deletes the row, so a revoked link and a link that never existed both return This shared chat is no longer available. as HTTP 404. The walkthrough is in share a conversation.
Hand work over as files rather than as access. A chat answer can produce a real .xlsx or .docx that downloads in the browser, which is usually the right way to get a result to someone who is not on Whizi. Separately, GET /api/account/export returns the account's data as one downloadable JSON file, reachable as Export Data in Settings under Account. See export chats and files.
What is not available as a workaround: there is no public or developer API, no API key issuance and no personal access tokens, so a shared internal tool cannot be built in front of one subscription either.
Invoicing several people at once
There is no self-serve way to do it. Checkout is per account, and the product has no basket that buys more than one subscription.
One exception exists on the operator side and it is deliberately not a product feature: entitlements can be granted by hand for an invoice covering several seats, paid outside the app. That is a manual arrangement handled by Whizi, not a setting anyone can reach in the interface, and it does not create a team object, an admin, or any link between the accounts it grants.
If that is what you need, support is the only route to it. Everything else about billing, including where to cancel and when changes take effect, is in billing and cancellation.
Before you take Whizi into a company
Two things in the Terms of Service matter to anyone evaluating Whizi for work.
The agreement can be entered by a company. The terms are "made between you, whether personally or on behalf of an entity" and the license covers "internal business purpose". So business use is contemplated, it is simply business use of individual accounts.
Regulated work is excluded. The terms state that the Services "are not tailored to comply with industry-specific regulations (Health Insurance Portability and Accountability Act (HIPAA), Federal Information Security Management Act (FISMA), etc.), so if your interactions would be subjected to such laws, you may not use the Services", and that you may not use the Services in a way that would violate the Gramm-Leach-Bliley Act. That rules out the health, federal and financial-services cases before the team question even comes up.
For where data goes and what is retained, which is the other question procurement asks, see what Whizi does with your data.
- Nothing in the data model or the routes represents more than one user on an account
- Three individual tiers only: Starter, Pro and Powerhouse
- No seat-based, enterprise, education or student pricing exists
- Billing is per account and tier is read from that user's own subscription
- More than 3 device or session keys in 24 hours returns
Account sharing limit reached. Please use your own Whizi account. - One generation at a time per account, so two people on one login block each other
- Read-only share links and file exports are the supported ways to pass work around
- Multi-seat invoices are a manual operator arrangement, not a self-serve feature
Frequently asked questions
My colleague has no subscription. Can I add them to mine?
There is nothing to add them to. Their tier is read from the subscription on their own account, so an account with no plan gets a 7 message lifetime allowance of its own and nothing more, however much anyone else is paying. Past that the reply is Your free messages are used up. Start a subscription to keep chatting., HTTP 402 free_limit_reached, and a route that requires a paid plan answers Choose a subscription to use Whizi., HTTP 402 subscription_required. Why an account that is paying can still hit that second refusal is covered in subscription not active.
I already subscribe. Can I move my plan onto a colleague's account instead?
No. The plan stays with the account it was bought on, because tier is derived in exactly one place, from the subscription attached to the requesting user, and nothing in the data model represents more than one user on an account. There is no reassignment and nothing to reassign it to. The working version is that they subscribe from their own account and you cancel yours, from Settings under Subscription. When cancellation takes effect is in billing and cancellation.
We shared one login and now we want to separate. What happens to the chat history?
It stays with the account, not with whoever typed it, so changing the password locks the other people out of that history rather than dividing it. Nothing splits an account's chats across two accounts. GET /api/account/export hands you the account's data as one JSON file, from Export Data in Settings under Account, but that file is not an import format: Whizi's import accepts exactly two sources, ChatGPT and Claude, so a Whizi export cannot be loaded into a second Whizi account.
Does the 3 device limit count my own phone and laptop as two?
Yes. The guard counts distinct device or session keys seen on one account in the last 24 hours, not people, and it fires once more than 3 have been seen: Account sharing limit reached. Please use your own Whizi account., HTTP 403 account_sharing_limit. One person on a phone, a laptop and a tablet sits inside that. The same person plus a colleague on two more devices does not. Signing in on several of your own devices is supported, with the separate rule that only one generation can run per account at a time.