Team Cloud
Billing and seats
Since 0.7.0 Requires Cloak Proxy 0.7.0 or later.
Team Cloud costs $5 a seat a month or $48 a seat a year, 2 seats minimum. Who takes a seat, adding and lowering seats, switching interval, refunds, and what happens when a subscription ends.
Team Cloud is billed per seat, monthly or yearly, through Polar, our merchant of record. Owners and billing managers manage it on the console’s Billing page.
Prices
Section titled “Prices”| Monthly | Yearly | |
|---|---|---|
| Price per seat | $5 a month | $48 a year ($4 a month) |
| Minimum | 2 seats | 2 seats |
| Maximum | 1,000 seats | 1,000 seats |
Prices are in US dollars, plus local tax. Polar collects tax, and a business tax ID if you add one at checkout. There’s no free trial.
Founding offer: the first 20 teams that buy 10 or more seats get 30% off their first year: on the first 12 months on monthly, or on the first year’s payment on yearly. It’s applied at checkout; Polar’s page shows it. The offer closes once 20 teams have bought with it (a checkout already open then can still get it), and a team gets it once. During that first year the team keeps at least 10 seats and stays on the plan it bought (monthly or yearly), as long as that subscription is the team’s; after it, seats and plan change as usual. We may end the offer for new teams at any time; teams that bought with it keep it for their first year.
Who takes a seat
Section titled “Who takes a seat”| Takes a seat | Doesn’t |
|---|---|
| Members and admins who’ve joined | The owner and billing managers, if they don’t use Cloak Proxy with the team |
| People with an open invitation | CI tokens |
| People being removed, until the removal completes |
Each seat is one named person: seats can’t be shared. Inviting someone needs a free seat; the owner or a billing manager adds seats in Billing.
Change seats
Section titled “Change seats”On Billing, click Change seats. Changing seats asks you to confirm with a passkey or a fresh email code.
- Adding seats charges the prorated difference for the rest of the period at once. The new seats count only when Polar confirms the payment; until then the console shows, for example, “Adding 2 seats… waiting for payment”.
- Lowering seats takes effect at renewal, with no credit for the current period. The console shows, for example, “Drops to 4 seats on 1 Dec”, and the seats stay usable until then. You can’t go below 2, or below the seats in use: “Remove members or invitations first”. A team on the founding offer can’t go below 10 during its first year. Keep 6 seats cancels a pending drop.
When someone leaves or is removed, their seat is free for an invitation once an admin’s Mac has carried out the removal (it does so on its own the next time it’s online), and stays billed until you lower the seat count.
Switch between monthly and yearly
Section titled “Switch between monthly and yearly”Switch to yearly or Switch to monthly on Billing. Polar charges or credits the difference as its checkout shows. It asks you to confirm with a passkey or a fresh email code. A team on the founding offer can switch once its first year ends.
Invoices and payment method
Section titled “Invoices and payment method”Open Polar portal on Billing asks you to confirm with a passkey or a fresh email code (the portal can cancel the subscription), then opens Polar’s customer portal, where you update the card and download invoices. When the team shares the owner’s Polar billing account with their other plans, only the owner can open it (see Personal Cloud and Team Cloud billing). The Billing page also lists every order: date, reason, seats, amount and refund state.
Refunds
Section titled “Refunds”You can get a full refund of any team payment within 30 days of the charge, on request. Email team-support@subcloak.com from the owner’s or a billing manager’s address.
- Refunding a period’s charge (the first payment or a renewal) ends the team: it becomes read-only for 30 days, then its data is deleted.
- Refunding a seat-change charge removes those seats. If that leaves more people than seats, new invitations and Macs are refused at once, and after 7 days the team is read-only until members are removed or seats are added. The same applies after a renewal at fewer seats, a decrease in Polar’s portal, or a chargeback.
- Deleting the team refunds automatically: every payment made in the 30 days before the owner asked is refunded in full when the deletion runs. See Delete a team.
Cancel
Section titled “Cancel”Cancel subscription on Billing (owner or billing manager, with a passkey or a fresh email code). The team keeps working until the end of the period you’ve paid for. You can undo it until then.
When a subscription ends
Section titled “When a subscription ends”| Situation | What happens |
|---|---|
| Cancelled | Everything works until the end of the paid period. There’s no extra grace period |
| A renewal payment fails | Everything works for up to 7 days while Polar retries |
| Then | The team is read-only for 30 days: Macs can read and export team data, but can’t change it. Monitors and hosted mocks stop at once |
| After 30 days read-only | The team’s data is deleted from Subcloak’s servers |
Data on members’ Macs isn’t touched by any of this, except that a Mac deletes its copy of team data when its owner leaves or is removed.
Delete a team
Section titled “Delete a team”The owner can delete the team in the console’s Settings › Delete team…, after confirming with a passkey or a fresh email code. Deletion always waits 72 hours. The owner and every admin get an email with their own link that cancels it (each link works once), and the owner or any admin can also cancel it in the console’s Settings until then. Asking closes the team at once: it’s read-only on every Mac during the 72 hours. Deleting the team sets its subscription to end at its period end, and any payment the team made in the 30 days before the owner asked is refunded in full when the deletion runs. When it runs, the team’s data is deleted from Subcloak’s servers, including its members, console roles, SSO settings, domain and SCIM records; billing records are kept. Cancelling the deletion reopens the team but leaves the subscription set to end: resume it in the console’s Billing to keep the team.
The owner’s Personal Cloud account can’t be deleted while they own a team, because the team may be billed with the same Polar account: delete the team first, or write to team-support@subcloak.com to move it.
Personal Cloud and Team Cloud billing
Section titled “Personal Cloud and Team Cloud billing”Personal Cloud and Team Cloud are separate subscriptions. A Team seat doesn’t include Personal Cloud, and Personal Cloud doesn’t count as a seat. Each team’s subscription is billed to its owner at Polar. If the owner already pays for Personal Cloud or another team with the same address, the team is added to that same Polar billing account, and only the owner can open its billing portal, because the portal shows all of the owner’s plans. When the owner also pays for Personal Cloud, their Manage billing in Cloak Proxy’s Personal Cloud settings opens that same Polar billing account on their Mac, so the team’s subscription can be cancelled there too, without the console’s confirmation. Billing managers see the team’s seats and invoices in the console; for anything in the portal they ask the owner, or write to team-support@subcloak.com. If the owner’s address belongs to a Polar billing account that isn’t theirs, checkout stops and asks you to write to team-support@subcloak.com.
Limits per team
Section titled “Limits per team”| Limit | Value |
|---|---|
| Macs per member | 5 (or the Devices per member policy) |
| Encrypted storage (spaces, history, library, CI recordings, vault) | 10 GB for each seat; small items and their history also share a 4 GB database per team, of which each member may use a share (a file attached to an item counts toward it too, and each Mac may have at most 10,000 uploaded files that no item uses yet). Once a member’s share or the database is used up, their writes, access-list changes in spaces they manage included, wait until room is freed; an admin’s access-list changes (in spaces they manage) always go through |
| Spaces | 2,000 at a time (deleting one frees its place); each member makes at most 100 new ones a day |
| CI | 20 tokens; 300 runs a month for each seat; 100 MB per recording |
| Pair debugging | 20 hours a month for each seat; 10 viewers; 8 hours per session |
| Monitors* | 5 for each seat, at most 100; every 5 minutes or longer; 500 alerts a month |
| Hosted mocks* | 10 sets; 10,000 requests a month for each seat; 20 a second |
| Notification emails | 50 per member a day |
| Invitations | 200 a day |
The console’s Usage page shows how much of each you’ve used. Over a limit, the action that would exceed it is refused with the limit named, and nothing on your Macs stops working. When the team reaches its monthly cap for monitor alerts or for hosted mock requests, admins also get one email that month.