Skip to main content

Overview

At the heart of Formal are two proxies: the Formal Connector, an easily deployed, cloud-native reverse proxy, and the Formal Endpoint, an egress proxy that intercepts and inspects TLS traffic on the host (macOS, Linux, and Windows). Organizations can use the Formal Connector to understand and control their data. The Connector is deployed as a container in your infrastructure. Formal’s architecture relies on two main parts: the Control Plane and the data plane (the Connector and Endpoint). The Control Plane cannot interact with your data; only the Connector and Endpoint can.

Minimal Architecture Diagram

At a minimum, Formal consists of a Connector deployed in your own infrastructure: The Connector needs to have network access to https://api.joinformal.com (the Control Plane), which is hosted in Formal’s infrastructure. This enables you to manage your Connectors via the API, Terraform provider, and the Control Plane (https://app.formal.ai). Alternatively, a Formal Endpoint runs on the host that originates the traffic, without a Connector: The Endpoint also needs network access to https://api.joinformal.com.

Satellites

The Data Discovery Satellite is also deployed in your infrastructure. Add it if you want Formal to catalog and classify your database schemas. Satellites also require direct network access to the Control Plane.

Within the Connector

The Formal Connector interprets network traffic, identifies the user, and evaluates policies against requests and responses. It can call Hooks to make policy decisions. The Connector also logs and records sessions that are viewable via the Control Plane. Formal Connector internals