Case study · Observability software

One network for a company that lives in customers' environments

Cribl builds data infrastructure for observability — and its people need secure reach into lab environments, demo fleets, and customer-adjacent systems. OpenVLAN replaced a tangle of per-purpose VPNs with one identity-based network.

Cribl — ephemeral lab workstations on a bench

The challenge

A distributed company, multiple cloud environments, and a lab strategy that spawns short-lived infrastructure on demand. Field engineers reached demo environments through one VPN, support through a bastion, engineers through cloud-specific VPNs — each with its own client, credential lifecycle, and failure mode. Onboarding a new engineer meant provisioning four kinds of access; offboarding meant hoping nothing was missed.

The switch

Cribl standardized on OpenVLAN as the connective tissue: ephemeral lab environments join a dedicated tailnet on creation and disappear with it. Identity comes from their SSO, so access reviews became group reviews instead of credential archaeology.

The results
4→1

access tools consolidated into one

90s

to stand up a networked lab environment

0

standing credentials in field demos

Why it worked

The match between ephemeral infrastructure and ephemeral network identities. When an environment exists for a day, its network access should exist for exactly that day too — not live on in a VPN config file somewhere.

This case study is an illustrative example with fictional data for demonstration purposes.

Infrastructure that comes and goes?