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
runmatCLI 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
| Deployment | Who runs the server | Data lives in | Identity | Network | Plan |
|---|---|---|---|---|---|
| RunMat Cloud | RunMat | RunMat's cloud | RunMat sign-in, or the organization's SSO | Internet | Free, Professional, Enterprise |
| Single-tenant | RunMat, for one organization | A dedicated environment in a chosen region | The organization's SSO | Internet or private connection | Enterprise |
| Self-hosted | The customer, in its cloud account or data center | The customer's PostgreSQL and object store | The customer's identity provider | The customer's network | Enterprise |
| Air-gapped | The customer, on a network with no internet route | The customer's infrastructure | The customer's identity provider | None outside the enclave | Enterprise |
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 customer | Cloud | Single-tenant | Self-hosted | Air-gapped |
|---|---|---|---|---|
| Desktop installs on workstations | Yes | Yes | Yes | Yes |
| Firewall rules for workstations | Outbound HTTPS | Outbound HTTPS or private link | Internal | Internal |
| Identity provider for SSO | Optional | Yes | Yes | Yes |
| Server, PostgreSQL, object store, Redis | No | No | Yes | Yes |
| TLS certificates and load balancer | No | No | Yes | Yes |
| Backups, upgrades, monitoring | No | No | Yes | Yes |
| Compute nodes for clusters | Optional | Optional | Optional | Optional |
| Model provider or gateway for the agent | No | Optional | Yes, or agent off | Internal gateway, or agent off |
Where to go next
| Task | Page |
|---|---|
| Understand the components | Architecture |
| Connect SSO and SCIM | Sign-in, SSO and SCIM |
| Set roles and API keys | Roles and API keys |
| Open the firewall | Networking |
| Plan a self-hosted or air-gapped deployment | Contact 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.