Formal

Name: Formal
Brand: Formal
Rating: 5 (1 reviews)

AI Native

Automate least privilege at the packet level

Est 2020|Valuation $1.8M|Raised $6.9M

LinkedIn 2K|Website|FTEs 45|HQ Paris, Île-de-France, FR

MarketsData Security Platforms

01Competitive Landscape

Narrative analysis

- Formal vs StrongDM: StrongDM is positioned as an infrastructure access platform with more public pricing information. Formal’s technical distinction is deeper protocol-native inline controls, though StrongDM benefits from broader market awareness and more public materials. - Formal vs Teleport: Teleport is widely used for SSH/Kubernetes access, identity, and audit. Formal overlaps on session-level audit concepts but emphasizes datastore and API controls at the query/response layer. - Formal vs Apono (JIT/ZSP): Apono focuses on eliminating standing privileges with just-in-time workflows. Formal emphasizes controlling and observing the session/query stream in-line, not just gating access.

Market share and adoption trends

No authoritative market share sources were identified in the accessible materials. The most concrete adoption signals available are press reporting of customer signings and early-stage funding, and a limited volume of public reviews, which may indicate early-stage adoption or limited participation in review platforms.

	Formal	StrongDM	Teleport
Starting Price	Not publicly posted (demo / sales-led)	Public materials provide some pricing examples; vendor-published figures exist	Example marketplace listing shows an example contract price (varies)
Primary Fit	Teams requiring inline, protocol-aware enforcement (mask/filter/rewrite) across datastores/APIs	Organizations seeking centralized, auditable access to infrastructure and databases via an access-broker model	Organizations standardizing on infrastructure identity for SSH/Kubernetes with strong audit and SSO workflows
Key Strength	Query-/protocol-level policy enforcement without application changes; VPC deployment model	Clearer pricing posture in some public materials and an established access-platform positioning	Recognized brand for infrastructure identity and audit; common fit for SSH/Kubernetes access and compliance
Key Weakness	Limited independent review volume; proxy insertion risk; pricing not publicly disclosed	Potentially higher cost at scale (per-user); may emphasize access brokering rather than deep query rewriting	May not natively offer the same depth of query-level masking across many database protocols

01Competitive Landscape

Narrative analysis

Formal vs StrongDM: StrongDM is positioned as an infrastructure access platform with more public pricing information. Formal’s technical distinction is deeper protocol-native inline controls, though StrongDM benefits from broader market awareness and more public materials.
Formal vs Teleport: Teleport is widely used for SSH/Kubernetes access, identity, and audit. Formal overlaps on session-level audit concepts but emphasizes datastore and API controls at the query/response layer.
Formal vs Apono (JIT/ZSP): Apono focuses on eliminating standing privileges with just-in-time workflows. Formal emphasizes controlling and observing the session/query stream in-line, not just gating access.

Market share and adoption trends

	Formal	StrongDM	Teleport
Starting Price	Not publicly posted (demo / sales-led)	Public materials provide some pricing examples; vendor-published figures exist	Example marketplace listing shows an example contract price (varies)
Primary Fit	Teams requiring inline, protocol-aware enforcement (mask/filter/rewrite) across datastores/APIs	Organizations seeking centralized, auditable access to infrastructure and databases via an access-broker model	Organizations standardizing on infrastructure identity for SSH/Kubernetes with strong audit and SSO workflows
Key Strength	Query-/protocol-level policy enforcement without application changes; VPC deployment model	Clearer pricing posture in some public materials and an established access-platform positioning	Recognized brand for infrastructure identity and audit; common fit for SSH/Kubernetes access and compliance
Key Weakness	Limited independent review volume; proxy insertion risk; pricing not publicly disclosed	Potentially higher cost at scale (per-user); may emphasize access brokering rather than deep query rewriting	May not natively offer the same depth of query-level masking across many database protocols