Platform

The Faros platform

Faros gives developers, agents, and platform teams one resource model for building and operating systems. Its core primitives stay the same whether you use the hosted service or run the open-source control plane yourself.

Explore the architecture Follow the quickstart
  • Workspace isolation
  • Provider-based capabilities
  • Workspace-scoped MCP
  • Outbound edge connectivity

Core architecture

Four primitives carry the platform.

Faros keeps tenancy, capabilities, agent access, and remote connectivity separate enough to evolve independently while presenting them through one control plane.

01 · Isolation

Workspaces

Each workspace is a logical cluster with its own resources, APIs, RBAC, and quota. Credentials are issued for a workspace, so isolation is part of the address space rather than an application-side filter.

Understand workspaces

02 · Capabilities

Providers

Providers add APIs, controllers, backends, portal UI, and MCP tools through a shared contract. They ship and operate independently instead of growing one control-plane monolith.

Explore providers

03 · Agent interface

MCP

A workspace can expose one aggregate MCP endpoint for its enabled providers. Tool calls execute as the caller and inherit the same workspace scope and RBAC as API requests.

Use MCP

04 · Connectivity

Edges

An edge agent dials out from a Kubernetes cluster or Linux host and holds a reverse tunnel open. Kubectl, SSH, services, and MCP can use that established path without inbound firewall rules.

Connect an edge

One resource model

Different interfaces reach the same live resources.

The portal, command line, APIs, controllers, and MCP are interfaces over the platform—not separate inventories with separate policy.

For people

Portal and CLI

Developers can discover and operate resources through the portal or use kubectl-faros for workspace, edge, SSH, and MCP workflows.

  • Workspace-aware commands
  • Live provider surfaces
  • The same resources visible through APIs
Browse CLI commands

For automation

APIs and controllers

Providers publish Kubernetes-style APIs into tenant workspaces and reconcile resources across those workspaces through virtual workspaces.

  • APIExport and APIBinding
  • Provider-owned reconciliation
  • Workspace-scoped identity
Read the API model

For agents

MCP tools

Agents can use provider tools through one endpoint while staying inside the caller's workspace permissions. Narrow service accounts can reduce that scope further.

  • Federated provider tools
  • Caller-derived authorization
  • No separate gateway policy model
Build MCP tools

Provider catalog

Start with capabilities that already ship.

The repository includes providers for edge connectivity, application templates, code, hosted agents, App Studio, fleet query, Databricks resources, and a quickstart provider scaffold.

Build and run

Applications and code

Provision application templates as workspace resources, connect source repositories, and keep build and package state visible to the platform.

See application capabilities

AI workflows

Agents and App Studio

Run persistent hosted agents or use project workspaces that combine an assistant, a repository, and a live development environment.

See agent capabilities

Operate anywhere

Edges and fleet query

Reach Kubernetes clusters and Linux servers through outbound tunnels, then query objects and relationships across connected clusters.

See edge capabilities

Go deeper

See the platform as resources, requests, and reconciliation.

The concepts guide traces a complete request through Faros. The provider catalog shows the capabilities available in the repository today.

Read the concepts guide Browse the provider catalog