Solutions

Ways to use Faros

Faros is one platform with different operating relationships. Use the hosted service, run the open-source control plane on infrastructure you choose, or work directly with the Faros team on adoption and deployment.

Talk to Faros Review self-hosting
  • One platform
  • Hosted or self-hosted
  • Apache 2.0 source
  • Direct adoption path

Operating models

Choose who operates the control plane.

The underlying platform model does not change. The meaningful choice is where it runs, who maintains it, and how closely you want to work with the Faros team.

Hosted

Faros Cloud

Use the hosted Faros control plane without deploying and maintaining the hub yourself. Public plan details are not published on this site yet.

  • Faros operates the control plane
  • Use the platform without a hub deployment
  • Contact Faros for current commercial details
Discuss the hosted service

Open source

Self-hosted Faros

Deploy the Apache 2.0 control plane on a Kubernetes cluster you operate, then choose ingress, authentication, storage, and provider configuration for your environment.

  • Your infrastructure and operating model
  • Helm-based deployment guidance
  • Source available for inspection and extension
Deploy a hub

Direct relationship

Work with Faros

Talk with the team behind the project about architecture, deployment, adoption, and operational requirements. Scope and terms are established directly.

  • Architecture and deployment discussions
  • Organizational requirements
  • A direct path to the Faros team
Start a conversation

Where it fits

Use the same primitives for different platform problems.

Faros is designed around shared resources, multiple actors, and boundaries that remain meaningful for both people and software agents.

Internal platforms

Give teams isolated workspaces

Publish selected provider APIs into each workspace, apply workspace-specific RBAC, and let teams operate resources without sharing one global namespace.

Review tenancy

AI-enabled development

Give agents governed tools

Expose enabled provider capabilities through a workspace-scoped MCP endpoint so agents use the same resource boundaries as human and automated API clients.

Review the MCP flow

Distributed infrastructure

Reach clusters and servers outbound

Connect Kubernetes clusters and Linux hosts with an agent that dials out, then carry kubectl, SSH, service, and MCP traffic through the existing tunnel.

Review connectivity options

Extensible platforms

Add a provider instead of changing the hub

Package an API, controllers, backend routes, portal UI, and MCP tools behind the same provider contract used by capabilities in the Faros repository.

Study the provider lifecycle

Evaluate Faros

Move from architecture to a working environment.

Start with the smallest path that answers your question, then go deeper into security, providers, or deployment.

Try

Run the quickstart

Install the CLI, log in to a hub, register an edge, start its agent, and use the resulting connection.

Follow the quickstart

Inspect

Review the security model

Understand organizations, workspaces, service accounts, OIDC, static tokens, and how requests remain scoped.

Read security and tenancy

Extend

Browse the provider catalog

See which capabilities ship today, the APIs they expose, and the portal and MCP surfaces they provide.

Open the catalog

Choose a path

Self-host from the docs or discuss the hosted path directly.

Faros does not publish commercial prices or service commitments on this site today. Contact the team for current hosted and organizational details.

Contact Faros Deploy it yourself