Service / 07
Deploy.
Host.
Without the drama.
Senior DevOps freelance support. Safer deployments, hosting that's easier to manage, and infrastructure less mysterious than it needs to be.
Service / 07 / Capabilities
What's covered.
Deployments and CI/CD
GitHub Actions, build pipelines, release workflows, and the checks needed to ship changes without holding your breath.
Cloud hosting
AWS, GCP, Vercel, Cloudflare. I can work with what you already have or simplify it if the current setup is doing too much.
Containerization and migrations
Docker-based local/dev/prod consistency, server moves, provider changes, and controlled migrations that do not wreck uptime.
Operational cleanup
Backups, env handling, secrets, logs, alerts, and the missing runbook details that make incidents harder than they need to be.
10+ years senior delivery
Why me
Senior delivery you don't have to project-manage.
Infrastructure work is often ignored until it becomes a release blocker. I focus on the changes that reduce operational risk without adding needless complexity — and leave enough documentation that your team can run things without me afterwards.
- Deployments are manual or stressful
- Hosting setup is hard to reason about
- Environment drift keeps causing surprises
- Migration is overdue but the team is nervous about downtime
- App works, but the operational setup feels brittle
Engagement / Snapshot
A typical infrastructure & devops engagement.
Lead time
<7
Days to start, contract permitting
Length
4-12
Weeks for fixed-scope work
Reply
<24
Hours, every working day
Day rate
POA
Quoted per engagement
FAQ / Infrastructure & DevOps
Frequently asked
Q · 01
Can you work with an existing platform choice?
Yes. Most of the time the right answer is improving the current setup rather than replacing everything for the sake of it.
Q · 02
Do you handle migrations?
Yes. Server moves, provider changes, deployment changes, and gradual modernization work are all in scope.
Q · 03
Is this only for large teams?
No. Small teams often benefit most because they usually have less time for operational cleanup and less margin for deployment mistakes.
How I work
Remote-first. Async by default.
Inspired by Remote and the way Basecamp ran a distributed team without burning anyone out. Meetings are expensive, writing is cheap, and momentum belongs to whoever can make a decision without a calendar invite.
01 / Specs
Specs before code
A short written spec covering problem, scope, and acceptance before anything gets built. Cuts rework, makes review easier, and means we never argue about what was agreed.
02 / Workstreams
Workstreams over standups
Active work lives in tickets and PRs with running notes. Async updates instead of daily standups, so deep work is the default and meetings only happen when they earn it.
03 / Loom > Zoom
Loom over meetings
Most reviews and walkthroughs go out as a 5-minute Loom you can watch at 2× when convenient. We jump on Meet / Zoom / Teams when the topic actually needs a conversation.
Channels / Tools
Slack
Async, threaded, no expectation of instant reply
Loom
PR walkthroughs, demos, design reviews
Google Meet / Zoom / Teams
Booked when conversation > writing
Linear / Jira / GitHub
Source of truth for the work
Notion / Docs
Specs, decision records, retros
Related / Other services
More ways I work.
The pitch
I write the code, talk to your team, and ship what we agreed. No agencies. No PMs. No surprises.
James Donnelly
Freelance developer · Manchester