Workspace Plans
Part of the MountDev Ops Subscriptions documentation. Updated November 14, 2026
MountDev Ops Subscriptions documentation | Updated November 14, 2026
Our Commitment
MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.
Every update passes all 4,402 automated checks before it ships, and every screen change is walked through before release.
What It Is
If you sell your clients a workspace, you set its plan yourself, as an ordinary product in your own account. Its price is the product's price. What it includes each month and what anything beyond that costs are fields on the product. MountDev Ops holds no price, allowance, or rate of its own: it only counts, and each client's Usage shows the plan you sent.
Every account works the same way. Nothing here names an account, and no account has terms of its own in code.
Make a Plan Product
In Products, add or open a product and set:
- Workspace plan use: Plan for the plan itself, or Extra Runner for the product that is the price of an Extra Runner. Leave it empty for any other product.
- Name, Price, Billed every: the plan's name, what it costs, and how often (Month or Year). The name is the plan's label on your client's Usage.
- Plan terms start on: the date the terms apply from. New terms apply from the first day of the next month on or after this date, so a month is never priced two ways. Empty means today.
- Billing starts on: the date you begin billing the plan. Until then your client's Usage shows the plan on its own and leaves it out of the total.
- Included each month: actions, background tasks, and GB of data storage, file storage, and embedded file delivery.
- Price beyond: the price for each 1,000,000 actions, each 1,000,000 background tasks, and each GB of data storage, file storage, and embedded file delivery. A price left empty means nothing is added for that item.
These are prices, so they follow your price rules: owners always see and change them, and admins only as an owner chooses (Permissions). Members never do unless an owner gives their role the field. An AI agent or key never sends a plan.
Send It to Your Clients
Send Plan Terms (action subscriptions.plan_terms.publish, owners only) sends each client account the terms of the plan product it has an active subscription line for. A client with no such line, or an account you do not provide for, gets nothing and is counted as skipped. Each client gets only its own plan: a label and numbers, never a name, a record, a key, or an amount to charge. The same terms sent again are kept once; new terms replace the old from their date, and the old are kept.
The message goes the same way as every message between accounts: it waits in a queue and is tried again until it goes through.
What Your Clients Send Back
Once a month, after the month is over, each client's workspace sends the counts for the month: a number for each of the five items, nothing else. See What Each Client Used (action subscriptions.plan_terms.usage, owners only) shows, for a month, each client's counts, what is beyond its plan, and what that comes to at your rates, to the cent, with the total. It reads only; it makes no invoice and charges no one. Charges still go through Invoices, which never charges a customer twice.
Who Can Use It
Owners only (permission subscriptions.plan_terms). Both actions are for people only, never for AI agents or keys, because they are prices and the first reaches your clients.
What Your Client Sees
A client sees its plan's name and price on Usage, what it includes next to what it used, and, when you set one, the price of an Extra Runner. With no plan from you, its Usage shows counts only (Usage). A client never sees your rates for your own provider, and never another client's plan.
