DevOps and cloud

DevOps consultant for servers, deployments and cloud costs

Slow deployments, a server nobody wants to touch, a hosting bill that keeps growing. I set up servers, automatic deployments and backups, move apps to better hosting, and cut cloud costs. I work with companies that have no developer of their own, and with teams whose developers would rather work on features.

I'm all in on AI, so the work goes fast. I stay careful with anything that could take your app offline or lose data.

I usually reply within one working day.

Vincent Schmalbach

What I take care of

Your servers, and the way your code gets onto them.

Server setup

Linux servers with Forge or Docker, on Hetzner, DigitalOcean or AWS, with updates, a firewall and SSL.

Automatic deployments

You push the code, the tests run, and the change goes live. A staging copy lets you check changes first.

Moving to better hosting

I move apps between hosts and clouds, with a way back if something goes wrong. The real estate website I rescued moved to Hetzner and Forge this way.

Lower cloud costs

Oversized servers, services nobody uses, a database on the wrong plan. I look at the bill and the load and cut what is not needed.

Several servers and queues

Queues, workers and caching spread across machines when one server is no longer enough. My outreach platform runs on more than 30 servers.

Backups and monitoring

Backups that have been tested by restoring them, monitoring for uptime and queues, and alerts that reach a person.

How I work

You don't need to have everything figured out before we talk. An idea, access to the repo, a screen recording or a list of problems is enough. I look at what is there, tell you what I would do and what it costs, and then I build it.

I use Claude Code, Codex and my own agent workflows for reading code, planning changes, writing tests, refactoring and debugging. It is not vibe coding. It is senior engineering with a much faster loop.

AI-first, with a way back

Claude Code and Codex write server configs and deployment scripts fast. I review every change, try it on staging first, and keep a way back before anything touches the live server.

I stay in control

AI writes a lot of my code. I still make every technical decision, read every change before it ships, and test it. Fast, but meticulous: the speed is only worth something if what goes live is right.

The way you want to work

Some clients want to look at every change before it goes live, others want me to deploy. Some want a weekly call, most prefer written updates. I work well asynchronously, and I still ask the important questions when they come up.

I think like an owner

I still run my own online products. So when I build or fix yours, I think about traffic, conversion, revenue and support as much as about the code, and I tell you when something is not worth building.

Examples of my work

Hosting and server work from client projects and my own.

Backend consolidation

From four figures a month to about $150

Two backends in PHP and Ruby on Rails merged into one Laravel app that replaced both. The monthly costs dropped to about $150.

Real estate website

Moved to Hetzner and Forge

The site moved from a poor host to Hetzner with Laravel Forge, with automatic deployments and a proper staging copy.

Outreach platform

More than 30 servers

A Laravel platform whose queues spread scraping and email work across more than 30 servers. It runs without anyone operating it by hand.

What clients say

"Vincent is reliable, technically skilled, and a valuable partner for keeping our site running optimally and moving forward."

Howard Rickard, Athena Advisers Ltd

"The end result was excellent and has been running smoothly since launch."

Philipp Toepelmann, Digital Investments GmbH

"He doesn't need micromanagement - he's fully capable of making decisions and driving the project forward, which has freed me up to focus on other parts of the business."

Aidas K., Bizdras OU

Questions

Hetzner, AWS or something else?

It depends on the app and on how much you want to manage yourself. For many apps Hetzner with Forge is cheaper and simpler. When you need managed services, AWS can fit better. I tell you which one I would pick.

Do we need Kubernetes?

For most apps, no. A few well-run servers with queues and caching carry a lot of load. I suggest Kubernetes only when the app needs it.

Can you move our app without downtime?

I copy everything to the new servers, test there, and switch over with a way back. How much downtime is left depends on the database, and I tell you before we start.

Can you work with our own developers?

Yes. I set things up so your team can deploy on its own, and I write down how it works.

Can you look at our cloud bill?

Yes. With the bill and some access, I can see where the money goes and what you can cut.

How do you charge?

Fixed price for a job with a clear outcome, a flat monthly rate for ongoing work, or hourly. Describe what you need and I'll suggest one.

Get a quote

Where your app runs today, how you deploy, and what bothers you most. A few sentences are enough. I'll reply with what I would do and what it would cost.

If you would rather talk first, book a 30-minute call or email contact@vincentschmalbach.com.

I usually reply within one working day.