IT infrastructure · Cybersecurity · Automation

Calm systems.

Sanly Tech plans, builds and secures IT infrastructure for businesses – and automates whatever repeats. Structured, documented and with one contact who actually runs the systems.

Get in touch View services
Diagram of a secured IT environment Requests from the internet pass a firewall at the perimeter and reach three servers via the core switch; unwanted requests are rejected at the firewall. Over a separate management network, a CI/CD pipeline distributes deployments, monitoring collects metrics, and backups are additionally stored off-site (3-2-1). perimeter ops 10.0.0.0/16 internet core srv-01 srv-02 srv-03 backup offsite 3-2-1 fw-01 ci/cd monitor
Legend
Location
Düsseldorf, Germany · remote and on-site
Contact
One person – from concept to operations
Approach
Standardised, documented, traceable
Response
Usually within the same business day

01Services

Three areas, one contact.

The areas interlock: an environment is only as secure as it is cleanly built – and only as stable as its processes are reproducible.

01 infrastructure

IT Infrastructure

Servers, networks, virtualisation and cloud – planned, built and operated. On-premise, in the cloud or hybrid, with monitoring and tested backups.

  • Linux & virtualisation
  • Containers (Docker)
  • Networking, VPN, DNS
  • Monitoring & alerting
  • 3-2-1 backups
02 security

Cybersecurity

Know your attack surface and shrink it: audits, system hardening, access concepts, vulnerability assessments and incident plans that hold up when it matters.

  • Security assessments
  • Hardening & patching
  • MFA & least privilege
  • SPF · DKIM · DMARC
  • Incident plans
03 automation

Automation

Replace recurring operations and admin work with scripts, pipelines and infrastructure as code – less manual work, fewer errors.

  • Bash & Python
  • Infrastructure as code
  • CI/CD pipelines
  • REST APIs & webhooks
  • Automated reports

02Starting points

Where I typically come in.

Projects rarely start from scratch. There is usually a concrete trigger – such as one of these.

  1. 01

    The environment has grown over the years – there is no up-to-date documentation.

    Assessment, network and system documentation

  2. 02

    Backups are running. Whether they can actually be restored has never been tested.

    3-2-1 backup concept with restore tests

  3. 03

    An audit, NIS2 requirements or an incident call for a reliable security baseline.

    Security assessment and prioritised action plan

  4. 04

    Recurring tasks are done by hand – with the effort and error risk that comes with it.

    Scripts, pipelines and infrastructure as code

03How I work

Three principles.

  1. 01

    Understand before changing.

    Every environment has grown over time. Inventory and dependencies first, then the change.

  2. 02

    Standards over workarounds.

    Proven tools and common conventions – so systems can be run by others, not just by me.

  3. 03

    Documented, not memorised.

    What I build is written down and versioned. Knowledge stays with the company, not with one person.

04This site

This website is a work sample in itself.

What I implement for clients applies here too: only what is needed – and everything verifiable.

  • Served statically – no server code, no database
  • No cookies, no visitor profiles – JavaScript only for cookieless audience measurement
  • No third-party requests, fonts hosted locally
  • Strict security headers: Content Security Policy, HSTS, protection against clickjacking and MIME sniffing
  • Light and dark mode follow your system, reduced motion is respected
$ curl -sIL https://sanlytech.de HTTP/2 200 content-security-policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; object-src 'none'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'cross-origin-opener-policy: same-originpermissions-policy: camera=(), microphone=(), geolocation=(), interest-cohort=()referrer-policy: strict-origin-when-cross-originstrict-transport-security: max-age=63072000; includeSubDomains; preloadx-content-type-options: nosniffx-frame-options: DENY # trimmed: final response, security headers only · source: vercel.json · build 7885ebb $

05 Contact

A concrete topic on the table?

Give me a short outline of where you stand. You get an honest assessment of whether and how I can help – no sales pitch.

info@sanlytech.de
  • Replies usually within the same business day
  • The e-mail opens with a short template