Lückdigital
Infrastructure

Servers and deploys you can follow, directly with the developer

Many projects do not fail on the feature. They fail on a Friday deploy. This is about a setup that runs, is documented, and does not leave you in a black box.

You work directly with me in Berlin-Lankwitz, not through rotating consultants. I set up VPS, Docker, Nginx, backups, and pipelines so you get access, short docs, and a setup I would run myself. Ongoing operations after that: DevOps consulting or Care.

Book a 15-minute intro call

No obligation. I review what is running and tell you which package fits.

Infrastructure packages

Infra audit + hardening

I look at what actually runs on the server: access, updates, backups, open ports. Then I harden the critical bits and write down what should come next.

  • Review of server, SSH, and permissions
  • Update and backup check
  • Hardening of the biggest gaps
  • Short report with prioritized next steps

Duration: 1–2 weeks

from €1,200

Guideline price. Final quote after a short briefing.

Book a 15-minute intro call

Automation setup

Build and deploy should be repeatable. Less manual copying, less "it worked on my machine". Staging and production stay separate.

  • CI/CD for build and deploy
  • Staging separate from production
  • Secrets and env vars in one place
  • Short runbooks for day-to-day ops
  • Handover so your team can keep deploying

Duration: 2–4 weeks

€2,500–5,000

Guideline price. Final quote after a short briefing.

Book a 15-minute intro call

Full infrastructure

From empty server to a running platform: containers, reverse proxy, backups, monitoring. Useful when you start fresh or want to replace tangled growth.

  • Server setup and basic hardening
  • Docker and networking
  • Backup including one restore test
  • Monitoring and sensible alerts
  • Docs plus a shared walkthrough

Duration: 4–8 weeks

from €6,000

Guideline price. Final quote after a short briefing.

Book a 15-minute intro call

How an infra job runs

First inventory: what is already running, where the risks are, what I am allowed to touch. Then a fixed scope with priorities. At the end, a walkthrough and notes, so you are not waiting on me for every restart.

What you bring as the client

Infra work stalls without access and a clear contact. From you I need:

  • Access to the server, panel, or cloud account with enough rights
  • A list of running services and domains, as far as you know them
  • Existing docs, runbooks, or deploy notes if you have any
  • SSH keys, where secrets live, and who else has admin rights
  • Maintenance windows and what is critical live (shop, mail, staging)
  • A contact who can decide on incidents and approvals
  • Feedback within the agreed windows, typically 3–5 business days

If access or info is missing, I wait or only work on what is cleared. Dates move accordingly.

Docs and handoff: how we work

  • After setup you get short notes: what lives where, how to deploy, what not to touch.
  • Where it helps, I write runbooks in plain language, not a 40-page PDF.
  • Secrets stay with you. I set up storage; I do not park passwords in chat.
  • We do a walkthrough at the end. You should be able to restart the stack without me.
  • Ongoing monitoring and on-call belong in Care, not in a one-off setup.

What is out of scope

Infra packages cover setup, hardening, and automation. Not included:

  • 24/7 on-call without a care contract
  • A cloud migration "just because" with no target picture or inventory
  • Managed Kubernetes when a VPS is enough
  • License costs for cloud, domains, certificates, or monitoring SaaS
  • Full app or frontend development (see the web packages)
  • Legal advice on hosting, DPAs, or data residency
  • Unlimited rework after acceptance without an hour budget

Anything beyond that we discuss in the briefing and quote separately.

Book an intro call

Web application development

Need a custom web app or client portal alongside your infrastructure?

Web app development in Berlin