We build and improve the environments that run business applications. Our services cover cloud infrastructure, monitoring and release pipelines, from a specific repair to a new production setup.
Work with us on an existing application or an environment being prepared for launch. We agree the systems, changes and testing included in each assignment.
Set up application hosting, network access and managed resources. We also repair existing environments and bring changes made in a console back into maintained configuration.
Configure logs, metrics and traces around the behavior your team needs to investigate. For a recurring fault, we follow the affected request, worker or dependency to identify the change needed.
Develop or improve the pipeline that builds, tests and deploys your application. Where a release changes the database, we check compatibility during rollout and the limits of rollback.
You may already have developers responsible for the application. We work on the infrastructure and delivery changes around their code, with access and responsibilities agreed before work starts.
An assignment can cover one deployment problem or a wider environment change. We review the current setup, define the work and check the result in the environments included in the scope.
Discuss a projectThe scope names the repositories and environments involved, the expected changes and how those changes will be checked. Support hours and ongoing maintenance are agreed separately.
Configuration, deployment instructions and relevant checks stay with the agreed repositories. We explain the operating implications and any work that remains outside the assignment.
A new application version may need a different setting, resource or database structure. We include those dependencies in the deployment work and check what happens while old and new versions overlap.
Read about release compatibility
A report of a slow page is a starting point. We connect it to the relevant request, application release and dependency measurements so the team can investigate the affected part of the service.
How we investigate a servicePractical explanations of deployment compatibility, environment configuration and service performance.
Why 985 requests at 100 milliseconds can hide the experience of another fifteen.
A nullable field, a backfill and the point at which an older release stops being a rollback target.
Identify configuration, secret references and managed resources without copying protected values.
The entry point, web process, worker and database do not share the same lifetime.