Cloud & DevOps
Containerised deployment, CI/CD, monitoring and backups: the part that decides whether software is still running six months after launch.
Deployment is where most of the risk actually sits. A system that works on a laptop and cannot be rebuilt from source is a system with one point of failure: whoever set it up.
Reproducible by default
Everything runs in containers, defined in files that live in the repository. A new server is brought up by running the same commands as the old one, not by remembering what was installed.
The unglamorous parts
Log rotation, real client IPs behind a proxy, health checks, restore-tested backups and TLS that renews itself. These are the things that quietly break production, and they are checked rather than assumed.
/What this includes
Containerisation
Docker images that build the same way on any machine, running as an unprivileged user with no secrets baked in.
CI/CD pipelines
Lint, type check and tests on every push, and a deploy that is one command rather than a checklist.
Monitoring and logs
Structured logs with request ids, health endpoints and rotation, so a disk never fills up with its own history.
Backup and recovery
Scheduled dumps with a retention window, and a restore actually performed into a scratch database rather than assumed to work.
/Technologies
- Languages
- TypeScript
- Python
- SQL
- JavaScript
- Dart
- Backend
- NestJS
- FastAPI
- Prisma
- SQLAlchemy
- Alembic
- Celery
- Frontend
- Next.js
- React
- Astro
- Tailwind CSS
- Flutter
- Data and analytics
- Microsoft Fabric
- PySpark
- Power BI
- PostgreSQL
- InfluxDB
- Redis
- Infrastructure
- Docker
- nginx
- Caddy
- Cloudflare
- GitHub Actions
- Linux
/Related work
Newspaper portal, from empty database to daily use
A regional newspaper needed a publishing platform its own editors could run. Client project, live since August 2026 and now operated entirely by their team.
A subscription billing pipeline that survives failure
An uptime monitoring product built around the part most teams get wrong: Stripe subscriptions, webhooks and the states in between. Our own product, built to be shown rather than described.
/Questions
Questions we get asked
Do you work with our existing cloud account?
Yes. Infrastructure is defined in files in your repository, so it stays yours and can be rebuilt without us. We do not hold the only copy of anything.
Are backups actually tested?
A backup nobody has restored is a hope, not a backup. Restores are performed into a scratch database and the row counts are compared before the arrangement is called done.
Have a project in mind?
Tell us what you are building and we will tell you honestly whether we are the right fit.
Contact us