Cloud and DevOps, so releases become routine.
We set up the infrastructure and delivery pipelines behind your software on AWS, Azure or Google Cloud, all defined in code, so environments can be rebuilt from scratch and releasing a change is safe, quick and uneventful.
What we build
The foundations your software runs on, and the pipelines that get changes to your users.
-
Cloud foundations
Accounts, networks, identity and access set up properly from the start, with separate environments for development, testing and production.
-
Infrastructure as code
Every server, database, network and permission defined in code with Terraform, AWS CDK or Pulumi, and servers configured with Ansible, all reviewed like code and rebuildable at any time.
-
Delivery pipelines
Pipelines that build, test, scan and release your software on every change, with approvals where you want them.
-
Containers and Kubernetes
Applications packaged in containers and run on managed Kubernetes or simpler container services, whichever fits.
-
Moving to the cloud
Applications and data moved from your own servers or another provider, step by step, with a plan to switch over and a way back.
-
Cost and performance tuning
Right-sized resources, scaling that follows demand, and clear cost reporting, so you pay for what you use.
-
Backups and recovery
Automated backups, tested restores and a written recovery plan, so an outage is an inconvenience rather than a crisis.
-
Observability
Logs, metrics and alerts across your applications and infrastructure, so problems are visible and can be traced.
What goes into every environment we set up
Behind this work
Our managing director, Johnson Nuviadenu, is an AWS Certified DevOps Engineer and Solutions Architect at Professional level.
-
Reproducible
Environments rebuilt from code, not from memory, so nothing depends on one person.
-
Least access
People and services get only the permissions they need, reviewed and recorded.
-
Secure pipelines
Code, dependency and container scanning on every release, and secrets kept out of the code.
-
Safe releases
Small, frequent changes with automated checks and a quick way back if something goes wrong.
-
Documented
Diagrams, runbooks and written decisions, so your team understands what we built and why.
-
Cost you can see
Tags and reports that show what each part of your system costs to run.
Technology we use
We'll suggest the simplest set of tools that does the job, and that your own team can live with after we're done.
Cloud
- AWS
- Azure
- Google Cloud
Infrastructure
- Terraform
- AWS CDK
- Pulumi
- Ansible
Containers
- Kubernetes
- Docker
- Managed container services
Pipelines
- GitHub Actions
- Bitbucket Pipelines
- Argo CD
- GitLab CI/CD
- Azure DevOps
What you get
Everything your team needs to run it, change it and understand it.
- Environments defined in code, with Terraform, AWS CDK or Pulumi
- Delivery pipelines for each application
- Monitoring, logs and alerts
- Backups and a written recovery plan
- Access set up by role, with a record of who has what
- Architecture diagrams and runbooks
How a project runs
Nothing starts without your sign-off, and you'll see working software every two weeks.
- 1
A free call
Thirty minutes to talk through what you need. If we're not the right fit, we'll say so.
- 2
Discovery
A few short workshops to agree goals, users, constraints and what success looks like.
- 3
Design
Screens you can click through and test with real users before we write any code.
- 4
Build
Two-week sprints. Each one ends with a demo of working software you can try and comment on.
- 5
Launch
Automated tests, security checks and a go-live plan with a way back if something goes wrong.
- 6
Looking after it
Your system moves onto a Managed Services retainer, supported by the people who built it.
What happens after launch?
You can keep us on to look after it. The people who wrote the code are the ones who keep it running, so nothing gets lost in a handover.
Common questions
- Which cloud should we use?
- Usually the one your organization already uses. If you are starting fresh, we compare AWS, Azure and Google Cloud against your needs and recommend one, with our reasons.
- Can you improve the setup we already have?
- Yes. We start with a short review of your accounts, pipelines and costs, then fix the biggest risks first.
- How do you charge?
- Build work is billed by the hour against an estimate we agree before we start, and you see hours and progress every sprint. Looking after a live system is a monthly or yearly retainer.
- Where do we start?
- With a free 30-minute call. If we're not the right fit, we'll tell you. If we are, we agree goals and an estimate before any work begins.
Tell us what you're working on
The first call is free and there's no sales pitch. We reply within 24 hours.