Delivery, code health, database ops
Pipeline metrics, a reusable Terraform library and a browser shell, sitting next to the infrastructure they deploy to.
Delivery data lives in the CI tool, code health in another dashboard, and the infrastructure both of them ship to is somewhere else entirely.
CI/CD pipelines
Pipeline run history and delivery metrics.
Delivery data usually lives in the CI tool, separated from the infrastructure it deploys to. Pipeline run history and delivery metrics sit next to the cloud resources they change, so a deployment can be correlated with what happened afterwards.
- Pipeline run history
- Delivery metrics over time
- Alongside the infrastructure being deployed
Code quality
SonarQube metrics alongside your infrastructure view.
SonarQube metrics displayed alongside your infrastructure view, so code health is part of the same operational picture as cost and reliability rather than a dashboard only the dev team opens.
- SonarQube metrics in context
- Code health next to infrastructure health
- One place for engineering leadership to look
DevOps-in-the-Box
Reusable Terraform and script library with placeholder templating.
Most teams rewrite the same Terraform and shell scripts on every project. This is a reusable library of both, with placeholder templating so a module can be adapted to a new environment instead of copied and edited by hand.
- Reusable Terraform and script library
- Placeholder templating for new environments
- Stop rewriting the same infrastructure code
CloudShell
Browser terminal into your environment with multiple tabs.
A browser terminal into your environment with multiple tabs, for the moments when the fastest path is a command rather than a UI. No local credential setup needed to get a shell.
- Browser-based terminal
- Multiple concurrent tabs
- No local credential configuration
GitHub integration
Repository and token configuration for pipeline and code data.
Repository and token configuration that feeds the pipeline and code-quality views. Connect once and the delivery and code health data follows.
- Repository connection and token management
- Feeds pipeline and code quality data
- Configured once per repository
Managed database inventory, savings opportunities, query stats and health snapshots.
Managed databases get the same treatment as the rest of the estate: a full inventory, savings opportunities, query statistics and health snapshots. Routine database work stops depending on a specialist being available.
- Inventory of every managed database
- Savings opportunities per instance
- Query statistics and health snapshots
DevOps, answered.
Because a deployment and its consequences are usually investigated separately. Pipeline history, delivery metrics and SonarQube code quality sit next to the infrastructure being deployed, so a change can be correlated with what happened after it.
A reusable library of Terraform and scripts with placeholder templating, so a module can be adapted to a new environment instead of the same infrastructure code being rewritten on every project.
CloudShell provides a browser terminal into your environment with multiple tabs, with no local credential configuration required.
Managed database inventory, savings opportunities, query statistics and health snapshots across AWS, GCP and Azure.
DevOps is one module of 8.
Ready to automate devops?
30-minute walkthrough. We connect to a sandbox and show this module running against real infrastructure.