Reverse proxy & automatic TLS
Traefik sits in front of everything as the single entry point, discovering new services automatically and issuing Let's Encrypt certificates for each one — no manual TLS management, no unencrypted routes.
A real example, not a mockup
Everything on this page is running in production right now — the same site you're reading. We designed it, deployed it, and operate it ourselves, using the same tools and the same approach we'd bring to your project.
How it fits together
One reverse proxy at the edge, a set of self-hosted services behind it, and a private network for anything that shouldn't be reachable from the internet at all.
A simplified view — the real deployment also includes automated backups, access logging, and rate limiting not shown here.
What's actually running
Traefik sits in front of everything as the single entry point, discovering new services automatically and issuing Let's Encrypt certificates for each one — no manual TLS management, no unencrypted routes.
One login, backed by a real identity directory, protects every internal tool that needs one. Adding another protected service later is a config change, not another separate user database.
A full GitLab instance — repositories, issues, and CI pipelines — running on our own infrastructure. Not rented, not rate-limited, entirely ours.
A dedicated relay so every service — this site's contact form included — can send transactional email without holding its own provider credentials.
Every service runs as an isolated, rootless container — no privileged daemon, a smaller attack surface, and each piece independently replaceable.
Nightly backups run unattended, including a proper application-consistent backup for GitLab — not just a raw file copy — with old backups pruned automatically.
This site itself: English and German, proper hreflang tagging, structured data, and a sitemap — built to be found, not just to exist.
Whatever the scale, we can design and run something like this for your business too.