Accounts and access
Who can change production, and how a person is added or removed.
Cloud and DevOps
We set up and look after the cloud a startup actually runs: accounts, environments, deployments, and a written line around who can change production.
A startup often has an application that works on one laptop and a cloud account that several people can change. The work here is to make that path repeatable: a place to build, a place to test, and a production release that does not depend on one person’s memory.
Management means the running system stays inside the scope. Access, backups, monitoring, and the monthly cloud bill are part of that, when they are written down. An open-ended on-call promise is not.
We work with the platform you already use, or name one in the scope before anything is moved. You keep the accounts. We do not hold the only keys.
Included
Who can change production, and how a person is added or removed.
Development, staging, and production kept apart, with a reason for each.
A release path that can be repeated, instead of a manual upload from one machine.
The application, its data store, and the checks that say whether it is up.
A backup you can restore, and a view of the bill before it becomes a surprise.
Notes the team can follow, so the infrastructure is not trapped with us.
Project
What is running now, what must stay up, and what the startup can operate without a large platform team.
Environments, access, and the release path, written before accounts are rebuilt.
The cloud setup and deployments in the scope, checked with a release you can see.
Handover notes, and ongoing management only if the hours and the boundary are agreed.
Fit
Questions
The one already in the account, or one named in the scope before anything moves. You keep ownership of the account.
The service is shaped for startups that need production looked after without a full platform department. A larger organisation with its own platform team is usually a different job.
Yes. The scope says whether the website, the ecommerce application, and the cloud are one job or separate ones.
Related
Send a short note about the website, the store, the support load, or the cloud. You get a written scope before any build.