DevOps and self-hosting
I run my own production platform: one Ubuntu server with nine apps in Docker containers, behind Nginx and Cloudflare, with MongoDB, Redis, single sign-on, monitoring and backups. I set up the same kind of thing for clients, or clean up the setup they already have on GCP or AWS.
Who this is for
- Small teams that want their apps on infrastructure they control, without a surprise bill each month.
- Startups that outgrew a quick deploy and now need staging, backups, monitoring and a repeatable release process.
- Anyone with a server nobody wants to touch, who needs it documented, secured and made boring again.
What I can do
Containerise and deploy your apps
Docker images for each app, a Docker Compose setup for the whole stack, and a deploy process you can repeat without SSH-ing in to fix things by hand.
Nginx, SSL and Cloudflare
Reverse proxy and SSL, plus Cloudflare caching rules that cache static assets at the edge while keeping APIs, dashboards and logins uncached.
Monitoring, logs and backups
Server and container health, capped log files so disks don't fill, and database backups you've actually tested restoring.
Security basics done properly
Private networks between containers, databases that are not exposed to the internet, rate limiting with Redis, security headers and secrets kept out of the code.
Cloud deployments
When a managed cloud makes more sense, I deploy to GCP or AWS and keep the setup simple enough for your team to own.
See it running
The self-hosted platform case study shows how my own setup works, and the home page shows the server's live status.
Schedule a DevOps & fleet quick chat or request an infrastructure audit.