This is a good fit if
- Your application has outgrown a single server or basic hosting.
- Releases are manual and nervous, and you want them automated.
- You need a clear picture of what runs where, and what it costs to run.
What is included
- Architecture that matches the workload (see the cloud sketches in the Engineering Lab)
- Docker containers and Linux hosting
- Automated build and deployment
- Secrets kept out of code and repositories
- Logging, monitoring and alarms so problems are noticed early
What you receive
- An architecture diagram in plain language
- Infrastructure and deployment set up and documented
- A runbook for common tasks
- Notes on expected running costs and how to keep them down
Related work
We have not published a project for this service yet. If you would like to know how we would approach yours, ask and we will walk you through it.
Questions
- Do I actually need AWS?
- Not always. A static site or a small app can run happily on simpler hosting. We recommend AWS where it earns its place, and say so when it does not.
- Will I be locked in?
- We favour containers and open standards where it makes sense, which keeps moving between providers possible. Some managed services do tie you more closely, and we tell you which.
- Can you work with a team in another country or time zone?
- Yes. We are in Lagos, Nigeria (UTC+1, with no daylight saving) and work with clients worldwide. At the start we agree meeting times, a channel for quick questions and a written update rhythm, so progress does not depend on being online at the same hour.