Planned public self-service platform
Managed Verse is planned to launch on 1 January 2027 as a public self-service cloud cyberrange. Users will create an account and configure their own authorized security exercises. Vulnverse will host and operate the native platform and cloud.
The planned service replaces all previous services and removes the customer cloud-operation workflow. All new inquiries are paused during the transition. Read Managed Verse →.
The older CLI and offline packages below do not specify the underlying cloud integrations, prices or service levels of Managed Verse. Provider names and logos alone do not establish those details.
Previous provider references at a glance
| Provider | Legacy reference | What the reference describes |
|---|---|---|
| AWS | Named range CLI and Terraform infrastructure | EC2 scenario application and a separately staged telecom runtime in EKS. |
| Microsoft Azure | Offline projection compiler and shared contracts | Planning and contract examples without resource creation in that package. |
| Google Cloud | Offline projection compiler and shared contracts | Planning and contract examples without resource creation in that package. |
Oracle Cloud and Alibaba Cloud are outside these legacy references. This table does not specify the underlying provider integrations of planned Managed Verse.
What the portability reference preserves
The reference architecture separates scenario meaning from cloud products. A target graph describes services and access relationships. Behavior plans describe activity. Agent, effect, evidence and evaluation contracts describe authority, outcomes and verification.
A provider mapping needs to preserve the scenario meaning and required isolation. Where a required capability cannot be met, a clear refusal is more useful than an undocumented approximation. Equivalent virtual machines or Kubernetes clusters alone do not establish equivalent exercise behavior.
What the older offline examples demonstrate
The legacy Azure and Google Cloud packages compile portable inputs into audit projections. Their tests check that a projection retains meaning, rejects altered inputs and cannot grant candidate execution authority. Those packages do not create subscriptions, projects, clusters or networks.
A deterministic fake provider exercises bounded failure, retry, stop and destroy paths in memory. Its inventory is simulated. These examples help explain lifecycle reasoning; they do not report the health or availability of planned Managed Verse.
Read a provider claim with its evidence
A meaningful deployment claim names the product version, provider, identity and policies involved. Review its resource mappings, isolation checks, readiness observations, evidence handling and cleanup results.
Include expired credentials, interrupted operations, missing telemetry, policy drift and partial teardown in that review. A missing observation cannot establish health. Changes to the relevant infrastructure or policy require renewed checks of the affected assumptions.
The older examples on this page are not certification evidence. Any Managed Verse availability or certification claim needs its own stated release scope and supporting material.
Read the planned service or study a legacy reference
Read Managed Verse → for the planned public self-service offering. At launch, users will define their exercises in the hosted platform; they will not need the AWS CLI setup below to operate it.
For historical study of the older AWS CLI, use the legacy setup guide and its cleanup instructions. For reference planning and lifecycle concepts, read the legacy architecture and offline examples.
Source and contribution provides legacy context. The previous implementation does not specify planned Managed Verse feature or provider details.