Border0 + OpenVLAN FAQ

Answers for Border0 customers now that Border0 is part of OpenVLAN. Short version: your service keeps working, and the roadmap gets faster.

What happened?

Border0 — the zero-trust access layer for SSH, web, and database connections — has joined OpenVLAN. The teams and technology combine; the mission was always the same: access without the perimeter.

Does my Border0 service keep running?

Yes. Existing Border0 portals, policies, and connectors continue to work unchanged. There is no forced migration date — we'll give at least six months' notice before anything changes, and most things won't.

Will OpenVLAN adopt Border0 features?

The Border0 team is building on OpenVLAN, bringing their experience with single-port access (one TCP port for SSH, HTTP, and DB protocols) and certificate-per-session models into the OpenVLAN access stack. Expect announcements in the changelog.

What should I do if I use both products?

Nothing immediately. Over time, running one platform instead of two will mean one identity integration, one policy language, and one audit log. We'll publish migration guides as capabilities converge.

What happens to my Border0 contract and pricing?

Existing terms are honored through their end date. Renewals transition to OpenVLAN plans at comparable or better terms — contact us before renewal and we'll map it for you.

Who do I contact for support?

Keep using Border0 support channels today; they now route to the combined team. New tickets can also go through OpenVLAN support.

Is there someone to talk to about all this?

Yes — reach the combined team here, or your existing account contact.