Miro Enterprise licensing is the licensing model of Miro’s Enterprise plan, sold through a signed Order Form under the Master Cloud Agreement. Under Section 2.2 of the MCA, Orders supply the service “for a specified number of Users and duration”.[12] Unlike the self-serve plans, where every member holds the same kind of seat, an Enterprise user holds one of several license types. The customer also chooses between two licensing models, the Flexible Licensing Program (FLP) and non-flexible licensing. These choices decide what happens when a new user starts editing boards.[2] Enterprise pricing is custom and starts from 30 members.[13] Catalog proof: Enterprise Orders specify a number of Users, who may include contractors.
Editions
The Enterprise plan offers multiple teams in one subscription, Flexible Licensing “after initial purchase without upfront commitments”, SSO and SCIM, domain control, audit logs, offline purchase with NDA, MCA and DPA, and offline invoicing for purchase orders.[14] Inside it, Miro sells two paid license types.
| License | Former name | What it includes | Licensing model |
|---|---|---|---|
| Accelerate | Advanced | Everything in Collaborate plus AI Workflows (Flows and Sidekicks), interactive AI prototypes, AWS Cost Calculator and CloudView, bi-directional ticketing in advanced tables, tree view, status workflows | Always a hard limit |
| Collaborate | Full, Standard | Core Miro features, Enterprise administration and security, AI credits, ticketing integrations, MCP (up to 10,000 calls per day), General Sidekick, Engage (up to 50 participants), basic prototyping, nesting in tables | FLP or non-FLP |
Source: Understanding Enterprise licenses.[1] Miro describes Accelerate as its “primary Enterprise license”. Collaborate “remains a supported legacy Enterprise license” with no forced migration or end-of-life planned.[1] The renaming did not change pricing, contract or renewal terms.[1] Since 2026-06-29, Miro Engage is included in all Enterprise license types and Miro Prototypes in Accelerate.[18] Catalog proof: Advanced renamed Accelerate; Full and Standard renamed Collaborate.
Add-ons sold on top of either license are Enterprise Guard, additional AI credits, additional Engage participants, unlimited MCP Server calls and services.[1] The add-ons page also lists AI Workflows as an Enterprise add-on, and Enterprise add-ons are bought through the account team.[16] Premium Support is purchased separately and identified in the Order.[17]
Beta features. New beta features carry a Collaborate or Accelerate designation. An Accelerate-designated beta feature can be used during the beta, “with the understanding that ongoing access after general availability will require an Accelerate license”.[1] Organisations on Collaborate should track which beta features their users adopt. Catalog proof: Accelerate-designated beta features need Accelerate after GA.
Metrics
Enterprise users have a license type and a separate Miro role (Company Admin, Team Admin, Member or Guest).[5]
| License type | Rights | Billed |
|---|---|---|
| Accelerate, Collaborate, Full (legacy) | View, comment, edit and create boards | Yes |
| Free (FLP only) | View and comment; upgraded automatically on editing or creating | No, until upgraded |
| Free Restricted | View and comment; can request an upgrade | No |
| Guest (Free or Free Restricted) | View and comment on shared boards; edit only if enabled | No |
Source: user access levels.[5] Admins on FLP plans can hold a Full (legacy), Collaborate, Free or Free Restricted license. On non-FLP plans they hold Free Restricted or Full (legacy)/Collaborate.[5] Visitors on public links need no license.[4]
Counting / floors
Named users, no pooling. “Our licensing model is designed around dedicated seats for specific, named users.” The regular or frequent recycling or pooling of licenses is not supported.[2] The MCA forbids letting individuals share User logon credentials.[12] Catalog proof: Enterprise licenses are named seats; recycling or pooling is not supported; Enterprise users may not share logon credentials.
One license per subscription. A user who belongs to several teams in one Enterprise subscription needs one license only. Teams in different subscriptions each need a license.[5] Catalog proof: One Enterprise license covers all teams in the subscription.
Who counts as a User. The MCA defines a User as an individual aged 16 or older whom the customer permits to use the service. This “may include Customer’s and its Affiliates’ employees, consultants, contractors or other third parties”.[12] Contractors working in the customer’s tenant therefore hold the customer’s licenses.
Accelerate is capped. “Accelerate licenses aren’t supported under the Flexible Licensing Program (FLP) and always operate on a non-FLP (hard limit) model.” Only the purchased number can be assigned. Organisations on FLP for Collaborate run a mixed model, with Collaborate flexible and Accelerate fixed.[2] Catalog proof: Accelerate licenses are always a hard limit.
Virtualization & partitioning
Not applicable; Enterprise licenses are per named user. The structural equivalent is teams and billing groups. One subscription can hold unlimited teams, for example separate teams for lines of business or external clients, and one license covers a user across them.[14][5]
Cloud / BYOL
Not applicable. The service is hosted by Miro, with regional data hosting in the EU, US, Australia and Japan on Enterprise. Existing customers pay migration fees to move out of EU residency.[13]
Programs
Flexible Licensing Program
Under the Flexible Licensing Program, available for Collaborate licenses, “your licenses scale as your usage grows”. Customers estimate their needs and add or remove licenses “without any upfront fees, retroactive costs or contract changes”.[3]
- No cap and auto-upgrade. FLP has no cap on Collaborate or Full (legacy) licenses and gives unlimited Free licenses to newcomers.[2] A Free user is upgraded automatically on creating a board, editing a shared board, being invited to edit, being granted co-ownership, or being added to a space as Editor.[3] Guests are never upgraded automatically. Catalog proof: FLP Free licenses upgrade automatically on board creation or editing.
- Default license for new users. New members get the company’s default license, Free or Free Restricted, whether invited by non-admins or captured by just-in-time provisioning, domain control or SCIM. The default is set by contacting Miro.[4] A default of Free lets usage grow without approvals. A default of Free Restricted sends upgrades through license requests.
- True-up. The subscription is reviewed “based on your defined true-up frequency”. The customer and its Miro account team decide how many new users need a Collaborate or Full (legacy) license, and “the contract will be amended with additional licenses and zero retroactive fees”.[3] Catalog proof: FLP true-up amends the contract with no retroactive fees.
- Reductions. “Twice a year you can reevaluate how many licenses you need for your organization.” Unneeded licenses can be removed without retroactive billing.[2] Company Admins can downgrade Collaborate or Full (legacy) users to Free Restricted at any time, singly or 50 at a time. Paid users cannot be downgraded to Free, which is only for new users.[4] Catalog proof: FLP license counts can be reduced twice a year.
The FLP model works as a true-up arrangement. Usage between true-ups is not charged retroactively, but auto-upgrades raise the license count used at the next review. Downgrading inactive editors to Free Restricted before the review is the documented way to keep that count down. See true-up for the general concept.
Non-flexible licensing
Non-flexible licensing “bills annually for a pre-set number of licenses. When those licenses are used, extra licenses must be purchased.”[2] When a non-FLP subscription runs out of paid licenses, all new users join on Free Restricted. Admins can buy more licenses or release some by removing members.[2] If several users are invited at once, they “receive licenses by order of their email addresses in the list of invitees”, and those at the end get Free Restricted.[6] Adding licenses does not upgrade existing Free Restricted users automatically.[6] Catalog proof: Non-FLP users join as Free Restricted when paid licenses run out; Bulk invitations receive licenses in list order.
License requests
A Free Restricted user who tries to create a board or project, requests edit access, is invited to edit, or is made board owner triggers a license request. The request goes to Company Admins or User Admins under the request-management settings. Requests expire after 30 days, and approval upgrades the user to a paid license.[7]
Billing groups and soft quotas
Billing groups let Company admins track consumption of Full (legacy), Collaborate and Accelerate licenses by internal budget, “simplifying process like license true-ups, renewals, and chargebacks”. Each user belongs to one group, and users without one fall into the default account group. Groups can be filled from SCIM cost-center attributes.[8] Soft quotas set a license limit per type and group, but “a billing group can exceed its soft quota”. They are indicators, not caps.[9] Catalog proof: Billing group soft quotas can be exceeded.
Reclaiming licenses
Deleting a user from a team “doesn’t release a license”. To remove a user from the organisation, an admin must first deactivate them and can then delete them.[11] A deactivated user no longer consumes a license: “Deactivated users aren’t billed. Their licenses are released and can be applied to another active user.” Content is retained for reactivation.[10] Enterprise also offers a SAM integration with Productiv. With an access token from the Enterprise admin console, the integration can download subscription usage and licenses allocated, and deactivate users based on usage.[15] Catalog proof: Removing a user from a team does not release the license; Deactivated Enterprise users release their license; Enterprise SAM integration can reclaim licenses.
Out of scope
- Enterprise list prices and discount levels, which are not published.
- The exact true-up frequency and default-license settings of a given customer, which are set in its Order or by Miro.
- Enterprise AI credit tiers: see Miro AI credits and MCP limits.
- Contract terms of the MCA beyond licensing: see Miro Terms of Service and Master Cloud Agreement.