From a drawing to a deployed, compliant, fully documented infrastructure. In one platform.
Vernix.one works in a continuous loop. You design or discover infrastructure. Vernix.one models it. Everything else — diagrams, deployment code, compliance reports, change history — flows from that model automatically. Here’s how each part works.
Step 1: Put your infrastructure in.
Vernix.one accepts infrastructure knowledge in whatever form it currently exists. You don’t need to start fresh or migrate anything.
Option A — Draw it
Use Vernix.one’s built-in visual designer to sketch a new architecture. Define components, set relationships, assign environments and ownership. The designer is infrastructure-aware — it understands the difference between a service, a container, a cluster, and a cloud region.
Option B — Import a diagram
Already have architecture diagrams in draw.io or Mermaid format? Import them. Vernix.one reads the topology, identifies the components, and builds an infrastructure model from your existing work.
Option C — Import infrastructure as code
Have Terraform, Pulumi, or Ansible files? Import them. Vernix.one parses the infrastructure definitions, builds the model, and generates diagrams and documentation from what you’ve already written.
Option D — Connect to live systems
Connect Vernix.one to your cloud provider APIs, Kubernetes clusters, network scanners, configuration management systems, or IaC repositories. Vernix.one scans everything automatically and builds the model from what’s actually running. Discovery runs continuously — the model stays current without manual updates.
Most customers use a combination: import existing diagrams and IaC to capture the design intent, then connect to live systems to verify what’s actually deployed.
Step 2: Vernix.one builds the infrastructure graph.
Everything that comes in — from diagrams, from code, from live systems — is mapped into the Infrastructure Knowledge Graph. This is the core of the platform.
The graph represents:
- Every infrastructure component as a node: servers, containers, services, databases, load balancers, networks, storage, applications
- Every relationship as an edge: runs on, belongs to, connects to, depends on
- Ownership and responsibility: team, environment, lifecycle state
- History: every version of every node and relationship, going back to the first discovery
The graph enables questions that would otherwise require manual investigation across multiple tools:
- Which services are exposed to the internet?
- What breaks if this database goes down?
- Where is personal data stored?
- What changed between last Tuesday and today?
- Which systems are not yet compliant with DORA?
Step 3: Generate everything from the model.
Once the graph exists, Vernix.one generates all outputs from it. Every output is derived from the same single source of truth — so everything stays consistent with each other and with reality.
Architecture diagrams
Vernix.one generates diagrams directly from the infrastructure graph. Supported formats include Mermaid diagrams, draw.io diagrams, architecture topology diagrams, and service dependency graphs. When the infrastructure changes, the diagrams update. You never maintain a diagram by hand again.
Infrastructure as Code
The graph feeds a template engine that generates Terraform, Pulumi, or Ansible definitions. New environment? Generate deployment-ready code from a known-good model in minutes. The code reflects exactly what the model contains — no translation, no interpretation.
Compliance reports
The compliance engine evaluates the graph against DORA, NIS2, GDPR, ISO 27001, PCI DSS, the AI Act, and the Cyber Resilience Act. Reports are generated from the current state of the model. Historical reports can be generated from any past version. Audit documentation that used to take weeks to assemble now takes minutes to export.
Dependency graphs
Vernix.one generates visual dependency maps from the graph. These are separate from architecture diagrams — they focus specifically on which systems depend on which, making blast-radius analysis and change impact assessment straightforward.
Infrastructure inventory
A continuously updated, searchable record of every infrastructure component, its configuration, its relationships, its owner, its environment, and its lifecycle state. The single place your entire organization can go to answer ‘what do we have and what is it doing?’
Step 4: Deploy from the model.
Generated IaC code goes directly into your deployment pipelines. Vernix.one does not require a specific CI/CD tool — it generates standard Terraform, Pulumi, or Ansible that works with any pipeline you already use.
The result: from architecture decision to running infrastructure in days, not weeks. The first Vernix.one customer reduced their deployment cycle from 90 days to 10.
Step 5: Watch it stay current.
After deployment, Vernix.one continues scanning. Connected discovery sources are polled continuously. When something changes in your environment — a new service, a configuration update, a new environment added — the model updates automatically.
If the real infrastructure diverges from the designed architecture, Vernix.one surfaces the drift immediately. You see it as it happens, not when an auditor finds it.
Step 6: Prove everything.
Compliance reports, change history, dependency graphs, and infrastructure inventory are always ready. When a DORA assessment arrives, you export the report. When an incident review asks what the infrastructure looked like at 14:00 last Tuesday, you pull the version from that timestamp. When a new engineer asks what depends on the payments database, you query the graph.
Governance stops being something you prepare for. It becomes something you already have.
Want to see the full loop with your own infrastructure?
Book a demo. Bring a diagram, a Terraform file, or just access to one environment. We’ll run the full workflow — input to output — in a single 45-minute session.