Secure. Reliable. Fully managed.
Cloud, hosting and security
Frontend and backend deployment, CI/CD pipelines, VPS and cloud servers, set up so releases are routine and recovery is a procedure rather than a scramble.
What this covers
Four things, in the order they matter on the day something breaks.
Frontend deployment
Preview on every branch, a CDN in front, TLS that renews itself.
Next.js and React front ends on Vercel, Netlify or Cloudflare, with a preview deployment on every branch, a CDN in front, automatic TLS and domains configured properly. Static and server-rendered routes are deployed as what they are, so pages are cached where they can be and fresh where they have to be.
Backend and database hosting
Docker behind Nginx, managed data, secrets out of the repository.
Node and Express APIs containerised with Docker and run on AWS, Google Cloud or a VPS, behind Nginx as a reverse proxy. MongoDB Atlas or managed PostgreSQL for data, Redis where a cache or a queue is needed, object storage for uploads, and secrets kept in the environment rather than in the repository.
CI/CD pipelines
Build, check and deploy on merge. Rollback is a command.
GitHub Actions running the build, the type check and the tests on every push, and deploying on merge. A release stops being an event somebody has to remember the order of, and a rollback becomes a command rather than a recovery effort.
VPS, security and recovery
Hardened Linux, tested restores, alerts before your customers call.
Provisioning and hardening Linux servers on DigitalOcean, Hetzner, Contabo or AWS EC2: firewall, SSH keys, non-root users, unattended security updates, Nginx, PM2 or Docker for process management, TLS certificates that renew themselves, nightly backups with a restore that has been tested, and uptime monitoring that reaches us before it reaches your customers.
Built with
- Vercel
- AWS
- Docker
- GitHub Actions
- Nginx
- Linux
- Cloudflare
- MongoDB
How a project runs
- 01Discover
- 02Define
- 03Design
- 04Develop
- 05Validate
- 06Deploy
- 07Evolve
Questions
A VPS or managed cloud?
A VPS is cheaper and entirely predictable, and suits a single application with steady traffic. Managed cloud services cost more and earn it when traffic is spiky or the system has many moving parts. We will say which one a project is rather than defaulting to the larger bill.
Can you take over hosting we already have?
Usually, yes. Migrating an existing site, API or database onto a server we set up is normal work, and so is taking over infrastructure somebody else built and documenting what is actually running on it.
What happens after launch?
We stay on it. Deployment, backups, monitoring and security are part of what we build, and the last stage of our process is Evolve: maintaining, improving and scaling the system as the business moves.