Tools you can
build on.

Start from your terminal

$ fpl login
$ fpl doctor
$ fpl fab sites list
$ fpl mcp status

The FPL CLI brings account profiles, diagnostics and agent connections into your development workflow. Install the CLI, then sign in:

curl -fsSL https://fpl.dev/install.sh -o fpl-install.sh
sh fpl-install.sh
fpl --help
fpl login
fpl doctor

Download and inspect the installer before running it. Use fpl --help to see the commands in your installed version. Inspect your endpoint profiles with fpl profile list and fpl profile current.

Connect your agents

Use the CLI’s MCP tools to inspect your connection and discover setup options for your client:

fpl --help
fpl mcp status

For browser-approved enrollment and client configuration, inspect the login options in fpl --help. MCP connections use your enrolled identity and its permissions.

Git-backed delivery

Fab builds from your repository. Fab Sites publishes static sites; Shroud runs isolated application workloads. Inspect the tooling available in your installation:

fpl fab --help
fpl fab sites --help

Fab’s CLI provides site inspection and diagnostics alongside build runs, logs, deployment and release status. Check --help for the syntax shipped in your installation; enrollment and lifecycle command coverage are still being aligned across releases.

Profiles and runtime bindings

Select an endpoint profile for a child process rather than changing every tool’s configuration by hand:

fpl profile list
fpl profile current
fpl profile exec <profile> -- <command>
fpl --help

Binding execution obtains scoped runtime credentials for a child process. Infrastructure definitions retain opaque binding references—not the vendor secrets. Access still requires the relevant project permission and a working hosted credential service.

Define infrastructure

The FPL OpenTofu provider describes resources as code. Review the example and service requirements before applying; a resource definition alone does not establish hosted availability or permissions.

Provider distribution and public setup guides are still being consolidated. Ask for the supported configuration for your account →

Availability and access

Source implementation, installed CLI support and hosted availability are separate checks. The console does not yet expose every CLI workflow. Use your installed help and diagnostics to verify the supported path; do not treat a resource definition as proof that its production endpoint is ready.

Anonymous-access service guides are still being consolidated here. Until then, onboarding should provide your account’s endpoints, permissions and supported deployment instructions—not require you to infer them from internal infrastructure configuration.

Explore the open foundations

Decision Catalog Protocol ↗ · FPL source repositories ↗

Need help choosing a path? Start with your account and goals →