fleetworks / warden / solutions
Solutions
Three kinds of caller use the same API: the platform team that runs it, the service owners who self-serve, and the automation in between.
Platform and DevOps teams
Keep one governed record of every workspace and the service and cloud account behind it.
- See every workspace by service, with its VCS tenant, region and Terraform version
- Grant roles per organization and keep everyone else out by default
- Run the config Review to find risky settings before they matter
Service owners
Find and create the workspaces your service needs without filing a ticket.
- Only your organization’s services and accounts are offered
- A new workspace is checked against your service, AWS account and the tenant catalog
- Follow your workspaces from the mobile companion
CI and automation
Give pipelines exactly the access they need, and get told when things change.
- PATs with a scope list and an optional pin to one resource
- Signed webhooks for workspace.created and workspace.updated
- A Review of every token and endpoint, so stale or over-broad ones stand out