04Linux · Proxmox · Cloudflare
InfrastructureThe layer nobody sees until it breaks — server, dns & infrastructure management.
Before & after.
Linux servers, virtualization, DNS and deploy pipelines. I set them up properly, watch them, and keep them running.
Illustration · keep scrolling, or drag to compare
(Δ) The differenceIllustrative: the kind of change I aim for
- Uptime
- 97.10%99.99%
- Deploy time
- 45.0min0.2min
- Manual steps
- 120
- Expired certificates
- 30
Before — Held together
- One server nobody understands
- Manual, nerve-racking deploys
- Expiring certificates and DNS guesswork
- Problems found by customers
After — Set up properly
- Documented, organised servers
- Push to deploy, every time
- DNS and SSL managed
- Monitored, with alerts first
What's included.
- 01
Linux servers
Setup, hardening, updates and tuning for web apps, databases and services.
- 02
Virtualization
Proxmox and vSphere hosts with virtual machines and containers organised and backed up.
- 03
DNS & routing
Domains, records, email authentication and routing configured correctly.
- 04
SSL & security
Certificates that renew themselves, firewalls and sensible access controls.
- 05
Deploy pipelines
Push code and it builds, tests and deploys automatically, with easy rollbacks.
- 06
Monitoring & health
Uptime checks, server health and alerts so issues are caught before users notice.
- 07
Backups
Scheduled backups you can actually restore from, tested.
- 08
Edge hosting
Cloudflare for caching, DNS and Workers where it makes sense.
How it runs.
Step 01
Audit
What's running, where, and what's fragile, often written down for the first time.
Step 02
Plan
What to fix first, what to move and what to automate.
Step 03
Rebuild
Servers, DNS and pipelines set up cleanly, with no downtime surprises.
Step 04
Run
Monitoring, updates and on-call fixes, so it keeps working.
The proof.
Good questions.
Yes. I'll start by documenting what's running and how, fix anything urgent, and then tidy up and automate the rest.
Either. I work with Linux on bare metal, Proxmox and vSphere virtualization, and cloud platforms like Cloudflare.
Yes. Pushing code can build, test and deploy your site or app automatically, with a simple way to roll back.
Yes. Domains, DNS records, SSL certificates and email authentication like SPF, DKIM and DMARC.
Both are part of a proper setup: scheduled, tested backups and uptime and health monitoring with alerts.
I stick around. Fixes, small changes, new features and the servers underneath. Most of my work doesn't end at launch, and I'd rather keep looking after something I built than hand it off and disappear.
Send a short note through the contact form or email me@dylanlambertson.dev with what you have in mind. I'll reply myself, ask a few questions, and come back with a plan, a timeline and a price before any work starts.
Also on offer
Contact
Let's build something.
New project, an idea you're weighing up, or a role you're hiring for. Send a note and I'll reply myself.