We design cloud architecture, migrate existing systems and automate releases, working with AWS, Docker and Firebase. Security and performance are reviewed as part of the work. The aim is a release that nobody has to stay late for.
What we do
An engagement can combine several of these. The scope lists which ones are included.
- 01
Cloud migration
An existing application is moved to the cloud in stages, and each stage is checked before the next begins.
- 02
DevOps and release pipelines
Automated steps that build and deploy each release, so that nobody has to do it by hand.
- 03
Cloud architecture
The servers, databases and networks a system runs on, sized to the load it actually carries.
- 04
Serverless systems
Code that runs on demand, with no server of your own to keep running.
- 05
Cloud security
Access, permissions and stored data are reviewed as part of the work.
- 06
Performance optimisation
We measure where a system is slow, then work on those parts.
How the work runs
This is the short version. The full one is on the page about how we scope and quote a project.
- Step 01
Review
We review how the application runs today, including a set-up built by another team, so that we know what we are taking on.
- Step 02
Plan
The work is planned in stages, and the plan is agreed with you before anything is moved.
- Step 03
Move
Each stage is carried out and checked before the next one begins.
- Step 04
Run or hand over
We continue to run and monitor the infrastructure, or hand it over to your team with documentation.
After set-up
Who looks after the infrastructure is agreed for each project. There are two ways to do it.
- 01
We run it
We continue to run and monitor the infrastructure after it is set up.
- 02
Your team runs it
We hand the infrastructure over to your team, with documentation.
Running costs depend on traffic, storage and the services chosen. We size the architecture to the actual load, explain what drives the monthly bill and review it with you. We do not promise a fixed figure in advance.
Tools
We work with these three. The application on top can be one we built or one built by another team.
- 01
Cloud platforms
Where the application, its data and its files are hosted.
- AWS
- Firebase
- 02
Containers
Packaging that runs the software the same way on every machine.
- Docker
Questions
What cloud and DevOps work do you take on?
We handle cloud migration, cloud architecture, serverless set-ups, DevOps pipelines, cloud security and performance optimisation. We work with AWS, Docker and Firebase.
Can you move our existing application to the cloud?
Yes. We first review how the application runs today, then plan the move in stages so that each stage can be checked before the next one begins. The plan is agreed with you before anything is moved.
Do you only work on systems that you built?
No. We also work on infrastructure for applications built by other teams. We begin with a review of the current set-up so that we know what we are taking on.
How do you approach cloud costs?
Running costs depend on traffic, storage and the services chosen. We size the architecture to the actual load, explain what drives the monthly bill, and review it with you rather than promising a fixed figure in advance.
Who looks after the infrastructure after it is set up?
That is agreed for each project. We can continue to run and monitor it, or hand it over to your team with documentation.
Related services
CRM, ERP and internal systems for organisations that have outgrown their spreadsheets.
More on custom softwareOnline shops, portals and web applications for businesses that sell or serve online.
More on web development
Start here
Tell us what runs today and where it runs. A few lines are enough to begin.