Kozlowski IT 0162 8213267
Client Portal DE
Portrait of Pascal Kozlowski

IT Care · Servers · Network · Biberach district, Germany

Your IT runs. Even when something fails.

Care, servers and network for businesses in Biberach, Laupheim, Ochsenhausen, Riedlingen, Ulm and the surrounding area. With clean documentation, so that in an emergency you don't have to hope, but can show that you were prepared.

  • One point of contact who decides and stands behind it
  • Reply usually within one business day
  • Tested backups: recovery verified, not just claimed
Start with the security check

The first step

The security check: where do you really stand?

A complete small first step, not an open-ended consulting appointment.

I come to you and look at what you have, that is servers, network, access and backups, and check whether it holds up to what you assume. Without interfering with your running operations.

What you know afterwards:

  • Whether your backups hold in an emergency. I actually restore one of them, on your behalf, in an isolated environment. Verified, not claimed.
  • Which systems aren't backed up at all. That's more common than people think.
  • Where access is open that shouldn't be.
  • What should come first, what can wait, and roughly what it costs.

The scope is small and clearly defined. You get a fixed offer in advance, no open-ended invoice and no follow-up obligation. The written report is yours; you can also present it to another provider.

Request the security check

Services

Two things I take off your hands.

Ongoing IT care

I take care of what has to run every day: workstations, updates, access rights, backups. And I write down what I do.

That sounds obvious, but it's exactly where most businesses come unstuck. When, after an incident, the insurer asks when a backup was last restored, or a major client demands proof of your access control, you need more than a good feeling. You need a record.

With you, that runs automatically. Once a month you get an overview you can present: backup runs, patch status, open items.

Servers, network and virtualization

When the server is getting on in years, the network has grown historically, or the VMware bill suddenly looks different than before: that's my core area. I've done Linux and virtualization for over ten years. My own production environment runs on Proxmox, with over 35 virtual machines and around 40 containers that I set up and run myself. What I recommend to you, I run myself first.

Leaving VMware: regular support for vSphere 8 ends on 11 October 2027. Migrating to Proxmox takes one to two years for mid-sized environments, so if you want to act in 2027, you should do the math now. I'll tell you honestly whether the switch is worth it for you or whether you're better off staying. Check VMware cost →

A network that separates instead of just connecting: production, office and guests don't belong on the same network, and remote access needs to be secured. That's no longer optional, it's written into the terms of every cyber-insurance policy.

Where manual work is unnecessary, I automate it. Reports someone pulls together from three systems every month. Approvals that run by word of mouth. Records someone compiles by hand. For that I build you a small tool, not a big project, but the solution for exactly the one workflow that's costing you time. See examples as a live demo →

Monthly packages for ongoing care · Fixed prices for scoped projects · Documentation that stays with you

Who's behind this

Pascal Kozlowski

It all started with curiosity, with a server I wanted to understand rather than just use. The hobby turned into years of real practice, with stints at IT service providers and system houses and an own operation that has grown every year.

For over ten years I've worked with Linux, servers and virtualization, at first for myself, now as what I do for a living. I'm currently completing that path formally: IHK degree as IT specialist for systems integration, expected December 2026.

What interests me about this job is the part most people skip: that a system doesn't just run, but that someone can understand why it runs. That's why I document everything I touch, for you, and so that in an emergency someone else could take over.

You can reach me directly: Phone +49 162 8213267 · Email pk@kozlowski-it.de

More about me →

How working together works

  • You never explain your setup twice. What you have, how it fits together and what was last done to it is documented, not in one person's head. Whoever shows up at your place is up to speed before they start.
  • Everything runs in an orderly way, not on the fly. You book appointments online, the documentation of your setup is ready, and every request along with its solution is logged. Those exact logs are what you need when an insurer or auditor later wants to know what was done and when.
  • Appointments are deliberately limited. Whoever rushes from appointment to appointment makes mistakes, and mistakes on your IT are something you can't afford. Better a day later and done right.
  • If your business is at a standstill, call. For real emergencies the phone number applies, not the portal.

Who it's for

This fits you if…

  • …you don't have your own IT department and the boss, the office clerk or the boss's son takes care of it on the side.
  • …you're not sure whether your backup really works in an emergency.
  • …your server is older than the last extension and nobody knows what happens if it fails.
  • …your cyber-insurance demands proof you can't currently provide.
  • …your last provider is no longer reachable, or you wonder what you're actually paying them for.

Discuss your situation

See for yourself instead of reading promises

Running applications and documented reference builds.

Snapshot of the FlowGate application Live demos

Live demos

Test FlowGate and Quellwerk right in the browser. The credentials are on each page.

 Snapshot of a network architecture diagram Reference builds

Reference builds

Proxmox, network segmentation and SaaS architecture: documented so you can follow the technical decisions. Not a client project, but my own infrastructure.

When it needs to go deeper

IT infrastructure analysis: understand first, then commit to a plan.

For grown or unclear environments, when the security check shows more depth is needed.

For unclear or grown IT environments we start with an IT infrastructure analysis at a fixed price. You get an understandable overview, prioritized measures and a recommended path to implementation, as a solid basis for a concrete implementation scope, schedule and project offer.

  • A tightly bounded review scope and a price agreed in advance
  • Prioritized measures instead of a confusing list of defects
  • A basis for a solid implementation offer

In the free initial consultation we clarify whether an analysis is needed and which review scope makes sense.

Discuss an IT infrastructure analysis What the analysis covers →

Frequently asked questions

What does it cost?

Ongoing care is billed as a monthly package whose scope we agree in advance, for example one server and your workstations. For one-off, well-scoped projects you get a fixed-price offer with scope, price and process after the initial consultation. For unclear or grown environments we start with an IT infrastructure analysis at a price agreed in advance, before an implementation offer is made. Larger software undertakings are split into traceable phases where needed.

Am I locked into a contract?

Pure projects are one-off engagements with a firmly agreed scope. Ongoing care can be cancelled. I want to convince through reliable work, not through unnecessarily long contract terms.

What happens in an outage or data loss?

For acute issues you reach me directly by phone and I deal with it as a priority. For maintenance clients a fixed response time can be agreed to match the package. As a precaution, tested backups are in place: we verify restores before the emergency and document how they work.

You work alone, what happens if you're unavailable?

Fair question. I document systems and access so they're ready to hand over and someone else can take over in an emergency, instead of hoarding knowledge in my head. On top of that come the tested, off-site backups with verified recovery. So your operation doesn't depend on my presence, and you aren't made artificially dependent.

How do you handle data protection and GDPR?

A data processing agreement (DPA) is part of every engagement. On the infrastructure I run, data is held in German data centers; if you also use cloud services such as Microsoft 365, the storage location follows their terms. Backups are encrypted, access rights are strictly controlled. I work aligned with the German BSI baseline-protection methodology, which is a way of working, not a certification.

Do you see our data when maintaining our systems?

To maintain your IT I need access to systems, not to your content. I work on configuration, structure and scripts. Your actual data (database contents, documents, emails) stays on your systems. If a specific task genuinely requires real data, it only happens by arrangement, documented, and under the data processing agreement.

Will I understand what's being done?

Yes, that's part of the job. No jargon, everything documented in writing and explained so you can pass it on to your team.

Do you use AI for development?

Yes, as a tool for routine work. Architecture, security, review and responsibility stay with me. Your confidential content is not simply fed into public AI services.

Start without obligation

Let's talk through your situation briefly.

In a free initial consultation we work out what you need and which next step makes sense. Without sales pressure and without technical knowledge on your side.

  • About 30 minutes
  • Reply usually within one business day
  • A clear next step instead of sales pressure
More details (optional)

Provide at least an email or phone number. Your details go straight to me, with no intermediary services.

Prefer to talk directly? Phone +49 162 8213267 · Email pk@kozlowski-it.de