Marius Voß
DevRel · edge infra
Writing for Elido since April 2024
Marius runs developer relations and edge infrastructure at Elido. Before joining the team in 2024 he spent eight years at a Berlin-based CDN operator and two years on the network reliability team at a German neo-bank, where he learned that the worst kind of latency bug is the one that only shows up at 3% of edge POPs.
He maintains the Elido edge-redirect runbook, contributes to the Helm chart, and writes the engineering posts that go deeper than "we use ClickHouse for analytics" — including the cache-invalidation propagation post, the multi-region failover testing post, and the on-demand TLS deep dive.
Outside Elido, Marius is a regular speaker at the German Cloud Native meetup and contributes occasional patches to fasthttp.
Expertise
- Edge networking and routing
- Multi-region failover and capacity planning
- ClickHouse query tuning
- Helm + Kubernetes for self-hosted Elido
Elsewhere
Posts by Marius Voß
Why we use ClickHouse for click analytics (and not Postgres)
The workload is 100M+ events/month, write-heavy, analytical-query-shaped. Why columnar wins, the schema we ship, and what we hit at 90 days of Postgres
engineeringHitting p95 < 15ms for redirects from FRA, ASH, and SGP
How Elido's edge-redirect path holds a 15ms p95 budget on cache HIT across three regions — architecture, cache strategy, real-region measurements
engineeringCornerstoneDeep links for mobile apps without an SDK
Universal Links + Android App Links cover 80% of deep-linking use cases without a paid SDK. The two association files, the trade-offs, and the cookbook
featuresSelf-hosting Elido on k3s — a complete playbook
A step-by-step guide to deploying the full Elido stack on a k3s cluster: Helm bootstrap, 14 services, the data plane as StatefulSets, Caddy on-demand TLS, backups, and upgrade strategy.
engineeringCornerstoneConnecting Elido to Claude and Cursor via MCP — a practical guide
How to wire @elido/mcp-server into Claude Desktop and Cursor so your AI agent can shorten URLs, generate QR codes, and query click analytics inline — without leaving your workflow.
featuresCornerstoneHow to set up a custom domain with TLS in 5 minutes (using Elido)
A step-by-step playbook for pointing your own subdomain at Elido, adding the two DNS records, and getting an HTTPS short link with automatic TLS — including the API call, common pitfalls, and how the certificate machinery actually works.
featuresDynamic vs static QR codes: what actually changes
Static QR encodes the URL directly. Dynamic QR encodes a short link. The difference determines whether you can edit the destination, track scans, or A/B route — and it matters before you print.
featuresCustom domain short links: DNS, TLS, and what runs at the edge
How branded short links actually work: DNS verification, ACME on-demand TLS issuance, edge redirect latency budgets, and the three failure modes operators hit in production
featuresManage your short links as Terraform
We shipped the only Terraform provider in the URL-shortener space — terraform-provider-elido. Here is what it does, how the resource lifecycle works, and the engineering trade-offs behind it.
engineeringCornerstoneShipping the Bitly migration: a worker, a token, a 30-minute budget
How we built one-click Bitly imports for Elido — the worker design, the conflict-resolution rules, and the four caps that keep an in-process goroutine safe.
engineeringSmart links explained: edge routing without an extra service
What a smart link is, where it runs, and the routing dimensions Elido supports. Engineering deep-dive on edge cache invalidation, first-match semantics, and when not to use one
featuresCornerstone