Fleetworks · Service catalog
The catalog of everything your org runs
One system of record for who owns a service, what it depends on and where it runs. Every row carries its own access rules, and every resource is reachable through a REST API.
Six core resources, and the links between them
A Team owns Services and Agents. A Service links to AWS and Azure accounts and depends on other Services. Labels classify all of them.
- 01
Service
One application or microservice, with ownership, contacts, links, cloud accounts and dependencies.
- 02
Agent
An agentic workload whose runtime Coastguard manages. Leaner than a Service, registered by Coastguard.
- 03
Team
The engineering team that owns Services and Agents, linked to cloud accounts and Labels.
- 04
AWS account
An AWS account by its account id, with onboarding and provisioning state.
- 05
Azure account
An Azure subscription by its subscription id, in the same onboarding role as an AWS account.
- 06
Label
A uniquely named tag on services, agents, teams and accounts.
What the catalog does
- 01
Six core resources
Services, Agents, Teams, AWS accounts, Azure accounts and Labels, each with full create, read, update and delete.
- 02
Access rules on every row
A chmod-style Mode on every catalog resource: view, edit and delete bits for the owner, the owner group and everyone else.
- 03
API keys
Machine principals with read or write scope for scripts, CI and other systems.
- 04
Signed webhooks
Outbound HTTPS notices of catalog changes, minimized and signed with HMAC-SHA256.
- 05
Connectors
Read-only views of a Service’s data from Coastguard and DNS, shown on its detail page.
- 06
Agent registration
Coastguard creates and updates an Agent’s catalog entry with one idempotent call, keyed by its Coastguard id.
Public rows are one request away
Reads are filtered by access rules: an anonymous caller sees only public rows, and a signed-in caller or API key also sees the rows it owns or its group can view. The OpenAPI document is served by the API at /openapi.json.
# public rows, no credentials
curl https://yp-api.fleetworks.dev/api/service
# with an API key (read scope)
curl -H "X-API-Key: yp_…" https://yp-api.fleetworks.dev/api/teamFrom empty catalog to a source of truth
- Step 1
Sign in
Sign in through Zitadel, the shared Fleetworks identity provider. Your auth role decides whether you may write at all.
- Step 2
Add teams and accounts
Create the Teams that own things and the AWS and Azure accounts they run in, and attach Labels to classify them.
- Step 3
Catalog services and agents
Add each Service with its owning Team, accounts and dependencies. Coastguard registers Agents itself through POST /api/agent/register.
Look up who owns it in seconds
Sign in with your Fleetworks account, or start with the public rows through the API.