Matrix OS

Your workspace.
Your deployment choices.

Choose managed Matrix Cloud or evaluate the preview self-hosting path. Match the workspace, AI providers and connected services to your team’s requirements.

Managed Matrix Cloud

Matrix provisions an isolated cloud computer and operates platform services for authentication, routing, updates and recovery.

  • Hosted workspace regions include Falkenstein and Nuremberg in Germany, and Ashburn and Hillsboro in the US.
  • Starter uses an automatic region. Builder includes region selection; confirm your plan and available capacity.
  • Workspace files and a local Postgres database live on the Matrix computer; account and control-plane services operate separately.
Discuss a hosted pilot

Preview self-host

Install the browser shell, gateway and local Postgres on your own compatible Linux VPS. The runtime is open source under AGPL-3.0-or-later.

  • You operate DNS, TLS, access protection, patching, backups and upgrades.
  • Browser and CLI are the documented standalone paths. Managed Desktop/mobile pairing is not included in the preview guide.
  • Platform integrations are not configured by default. External AI providers may still process task data.
Read the preview install guide

A workspace region is one part of the data flow.

The hosted service is operated by Finna Labs Inc., a US company. Its privacy policy describes processing in the US, EEA and other countries. Selecting a German workspace does not establish EU-only processing across authentication, support, payments, analytics, integrations and AI providers.

The team has European roots; that is separate from the contracting entity and where each service processes data.

Choose the AI and review its terms.

Supported agents and model providers can receive prompts, files, code and tool results needed for a task. The route depends on the feature, provider, model and account you configure. Some routes use intermediaries such as OpenRouter.

Provider retention and training terms must be checked for the exact service and account. Matrix does not make a blanket zero-retention or no-training promise for all connected providers. Self-hosting the workspace does not establish fully local, offline or air-gapped inference.

Agree the operating requirements before live data.

  • Confirm the contracting entity, applicable data-processing agreement, subprocessors and transfer safeguards for your deployment.
  • Map workspace, account, AI and integration data flows, permissions and deletion requirements.
  • Validate required identity controls, roles, audit coverage and approval enforcement against the exact workflow. Do not assume enterprise SSO, complete RBAC or organization-wide governance from the landing page.
  • Define which actions require human approval and test that boundary with the selected agent and tools.
  • Agree support, recovery, retention and security requirements before a broader rollout.

Retention and deletion

The published privacy policy describes active workspace storage and residual backup, log and analytics retention of up to 12 months after deletion, subject to legal obligations or holds. Provider and connected-service retention may differ. Review the policy and agree any stricter requirements before a pilot.

Read the privacy policy and terms of service.