Pricing
Scale from a single laptop to large teams and clusters.
Starter
For individuals, students and faculty, open-source contributors and smaller organizations.
Limits
- 20 Agent credits a week
- 20 MCP client calls a week
- 2 GB storage, 30 days of history
- 50 GFLOP of physics simulation a week
Limits
- 20 Agent credits a week
- 20 MCP client calls a week
- 2 GB storage, 30 days of history
- 50 GFLOP of physics simulation a week
Limits
- 500 Agent credits a week
- 500 MCP client calls a week
- 10 GB storage, unlimited history
- 100 TFLOP of physics simulation a week
Limits
- 500 Agent credits a week
- 500 MCP client calls a week
- 10 GB storage, unlimited history
- 100 TFLOP of physics simulation a week
Custom limits, plus
- SSO, SAML and SCIM
- Audit and compliance controls
- Dedicated support
Custom limits, plus
- SSO, SAML and SCIM
- Audit and compliance controls
- Dedicated support
Frequently asked questions
01What's included in each plan?
| Starter | Professional | Enterprise |
|---|---|---|
| Who it's for | ||
| Individuals, students and faculty, open-source contributors and smaller organizations | Professional engineers and teams | Organizations with specific requirements |
| Runtime and language | ||
| Runtime and CLI, with 2,100+ math and physics functions | ||
| Cluster usage | ||
| Free Use grant | Up to 3 machines | Custom |
| Workspace | ||
| Desktop, browser sandbox and multiplayer | ||
| Multiplayer cloud | ||
| People | ||
| Up to 3 | Up to 5 | Unlimited |
| Storage | ||
| 2 GB | 10 GB | Custom |
| History | ||
| 30 days | Unlimited | Unlimited |
| Simulations | ||
| Included operations | ||
| 50 GFLOP/week | 100 TFLOP/week | Custom |
| AI | ||
| Agent credits a week, per person | ||
| 20 | 500 | Custom |
| MCP actions a week, per person | ||
| 20 | 500 | Custom |
| Enterprise | ||
| SSO, SAML and SCIM | ||
| — | — | |
| Audit and compliance controls | ||
| — | — | |
| Self-hosted multiplayer | ||
| — | — | |
| Scale to large data centers | ||
| — | — | |
| Support | ||
| Community | Dedicated | |
| Feature | Starter | Professional | Enterprise |
|---|---|---|---|
| Who it's for | Individuals, students and faculty, open-source contributors and smaller organizations | Professional engineers and teams | Organizations with specific requirements |
| Runtime and language | |||
| Runtime and CLI, with 2,100+ math and physics functions | |||
| Cluster usage | Free Use grant | Up to 3 machines | Custom |
| Workspace | |||
| Desktop, browser sandbox and multiplayer | |||
| Multiplayer cloud | |||
| People | Up to 3 | Up to 5 | Unlimited |
| Storage | 2 GB | 10 GB | Custom |
| History | 30 days | Unlimited | Unlimited |
| Simulations | |||
| Included operations | 50 GFLOP/week | 100 TFLOP/week | Custom |
| AI | |||
| Agent credits a week, per person | 20 | 500 | Custom |
| MCP actions a week, per person | 20 | 500 | Custom |
| Enterprise | |||
| SSO, SAML and SCIM | — | — | |
| Audit and compliance controls | — | — | |
| Self-hosted multiplayer | — | — | |
| Scale to large data centers | — | — | |
| Support | Community | Dedicated | |
02How much does additional usage cost?
Packs are shared across your organization and last 180 days.
03What is a FLOP of physics simulation?
A FLOP is one floating-point operation, such as one multiplication; a GFLOP is a billion of them and a TFLOP a trillion. Simulation usage counts the FLOPs in physics simulations that use RunMat's meshing and built-in physics solvers only. Ordinary MATLAB-language code is not counted, and neither is reusing meshes and results or waiting. The count is the same on any computer, CPU or GPU, so a faster computer doesn't use more. The Starter plan includes 50 GFLOP a week (0.05 TFLOP), about 2 to 4 bracket bending studies or similar thermal studies. Professional includes 100 TFLOP a week, about one complex battery pack study with multiphysics and a reasonably small mesh. Actual usage depends on the mesh and the physics. See how simulation usage is counted, and usage and limits.
04How do Agent credits and MCP actions work?
Agent credits pay for work you hand to RunMat Agent, and MCP actions count requests from Claude Code, Codex and other agents. Each of these allowances is per person and refills 7 days after you first use it. See usage and limits.
05Does RunMat automatically bill for overage?
No. You aren't charged for usage beyond your plan. Your weekly limits for simulation, Agent credits and MCP actions reset 7 days after you first use them, and the rest of RunMat keeps working until then. To get more sooner, a billing admin can buy a pack. TFLOP packs require Professional. Packs are shared across your organization and last 180 days.
06Is RunMat open source?
RunMat is licensed under the Business Source License 1.1, a source-available license, and each version converts to the Apache License 2.0 three years after it is first published. While a version is under the BSL, it's free for:
- Individuals, including freelancers
- Students and faculty at an academic institution, for teaching or research there
- Contributors to an open-source project, for work on that project
- Organizations with 250 or fewer people and US$10M or less in annual revenue
- Anyone, for non-production use
The source code is available on GitHub. See the full license grant details.
07When do I need a commercial license?
When your organization has more than 250 employees and contractors or more than $10M in annual revenue, and uses RunMat in its work. A Professional seat is a commercial license for one person, on up to three computers they can use together as a cluster. Larger clusters and other servers need Enterprise. Compiling RunMat into a program doesn't change who needs a license to use that program in production. Everyone else uses RunMat free:
- Individuals, including freelancers
- Students and faculty at an academic institution, for teaching or research there
- Contributors to an open-source project, for work on that project
- Organizations with 250 or fewer people and US$10M or less in annual revenue
- Anyone, for non-production use
08What does a Professional seat cover?
One named person, on up to three computers they use for their own work, and in automated builds and tests of their code. They register those computers with RunMat Server and can use them together as a cluster; RunMat Server refuses a fourth, and removing a computer frees its slot. Simulations on any of them use that person's simulation allowance. For more computers or larger clusters, Enterprise covers as many nodes as your contract states. Seats can't be shared.
09How does billing work?
Professional is billed monthly by card, per person. Adding someone charges a prorated amount right away, and removing someone lowers the bill from the next month. You can cancel at any time, and Professional runs until the end of the paid month. Enterprise is billed by invoice.
10Does RunMat train models on my data?
No. RunMat doesn't use your code, projects, prompts or results to train models.