Operations
Who should run the hub?
Self-host when you want to own the Kubernetes deployment and operational lifecycle. Discuss the hosted path when you want Faros to operate the control plane.
Plans
Faros plans and operating paths
Choose an operating path for the same Faros platform. The open-source project is available under Apache 2.0. Public pricing for the hosted and direct-support paths is not published on this site yet.
- No invented price tiers
- Apache 2.0 self-hosting
- Commercial details by contact
Current paths
Three ways to establish an operating relationship.
This page describes who operates Faros and where to go next. It does not imply prices, quotas, support levels, or service commitments that have not been published.
Open source
Self-hosted Faros
Use the Apache 2.0 project and operate the hub on infrastructure you control. You are responsible for the deployment, infrastructure, upgrades, and operational environment.
- No Faros software license fee
- Your infrastructure and operating costs remain
- Community and public documentation path
Hosted
Faros Cloud
Use a Faros-operated control plane instead of maintaining the hub yourself. Current availability and commercial details are provided directly by the Faros team.
- Faros operates the control plane
- Same platform model as the open-source project
- No public price or quota claims on this page
Direct
Work with Faros
Discuss architecture, deployment, adoption, and operational requirements directly. Scope, deliverables, support, and commercial terms are determined through that conversation.
- Architecture and deployment context
- Organization-specific requirements
- No predeclared service package
How to choose
Start with ownership, environment, and support needs.
The useful comparison is not a checklist of invented plan features. It is the operating responsibility your organization wants to keep or hand off.
Environment
Where should control and data live?
Review the hub, edge, provider, and authentication architecture against your infrastructure and data-location requirements before selecting a path.
Review the architectureRelationship
What help do you need?
Public documentation and community channels support independent evaluation. Organization-specific architecture and adoption questions belong in a direct conversation.
Discuss requirementsEvaluate before deciding
Use public evidence to answer the technical questions first.
The source, quickstart, deployment guides, and security documentation are available without committing to a commercial path.
Try
Run the quickstart
Exercise login, workspace selection, edge connectivity, kubectl or SSH, and MCP from the documented workflow.
Start the quickstartInspect
Read the source
Review the implementation and provider ecosystem in the public Faros repository.
Open GitHubAssess
Review security and tenancy
Understand the workspace, membership, role, service-account, and authentication model before choosing an operating path.
Read security docsCommercial details
Ask for the current hosted and organizational options.
Faros has not published price points, packaged support levels, usage quotas, or service-level commitments on this site. Contact the team for current information.