Create Accountor Login
Docs

Usage

Part of the MountDev Ops Workspace documentation. Updated November 19, 2026

MountDev Ops Workspace documentation | Updated November 19, 2026

The Usage button in the menu shows what your company has used this month: your plan, the five things it includes, what your business did, and whether anything will be added to your bill. Open it any time, so there are never any surprises.

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 8,865 automated checks before it ships, and every screen change is walked through before release.

Included, Never Stopped

Nothing you use is ever stopped, slowed, or blocked. MountDev Ops counts what you use and nothing else. Your plan, what it includes each month, and what anything beyond it costs are set by your provider, the company you buy your workspace from, and shown on Usage exactly as it sent them. Usage starts fresh on the first of each month (UTC).

Your Plan

Your provider sends your workspace its plan terms: the plan's name, what it costs, an amount of each of the five items it includes every month, and a rate for anything beyond. Usage shows them as they came, and shows nothing it was not sent. Adding an app never changes your plan's price or what it includes.

If your provider has not set a plan for your workspace, Usage says "Your provider has not set a plan for this workspace." and shows your counts only: no plan card, no included amounts, and no estimate.

When your provider sends new terms, they apply from the date it names, and never inside a month that is already running, so a month is never priced two ways. Earlier terms are kept.

Once a month, as soon as the month is over (just after midnight Pacific on the 1st), your workspace sends your provider its counts for the month so your provider can price them at its own rates. The message holds a number for each of the five items and nothing else: no name, record, or file.

Usage Pools

A company that provides workspaces to its own clients (a partner) can pool those clients' usage into its own. The partner adds a client account to its pool (the owner's Add to Usage Pool, action core.pools.add), and from then on that account's usage counts toward the partner's. The client's workspace says in one plain line that its usage counts toward its provider, and shows nothing of the pool or of any other account.

  • One allowance. The partner's plan includes one amount of each item every month, shared by the partner and every account in its pool. 200 client accounts do not each bring an allowance.
  • How counts travel. After a month is over, each pooling account sends the partner its counts for the month: a number for each of the five items and nothing else, never a name or a record. The partner's own counts go to its provider as soon as every pooling account's counts are in, and by 3 AM Pacific on the 1st at the latest, so they are in the same invoice. They carry how many accounts pool and an opaque account id with five numbers for each. An account's counts that come in after that are sent on in a short follow-up message, once, and never counted twice.
  • What the partner sees. The pool for a month (action core.pools.read, owners only): each account's part, with the partner's own name for it, and the total. The parts add up to the total.
  • Billing. The partner's provider prices the pooled counts beyond the one allowance at its own rates, as lines on the partner's invoice: one for each item beyond, then a line for each account's part at $0, counts only. Nothing is charged to a pooling account by this. What a partner charges its own clients is its own products in its own account, and its provider never sees it or takes a share of it.
  • Where it is on screen. For the partner (owners only): Client Accounts in the Partners menu lists every account that pools to you with the day it started and its status, with Add Account to Pool (only accounts you provide for; action core.pools.list lists them) and Stop Pooling on each row, which asks first in a small pop up. Usage has a Pool tab: last month's pooled actions against the plan's one allowance, how it adds up (your own workspace plus every account, once), and a table of each account's part with a total row that equals it. The table scrolls inside its own box on a small screen. Your other companies are a Linked Companies card on Settings, Company, with Unlink; they pool the same way. For a pooling account, Usage shows its own plan and one plain line: "Your usage counts toward your provider's."
  • Names. An account shows by its plain name: your CRM company that holds the account, else the name the account gave in its own Get Help request, else "Unnamed client account" with a line that says to link it to a CRM company so it shows its name. When several are unnamed, the picker and the pool table number them. A name is worked out only from what your own account holds; MountDev Ops never reads the other account to find one, and an account's id is never shown.
  • Stopping. The partner (Stop Pooling, core.pools.stop) or the account's owner (core.pools.leave) can end it. The account keeps all its data. A month counts an account only when it was in the pool on that month's last day, so it drops out from the next month.

Combine Billing

An owner of several companies can pick one to pay and have the others' usage count toward its plan, on one bill, through the same usage pool. Each company keeps its own data, people, and settings, and linking gives no one a view into the other company. It is the Combine Billing page in Settings (the page that was called Linked Companies), for owners only; it opens with a short explanation and an example. It works as follows (owners only, never an AI agent or key):

  • On screen. Link a Company (two steps in a pop up) lists only companies you own, then shows what changes on your bill before it sends the request. The list shows each linked company, what it used this month so far, when it starts, and Unlink; a request that has not been answered shows Waiting for its owner with Cancel Request. In the company that was asked, the same page says who asked, with Review Request, Accept, and Decline, and afterward Stop Combining. On a phone each row is its own card of label and value pairs. The bill itself still changes only by the plan rules your provider has set.
  • Asking. The paying company's owner picks a company they own (core.pools.owned lists only those, never this company, one already waiting or in the pool, or one that pools elsewhere) and asks (core.pools.ask). The request holds only a start day and the paying company's own name. Nothing is linked, counted, or billed until the other company's own owner says yes. A request is made only when the hub confirms one person owns both companies; with no answer it is refused, with one answer that does not say whether the company exists.
  • Answering. An owner of the asked company accepts (core.pools.accept) or declines (core.pools.decline) from inside that company. Its own name goes to the paying company only with the yes. The paying company's owner can withdraw a waiting request (core.pools.cancel).
  • When it counts. A link starts on the 1st of the next month and ends on the 1st of the next month, whoever ends it (core.pools.stop by the paying company, core.pools.leave by the linked company). This month's usage stays in the pool through its last day, so nothing is prorated, refunded, or billed twice.
  • One at a time, no chains. A company with a request waiting cannot take another, a company that pools to another cannot pay for others, and a company that pays for others cannot be asked.
  • Used this month so far. Once a day a linked company sends the paying company its month so far, as five numbers and nothing else, and the paying company shows the actions (core.pools.list, running). A later day replaces an earlier one; it is only for showing and is never billed. What is billed is the month's final counts, as before. It is taken only from a company in the pool.
  • You are told. Every owner and admin of a company gets a notice (Needs You Today, linking to Combine Billing) when a request arrives, when your request is answered, withdrawn, or the other company stops. A notice holds words only, a company name and a date.
  • Nothing is charged. None of this creates a charge, a payment, or an invoice. Only Invoices charges.

Beyond What's Included

Your provider's plan has a rate for each of the five items. Rates are prorated and rounded to the cent. Storage is the size kept now. A GB is 1,000,000,000 bytes. Processing time is never billed; it is covered for everyone as fair use. If your plan has no rate for an item, nothing is added for it.

Runners

Background work is done by runners, which work side by side. Every company has 1 runner included. Extra runners only make work finish sooner and use the same usage as everything else, so the work counts the same however many runners do it. If your provider has set a price for Extra Runners, the Extra Runners pop up shows it, and it names no price when your provider has not. With 1 runner, a big job (for example 150,000 steps every Monday at 6 a.m.) can take hours; add runners and it finishes in a fraction of the time. A workflow shows about how long it takes with your runners, and with more, before you turn it on. Nothing is ever stopped or dropped while it waits for a runner.

What Each Item Counts

  • Actions: every click, save, page, and API call. Each request your workspace answers counts once: opening the workspace, signing in, every screen's request and every save, each REST API call with an API key, each AI agent call (connecting, listing tools, and each tool used), each visit or post to one of your public pages (a website form, the chat bubble, an invoice or proposal link, an upload link), and each file uploaded (each piece), downloaded, or sent to one of your websites. A request your workspace refuses or that fails never counts. The workspace's own program files (its scripts, styles, and icons) are the same for every company, are kept by your browser, and never reach your workspace, so they never count. The live connection that keeps your screens up to date does not count.
  • Background work: automations, scheduled jobs, emails, and webhooks handled for you. Each workflow step that does something (an action in an app, each try at calling an outside service, an AI step, or a send); starters, filters, formatting, branches, and delays are free; each check of an outside service for new items; each scheduled job that was due and ran (an app's reminders, its outgoing email queue, the monthly run); each try at sending a webhook or calling a connected service, retries included; each webhook received (your inbound webhooks, and Stripe's notices to Invoices); each email received and taken in; each email sent; each import batch (one call of up to 500 rows, however many rows it has); and each time your workspace wakes up on its own to do this work.
  • Your Own Storage: what workflows did in a bucket you own: storage calls made, bytes put, and bytes removed. These are counts and sizes only, never a name or contents. They are not part of the plan's billed meters; any price for them is your own account's data.
  • Data storage: the size of your company's own database: every record, setting, and its history. As a company grows, older history and Activity Log entries may be kept in monthly archives of your own, still shown everywhere they were before; Data storage adds up every part. The space each part needs just to exist, and the bookkeeping MountDev Ops does to keep the parts in step, are never counted.
  • File storage: the size of every file kept on your records (in Files and on any record's Files card). A deleted file stops counting at once. A file attached to several records counts once.
  • Embedded file delivery: every byte your workspace sends for the files and folders you published for your websites and apps (Files on Your Websites), counted as it is sent, for the whole of each answer (a part of a video counts the part). Browsers and our network keep a copy for 10 minutes; a copy they already kept is sent without reaching your workspace, so it is never counted or charged. Each request also counts as one action, like any public page.

What the Panel Shows

The panel opens with a short loading bar, then shows its numbers in tabs at the top, each fitting the screen. Every figure shows once.

  • Overview: your plan (its name and what it costs, as your provider sent them), and the bottom line: "You're within your plan" in green, or about how much this month will add beyond what's included, projected from the pace of the month so far (actions, background work, and embedded file delivery), with each item's part when more than one is beyond. This is the one place that amount shows. Beside it, the Next Bill Estimate: the true total of your next bill, with MountDev Ops as its own block. Until your provider's billing start date, that block is labeled "Starts when your provider begins billing this plan" and is not added to the total. For Managed Services clients, what makes up the bill: each website's monthly services, and its usage beyond what's included.
  • Usage: the five items, each as a big number with a bar against what is included (for example "Used this month | 1,000,000 actions included", when your plan includes that). Use beyond what's included shows in blue as "Beyond what's included"; its cost is on the Overview.
  • Websites (Managed Services clients): each website's services, each with what its plan includes next to what was used this month, with a bar for each: storage and emails for hosting (more with WordPress Pro), and bandwidth as used, with no overage charge and so no bar; emails sent for Transactional Email, with its price ($1 per 1,000 emails sent, $5 minimum a month per domain) and no bar, since no emails are included; monitored forms, elements, and pages for maintenance. Below them, the monthly report's key numbers: uptime and the busiest day, emails delivered and bounced, updates applied, backups, security scans, and attacks blocked, and the mobile speed score. A service with no numbers yet says when they will show (storage and bandwidth about two days after a website is live on our hosting, for example). A test website is never measured, and says so. The newest monthly report is a click away. A client with Managed Services only sees Websites and Next Bill.
  • Activity: what your business did this month: records added, records changed, emails sent and received, searches, automations run, files stored, forms submitted, proposals signed, payments recorded, video meeting minutes, and minutes transcribed. None of these are billed on their own. Video meeting minutes are each person's minutes in a video meeting, rounded up to the minute and counted when the meeting ends; your own Telnyx account bills you for them directly. Meeting Minutes (Planned) are each person's minutes in a Built-In Meetings room, counted in your own workspace when they leave, and stay at 0 until Built-In Meetings are available. Minutes transcribed are the minutes of meeting recordings transcribed automatically, counted when each transcript is saved. Below them, the year so far once it says more than this month, and every other count this month.
  • Technical Details (owners and admins only): what running your workspace takes this month, never billed: the rows of data each app read and wrote (the workspace's own upkeep listed last as Platform overhead), the requests your workspace answered, requests between the parts of your data, the seconds it was busy, and the size of each part (your main database, and each month of archived history).

Compared with last month: next to a count, a small "Up 12%" or "Down 8%" shows how it compares with last month, only when last month has a number to compare with. Your workspace keeps counts by the month, so it compares this month at its pace so far with all of last month, from about the third day of the month. A website's numbers are kept by the day, so they compare with the same days last month. Storage kept now has no comparison.

How Counting Works

Usage is counts only: how many and how much, never what. The counts are kept in your own company database, by month (action core.usage reads them; reading changes nothing). Each count is made by your own workspace as the work happens, once, so the totals can be checked against what happened. Your provider reads the totals to bill you and never the records behind them.

By Day

Each billed item that is counted as work (Actions, Background Work, and Embedded File Delivery) is also kept by the day, in your own company database. The action core.usage.days reads one item's days for a month: one row for each day with the workspace's part and each website's part, adding up to the day, and the days adding up to the item's total. Days run midnight to midnight UTC, the same as your month, so the days always add up to what your provider is sent. A month from before days were kept has no day rows, and the answer says so (has_days is false) while the month's total stays as it was. Reading changes nothing, and it shows counts only, never what was inside the work.

For AI Agents

AI agents can read usage (core.usage) and one item's days (core.usage.days) on your behalf. Each call an AI agent makes is one action, like any other.

Email as Its Own Usage Lines Planned

Once built, email stops counting as Background work. Emails sent become two lines of their own, Transactional Email (sent because of your action or an account event, such as receipts, invoices, proposals, sign-in codes, notifications, and ticket replies) and Marketing Email (campaigns, newsletters, and any bulk send to a list), shown per website and per app on this screen, day by day, with a warning before an allotment runs out. Which line an email counts in is decided by the feature that sends it, not by you. This replaces counting emails as Background work.

Ask Us Anything

We’d love to hear from you!