How it works

People work in the dashboard, automation works through the API, and every change is checked against the same Mode and recorded the same way.

Step 1
Sign in
Sign in through Zitadel, the shared Fleetworks identity provider. Your Org role decides what you may do inside your Organization.
Step 2
Record applications
Create an Application, set its Quotas per Cluster and its Namespaces, and link its Pipelines.
Step 3
Track delivery
Pipeline runs, Deployments, Stages, Events and Commit statuses arrive through the API, from people or from CI with a Service account PAT.
Step 4
Define agents
Create an Agent with its Runtime, model, instructions and the MCP servers it may use, then Invoke it and read the Agent run.
Step 5
Compose processes
Put Agents and Approval gates into a Process, pick a Topology, and start a Process run. The Worker drives it step by step.
Step 6
Decide at the gate
When a Process run reaches an Approval gate it waits. Approve to resume it or reject to cancel it, from the dashboard or the mobile app.

See every deployment and every Agent run in one place