Ask anyone who has rolled out TI components in German healthcare practices and you'll hear the same story: a technician drives to the practice, spends half a day configuring a connector, a card terminal, and network routes — and the next practice is waiting an hour down the autobahn.

That model — the Dienstleister vor Ort (DVO) — worked when TI was new and deployments were rare. It doesn't scale to the pace TI 2.0 is moving at.

What zeroDVO is

zeroDVO is an approach to TI component rollout without on-site service visits. Practices onboard themselves through a guided flow; configuration, certification handshakes, and post-install verification happen remotely, against cloud-based TI infrastructure.

Built by verkstedt and deployed via our partners at Thevea and ehex, zeroDVO takes the "truck roll" out of TI deployment. What used to be an afternoon becomes a self-service onboarding step.

Why it matters

For PVS vendors, platform operators, and Krankenkassen the benefit is direct:

• Rollout speed scales with servers, not with service vans. No more capacity ceilings defined by how many technicians are on the road.
• Cost per deployment drops by an order of magnitude. Travel time and on-site hours are the biggest line items; removing them changes the unit economics of TI entirely.
• Practices onboard when it suits them, not when a technician has a slot three weeks out.

What's behind it

zeroDVO isn't a single component — it's a set of remote-capable flows that cover what an on-site technician used to do manually: identity provisioning, certificate rollout, network configuration checks, and first-run validation against the gematik reference environment. We've been operating it in production long enough to know which edge cases bite and which ones don't.

If you run a platform that needs to onboard thousands of practices — or if on-site rollout is becoming your bottleneck — let's talk.