What we shipped

Connecting a workspace used to walk repositories one at a time. Discovery now fans out across them, so a workspace of a few hundred repositories finishes in minutes rather than most of an hour.

Nothing changes in how you connect a workspace - existing connections pick the new behaviour up on their next full sync.

The catalog is now the default landing page. It lists every service Beltic can see, who owns it, and which environments it is deployed to.

• Ownership is inherited from your identity provider groups
• Environments are detected automatically on first sync
• Filter by team, environment or health with a shareable URL

Audit events can now be exported continuously rather than downloaded after the fact.

• Webhook and S3 destinations
• At-least-once delivery with replay for the last 30 days
• Available on all plans, no add-on required

A group whose members were themselves groups resolved to an empty set, which left services owned by those groups showing as unowned. Nested groups are now flattened to their members during sync.

Everything the catalog shows is now available over HTTP, scoped to a workspace token you issue and revoke yourself.

• GET /v1/services with cursor pagination
• PATCH /v1/services/:id for ownership and metadata
• Webhooks for create, update and delete

Tokens are scoped per workspace and carry read or write separately, so a CI job that only needs to list services never holds a token that can change one.