RunMat
  • Pricing
RunMat
GitHub
GitHub
Sign inTry in browser
DesktopRuntimePhysicsCADAdministrationAgent

Get RunMat updates

New releases, guides and examples.

Product+
  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download
Math+
  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting
Physics+
  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA
Industries+
  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance
Learn+
  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students
Compare+
  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons
Company+
  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms

Product

  • Runtime
  • GPU
  • Parallel
  • Compile
  • Interop and MEX
  • Simulation
  • MCAD
  • ECAD
  • Enterprise
  • AI integrations
  • Pricing
  • Download

Math

  • Signal processing
  • Linear algebra
  • Statistics
  • Curve fitting
  • Differential equations
  • Control systems
  • Optimization
  • Finance
  • Data and tables
  • Plotting

Physics

  • Simulation overview
  • Structural
  • Thermal
  • Electromagnetic
  • Joule heating
  • Thermal stress
  • Acoustics
  • Fluid flow
  • Conjugate heat transfer
  • Fluid–structure
  • What is FEA

Industries

  • Aerospace
  • Automotive and transportation
  • Defense
  • Electronics and semiconductors
  • Energy
  • Industrial machinery
  • Life sciences
  • Quantitative finance

Learn

  • Guides
  • Docs
  • Function reference
  • Language reference
  • Migration guide
  • Changelog
  • MATLAB Online
  • MATLAB AI agent
  • For students

Compare

  • RunMat vs MATLAB
  • RunMat vs Ansys
  • RunMat vs SOLIDWORKS
  • RunMat vs Altium
  • RunMat vs Cadence
  • RunMat vs COMSOL
  • RunMat vs Python
  • RunMat vs Julia
  • RunMat vs Physics AI
  • RunMat vs Octave
  • Benchmarks
  • MATLAB alternatives
  • All comparisons

Company

  • About
  • Blog
  • Contact
  • Source code↗
  • License
  • Privacy
  • Terms
GitHubXLinkedIn

© Dystr, Inc. · RunMat v0.7.1, Nov 17, 2026

RunMat® is a registered trademark of Dystr, Inc. MATLAB® is a registered trademark of The MathWorks, Inc. RunMat is not affiliated with, endorsed by, or sponsored by The MathWorks, Inc.

/
    • Overview
    • Architecture
Docs>Administration

Administration

These pages are for the people who deploy, run and govern RunMat for a team: platform, infrastructure, IT and security staff. For the overview an engineer or manager reads first, see RunMat for enterprises; for what RunMat collects, see Privacy. They cover where RunMat can run, what a deployment is made of, how people sign in and get access, and what crosses the network. Enterprise customers receive the full deployment guide, with installation, configuration, scaling, backups and monitoring, as part of their release kit.

RunMat has three parts:

  • RunMat Desktop, the app people work in, native on macOS, Windows and Linux and in the browser.
  • The runmat CLI and runtime, which run MATLAB-syntax code, simulations and CAD on the user's computer and, as a node agent, on compute nodes.
  • RunMat Server (runmat-server), which provides sign-in, organizations, shared projects and their history, live collaboration, the package registry, remote and cluster execution, and the agent's model gateway.

Code runs on the user's own computer unless they send it to a cluster. The server stores and coordinates; it does not run users' code.

Choose a deployment

DeploymentWho runs the serverData lives inIdentityNetworkPlan
RunMat CloudRunMatRunMat's cloudRunMat sign-in, or the organization's SSOInternetFree, Professional, Enterprise
Single-tenantRunMat, for one organizationA dedicated environment in a chosen regionThe organization's SSOInternet or private connectionEnterprise
Self-hostedThe customer, in its cloud account or data centerThe customer's PostgreSQL and object storeThe customer's identity providerThe customer's networkEnterprise
Air-gappedThe customer, on a network with no internet routeThe customer's infrastructureThe customer's identity providerNone outside the enclaveEnterprise

RunMat Cloud needs nothing installed beyond Desktop or a browser. Organization administrators manage members, roles, SSO, clusters and packages from organization administration. The pages on sign-in, roles and API keys and networking apply to them.

Single-tenant is RunMat Cloud run for one organization, in its own environment, with its own database and storage, connected to the organization's identity provider. Single-tenant hosting is available; contact us to ask about regions and setup.

Self-hosted puts RunMat Server and all project data in the customer's infrastructure. The customer runs the server container, PostgreSQL, an S3-compatible object store and, for collaboration or more than one instance, Redis. The Enterprise deployment guide covers installation with Docker Compose or Kubernetes.

Air-gapped is self-hosted with every outbound connection removed and releases imported through the site's transfer process. It supports ITAR-aligned private deployment. Enterprise Desktop builds that point at a self-hosted server are available for air-gapped installations.

What each deployment needs

Provided by the customerCloudSingle-tenantSelf-hostedAir-gapped
Desktop installs on workstationsYesYesYesYes
Firewall rules for workstationsOutbound HTTPSOutbound HTTPS or private linkInternalInternal
Identity provider for SSOOptionalYesYesYes
Server, PostgreSQL, object store, RedisNoNoYesYes
TLS certificates and load balancerNoNoYesYes
Backups, upgrades, monitoringNoNoYesYes
Compute nodes for clustersOptionalOptionalOptionalOptional
Model provider or gateway for the agentNoOptionalYes, or agent offInternal gateway, or agent off

Where to go next

TaskPage
Understand the componentsArchitecture
Connect SSO and SCIMSign-in, SSO and SCIM
Set roles and API keysRoles and API keys
Open the firewallNetworking
Plan a self-hosted or air-gapped deploymentContact us for the Enterprise deployment guide

Request the deployment guide

Organizations with an Enterprise license get the full deployment guide: installation with Docker Compose or Kubernetes, every server setting, scaling, air-gapped installs, backups, upgrades and monitoring. Request access with the name of your organization, and we'll send the guide to you once we've confirmed the license.

Report a suspected security vulnerability to security@runmat.com.

Licensing

RunMat is licensed under the Business Source License 1.1, and each version converts to Apache 2.0 three years after it is first published. It is free in production 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; and organizations with 250 or fewer people and US$10M or less in annual revenue. Organizations with more than 250 employees and contractors or more than $10M in annual revenue need a commercial license. Self-hosted and air-gapped deployments, single-tenant hosting, SSO, SCIM and clusters on your own servers are part of Enterprise contracts. See Pricing and the license, or contact RunMat about a deployment.

On this page
  • Choose a deployment
  • What each deployment needs
  • Where to go next
  • Request the deployment guide
  • Licensing