Cloud and DevOps
Infrastructure set up once and properly. A push to the main branch runs the tests and deploys without downtime. Backups have been restored at least once. Alerts reach a person. The bill makes sense.
What you end up with
- Zero-downtime deploys from a tested main branch
- Backups you have seen restored
- Monitoring and alerts on the things customers feel
- Domains, DNS and email that land in the inbox
- A staging copy for trying risky changes safely
How we do it
Boring on purpose
Containers, one database, one cache. Simple systems are the ones a small team can keep running.
Roll back in one step
The previous release is kept ready, so a bad deploy is undone in a minute.
Email done right
SPF, DKIM and DMARC set up and checked, so receipts and invites are not marked as spam.
Questions about this
Can you move us off our current host?
Yes, with a rehearsal on a copy first and a planned cut-over.
Do you offer on-call support?
For products we maintain, yes. The hours are agreed in writing.
Tell us what you are making.
A few lines is enough. A person reads it and writes back with what it would take.