Plans and pricing
Solve your next challenge, automate your routine or bring your team together. Choose how Myrmex works with you.
Corporate policies or internal systems? Explore Enterprise.Explore Enterprise controlsMyrmex Business
Business brings together Pro features, shared workspaces and team controls. Start with one user and add operators as your operation grows.
$120 per user per month. Choose how many seats you need.
Add users as your operation grows. The price and pooled capacity scale with the number of users you subscribe to. Choose one option for your organization. Your team shares the allowance and the same data policy.
Start with 1 user. Monthly total = users × price per user.
The commitment not to use data for training is included in Business 10×.
1 × $120 = $120 per month. Capacity is combined in the team’s shared allowance.
Myrmex Enterprise
Attribute-based access policies, contractual audit requirements and integrations with internal systems. We size the agreement around your organization’s workspaces, teams and commitments.
Capacity, implementation and support scoped together.
Policies, workspaces and audit trail
SSO to sign in with corporate identity and ABAC policies to define who can act, in which workspace and under what conditions.
Centralized auditing, environment separation and retention requirements defined for your operation.
Organization-wide pooling, concurrency and continuity sized for your teams and automations.
Connect software developed within your company, based on available interfaces and permissions.
Licensing, capacity and usage policies are defined around procurement requirements. Allowances, usage windows, overages and evaluation terms follow the Gov proposal and contract; online plan rules do not apply automatically.
It brings together the assets, integrations and permissions for an operation. Production and Staging, for example, can be two contexts within the same organization.
Workspaces organize assets, integrations and permissions. The 1×, 3×, 5× and 10× multipliers describe monthly AI capacity, which is separate from a model’s context window.
Core: one individual workspace. Pro 3× and 5×: multiple individual workspaces. Business: shared workspaces, billed per user starting with one seat.
In every plan
Investigate, find vulnerabilities and execute authorized fixes from the first plan. Pro adds recurring automation and multiple workspaces; Business brings the team together.
With Pro 3× or 5×, create playbooks and runbooks, schedule executions and produce recurring reports. Automations follow the permissions and authorizations you define.
Included in Pro, Business and Enterprise.How usage works
Core includes 1×. Pro offers 3× and 5× with the same features. Business offers 5× or 10× per user, combined in the team allowance. Multipliers represent monthly capacity, not speed or a fixed task count.
Your plan defines the total capacity for the monthly cycle. It renews at the start of the next subscription cycle; session and weekly windows distribute that usage.
Starts with the first use. The session limit renews at the end of the window, provided weekly capacity and monthly allowance remain.
Regulates how much can be used during the week. Renewal releases the weekly limit without replenishing the monthly allowance already consumed.
The same usage counts toward the session, week and month. Balances do not add up. Renewing a shorter window does not replenish the monthly balance; new tasks need capacity under all three limits.
Wait for renewal or purchase additional capacity. Extra usage requires authorization and a defined spending limit.
Additional usage is sold at US$4 per million tokens. For purchases in BRL, the price is shown before purchase. Tokens are the technical unit of AI usage; task consumption varies with the data analyzed, model and execution steps.
Compare work scope, automation and organizational controls. Both Pro capacities include the same features.
Swipe the table to compare plans.
| Your requirement | Core | Pro 3× | Pro 5× | Business 5× | Business 10× | EnterpriseCustom quote |
|---|---|---|---|---|---|---|
| Capacity and scope | ||||||
| Capacity and scope | ||||||
| Monthly AI capacity | 1× individual | 3× individual | 5× individual | 5× per user, pooled | 10× per user, pooled | Sized pool |
| Subscription unit | 1 professional | 1 professional | 1 professional | Per user, starting at 1 | Per user, starting at 1 | Organization |
| Workspaces (contexts) | 1 workspace | Multiple workspaces | Multiple workspaces | Shared workspaces | Shared workspaces | Structure by operation and team |
| Allowance and usage windows | Monthly + session and week | Monthly + session and week | Monthly + session and week | Shared allowance and windows | Shared allowance and windows | As contracted |
| Work and automation | ||||||
| Work and automation | ||||||
| Agents and catalog connectors | Included | Included | Included | Included | Included | Included |
| Diagnostics, scanning and audits | On demand | On demand | On demand | On demand | On demand | As scoped |
| Authorized fixes and reports | Included | Included | Included | Included | Included | Under organizational policies |
| Playbooks, runbooks and scheduling | — | Included | Included | Included | Included | Included |
| Automatic reports and recurring routines | — | Included | Included | Included | Included | Included |
| Security and governance | ||||||
| Security and governance | ||||||
| Encryption, protected credentials and change authorization | Included | Included | Included | Included | Included | Included |
| Team roles and approvals between people | Individual use | Individual use | Individual use | RBAC and approvals | RBAC and approvals | Organizational policies |
| Standard SSO | — | — | — | Included | Included | Included |
| Attribute-based policies (ABAC) | — | — | — | — | — | Enterprise scope |
| Records and retention | Task history | Task history | Task history | Team history | Team history | Contractual audit and retention |
| Commitment not to use data for AI training | — | — | — | Not included | Included | Contractual |
| Integration and contracting | ||||||
| Integration and contracting | ||||||
| Integrations with customer-owned software | — | — | — | — | — | Scoped project |
| SLA and implementation support | — | — | — | — | — | Defined in the proposal |
| Multi-company / MSSP operations | — | — | — | — | — | Custom sizing |
Connectors depend on compatibility, credentials and permissions in your environment. Specific Enterprise deliverables and commitments are formalized in the proposal.
Core supports one professional investigating, auditing and executing on-demand fixes in one workspace. Pro adds recurring automation and multiple workspaces with 3× or 5× capacity. Business starts with one user and grows with your team, with pooled capacity, RBAC, approvals and standard SSO. Enterprise addresses specific organizational and contractual requirements.
Monthly AI capacity. Both include the same features: playbooks, runbooks, scheduling, automatic reports and multiple workspaces. Choose based on your workload.
It executes authorized actions on supported systems, including multistep procedures. You initiate the work and Myrmex respects the permissions granted. Creating and managing reusable routines, scheduling and automatic reports start with Pro.
It is a Myrmex workspace that groups assets, integrations and permissions. Production and Staging can be contexts within one organization. It is different from an AI model’s context window.
Yes. The monthly total is the selected Business option’s price multiplied by the number of users. Start with one user. Two Business 5× users contribute 10×; two Business 10× users contribute 20×. Capacity is pooled across the team.
They are proportions of monthly AI capacity, using Core as the baseline. Consumption depends on the data, model and steps involved. Multipliers do not represent a fixed number of tickets or audits and do not guarantee greater speed.
No. Session, weekly and monthly limits track the same consumption. A short window resetting does not replenish monthly capacity already used. New tasks need capacity within all three limits or authorized additional usage.
For new tasks, you can wait for the corresponding reset or purchase authorized additional usage with a spending cap. Enterprise capacity, concurrency and usage terms are sized in the contract.
Encryption, credential protection, permissions, change authorization and history are included in every plan. Business adds standard SSO, RBAC and approvals between people. Enterprise addresses ABAC policies and contractual audit, retention and support requirements.
This can be part of Enterprise: internally developed software, company portals and legacy applications. We assess interfaces, authentication and required actions. The original system remains customer-owned; rights to connectors and deliverables are defined in the contract.
A use case, the teams, workspaces and required controls are enough to start. From there, we size capacity, integrations, governance, implementation and support.
Both include the same team features, automation, RBAC, approvals and SSO. Business 5× adds 5× capacity per user. Business 10× adds 10× per user and includes the commitment not to use data to train AI models. The organization chooses one option, with a shared allowance and data policy for the team.
No. Gov is arranged through contact, with its own licensing, capacity and usage policies. Allowances, usage windows, additional consumption and evaluation terms are defined in the proposal and contract.
Bring your environment, policies and the systems that need to connect.
Plan with a specialist