Faros

Name: Faros
Brand: Faros

The system for running engineering with AI

Est 2019|Valuation $299M|Raised $64.8M|4 Ref Customers

LinkedIn 2K|Web traffic 36K|FTEs 58|HQ San Francisco Bay Area, Ca, California, US

MarketsEngineering Analytics

01Competitive Landscape

Narrative analysis

- Faros vs LinearB: Both address AI productivity measurement and engineering insights. LinearB emphasizes workflow automation and has a transparent pricing entry point. Faros emphasizes a central SDLC data layer with broader integration and enterprise deployment flexibility. - Faros vs Jellyfish: Jellyfish focuses on allocations, capacity, and executive/finance alignment, while Faros is oriented around cross-domain SDLC data correlation and analytics, including measurement of AI tool impact. - Faros vs Pluralsight Flow: Pluralsight Flow provides established workflow metrics and transparent pricing; Faros may be preferable when custom connectors, cross-domain correlation, and explicit AI-measurement workflows are required.

Adoption / market traction indicators

Funding and press coverage indicate the company has reached Series A scale.
Partner announcements and marketplace listings indicate ecosystem engagement; marketplace presence supports certain procurement paths but does not by itself indicate broad market penetration.

	Faros	LinearB	Jellyfish
Public starting price	Public materials reference a public starting point per contributor (sales-led)	Public starting point per contributor (Essentials tier)	Quote-based (modules + seats)
Best for	Organizations seeking an integrated SDLC data platform with customizable analytics and AI impact measurement	Teams that prioritize workflow automation and process control	Leadership teams requiring allocation, capacity, and finance-aligned engineering metrics
Key strength	Broad SDLC data unification and customizable analytics; enterprise deployment options	Workflow automation and policy-based controls; clear public pricing entry point	Executive and finance alignment features; modular approach for engineering management
Key weakness	Requires configuration and data modeling; limited public pricing transparency	Credits model and automation focus may be unnecessary for analytics-only needs	Pricing and module complexity; change management requirements

01Competitive Landscape

Narrative analysis

Faros vs LinearB: Both address AI productivity measurement and engineering insights. LinearB emphasizes workflow automation and has a transparent pricing entry point. Faros emphasizes a central SDLC data layer with broader integration and enterprise deployment flexibility.
Faros vs Jellyfish: Jellyfish focuses on allocations, capacity, and executive/finance alignment, while Faros is oriented around cross-domain SDLC data correlation and analytics, including measurement of AI tool impact.
Faros vs Pluralsight Flow: Pluralsight Flow provides established workflow metrics and transparent pricing; Faros may be preferable when custom connectors, cross-domain correlation, and explicit AI-measurement workflows are required.

Adoption / market traction indicators

Funding and press coverage indicate the company has reached Series A scale.
Partner announcements and marketplace listings indicate ecosystem engagement; marketplace presence supports certain procurement paths but does not by itself indicate broad market penetration.

	Faros	LinearB	Jellyfish
Public starting price	Public materials reference a public starting point per contributor (sales-led)	Public starting point per contributor (Essentials tier)	Quote-based (modules + seats)
Best for	Organizations seeking an integrated SDLC data platform with customizable analytics and AI impact measurement	Teams that prioritize workflow automation and process control	Leadership teams requiring allocation, capacity, and finance-aligned engineering metrics
Key strength	Broad SDLC data unification and customizable analytics; enterprise deployment options	Workflow automation and policy-based controls; clear public pricing entry point	Executive and finance alignment features; modular approach for engineering management
Key weakness	Requires configuration and data modeling; limited public pricing transparency	Credits model and automation focus may be unnecessary for analytics-only needs	Pricing and module complexity; change management requirements