Understand the planned self-service platform
Managed Verse is planned as a public self-service cloud cyberrange. At launch, users will be able to create an account and configure authorized exercises. Vulnverse will operate the native platform and cloud, so users will not need to provision or maintain an exercise cloud.
The platform overview explains the planned simulated organizations and connected systems. Simulation connects technical activity with people, teams, goals and observed decisions.
All new inquiries are paused during the transition. Read Managed Verse →.
Study the previous CLI delivery model
The older deployment tool is named vulnvm. Its setup reference covers local prerequisites, AWS account configuration and a named telecom run.
Legacy CLI deployment explains its resource plan, run ownership and separate EC2 and staged EKS application paths. These procedures belong to the previous delivery model being replaced; they are not customer setup instructions for Managed Verse.
Inspect and close a legacy CLI run
Legacy CLI operations covers status, Terraform logs, Kubernetes workload checks and named teardown for that implementation.
The examples keep one explicit run name from planning through cleanup. They help explain how the older tool binds an operation to the intended environment.
Distinguish previous delivery from Managed Verse
Legacy CLI security boundaries describes account separation, operator access and evidence handling in the older example. Its restrictions and cleanup behavior are specific to that reference.
Planned platform operation separates Vulnverse-operated Managed Verse from the legacy provider references. Users will define their own authorized exercise boundaries in the planned hosted platform.
Read the previous reference designs
Legacy architecture describes infrastructure, workloads and control boundaries. The evaluation reference covers older candidate contracts; evidence and replay explains the earlier local record and transcript design.
These pages provide historical implementation context. They do not specify planned Managed Verse feature limits, underlying cloud integrations or certification. Read the planned platform scope →.