Fully isolated, high-performance dev labs on a single Proxmox host.

MSL Setup (Multiverse Secure Lab Setup) is an open-source framework for building fully isolated multi-project virtual lab networks on a single Proxmox host, with automated provisioning and VPN-based access for securely sharing isolated environments.

WHAT ZELOGX BUILDS

Security-by-default. Isolation-by-design.

Zelogx is focused on practical isolation, operator-friendly workflows, and clear boundaries. Start small, scale clean, and keep every project in its own universe.

Multiverse Isolation

Project-by-project network isolation on a single Proxmox host — predictable boundaries, predictable outcomes.

Proxmox SDN + Pritunl VPN

A clean path for remote access without collapsing your segmentation model. Built for lab realism, not toy demos. VPN traffic is scoped to the lab networks only – your users' Internet traffic does not hairpin through the VPN server.

One-click-ish, not Magic

Automate the boring parts, keep the important knobs visible. You stay in control — no black-box surprises.

Documentation that matches reality

Your environment is a product. We prioritize reproducibility and audit-friendly structure from day one.

WHY IT MATTERS

Dev environments are where "small mistakes" become real incidents

FIELD NOTES

Playbooks & whitepapers for real-world MSL Setup

Short, opinionated write-ups on how MSL Setup actually changes day-to-day operations: not just "release notes", but practical notes you can reuse for your own lab.

WHO IT'S FOR

Clarity beats complexity.

For teams where dev labs "just happened".

In most organizations, dev and test environments were never really "designed".
They just… happened:

  • A few random cloud VMs spun up for a PoC
  • A VPN here, a jump box there
  • Security groups copied from "something that worked last time"

Nobody is officially in charge, but everyone quietly hopes
nothing bad ever comes out of those environments.

MSL Setup is for teams and freelancers who want to change that.

  • For whoever ended up owning "the lab" by accident
    You finally get a clean, repeatable pattern: every project lives in its own L2-isolated network with a dedicated VPN entry, instead of a pile of ad-hoc rules.
  • For managers who know dev is part of the attack surface
    You can say, "Our dev environments are isolated by design, with a standard operating model that prevents cross-project data leaks by default" – and mean it.
  • For CxO-level stakeholders who have been half-ignoring this problem
    Instead of another vague "we should review dev security someday", you can put a concrete option on the table: isolate dev at the network layer, keep VPN access scoped to the lab only (not all Internet traffic), and standardize operations so this whole class of incidents stops stealing your attention.

You don't just get a lab that works — you get a lab whose behavior you can explain,
defend, and eventually hand over without fear.

Zelogx operator experience

WHO IT'S FOR

For the people quietly on the hook when dev labs go wrong.

NEXT STEP

Choose your path and get started

Compare editions on the Pricing page and choose the plan that fits your needs.

FAQs

Questions, answered.

A few practical answers before you invest time (and money) into your next lab setup.