Vernix.one connects to the infrastructure you already have.
Vernix.one is not another tool you need to migrate to. It reads from your existing cloud accounts, Kubernetes clusters, code repositories, and configuration management systems — and builds a model from what’s already there. Here’s what it connects to.
Cloud providers.
- Amazon Web Services (AWS) — EC2, EKS, RDS, S3, VPC, Lambda, and more
- Microsoft Azure — Virtual Machines, AKS, SQL, Storage, Virtual Networks
- Google Cloud Platform (GCP) — Compute Engine, GKE, Cloud SQL, VPC
- Private cloud environments — OpenStack and VMware vSphere
Discovery connects via read-only API credentials. Vernix.one requires only the minimum permissions needed to read infrastructure metadata — no write access, no admin access.
Container orchestration.
- Kubernetes — any distribution: vanilla, EKS, AKS, GKE, OpenShift, Rancher
- Helm — chart-based deployments are understood and modeled correctly
- Docker Compose — for development and smaller production environments
Vernix.one discovers pods, deployments, services, ingresses, namespaces, config maps, and cluster nodes. The relationships between them — which service connects to which database, which pod runs on which node — are mapped automatically.
Infrastructure as Code.
- Terraform — HCL files and state files
- Pulumi — TypeScript, Python, Go, and .NET programs
- Ansible — playbooks and inventory
- CloudFormation — AWS CloudFormation templates
Vernix.one reads IaC files from connected Git repositories or directly uploaded files. The infrastructure model includes both the intended state (from IaC) and the actual state (from live discovery), making drift immediately visible.
Version control and repositories.
- GitHub — repositories, branches, and pull requests
- GitLab — repositories and CI/CD pipelines
- Bitbucket — repositories
- Azure DevOps Repos
Repository connections allow Vernix.one to track IaC changes alongside infrastructure changes. When a Terraform change is merged, Vernix.one sees it. When the resulting infrastructure change is deployed and picked up by discovery, the two events are linked in the version history.
Configuration management.
- Ansible — inventory and playbooks
- Chef — cookbooks and node data
- Puppet — manifests and node reports
- SaltStack — states and grains
Configuration management data enriches the infrastructure model with operational state — patch levels, package versions, running services, and applied configurations.
Service registries and discovery.
- Consul — service registry and health status
- etcd — Kubernetes-backed service data
- Internal DNS — service name resolution mapping
Service registry data adds the application layer to the infrastructure model — which services are registered, their health status, and their network endpoints.
Diagram and documentation import.
- draw.io / diagrams.net — import existing architecture diagrams
- Mermaid — import text-based diagrams
- ArchiMate — enterprise architecture models
Import an existing diagram and Vernix.one builds an infrastructure model from it. You can then connect live discovery to verify what’s actually deployed versus what was designed.
What Vernix.one generates and exports.
- Terraform — deployment-ready HCL files
- Pulumi — TypeScript, Python, or Go programs
- Ansible — playbooks and inventory
- Mermaid diagrams — embeddable in documentation
- draw.io diagrams — editable architecture files
- PNG / SVG diagrams — for presentations and reports
- PDF compliance reports — for auditors and regulators
- JSON / YAML infrastructure inventory — for integration with other tools
REST API.
Every capability in Vernix.one is accessible via REST API. Query the infrastructure graph, trigger discovery scans, generate IaC output, pull compliance reports, and retrieve version history programmatically.
The API allows Vernix.one to integrate into existing workflows: trigger a compliance check from a CI/CD pipeline, pull dependency data into an incident management tool, or sync the infrastructure inventory with a CMDB.
API documentation is available after deployment. Contact us for early access to API specifications.
Don’t see an integration you need?
Vernix.one is under active development. If you work with infrastructure tooling that isn’t listed here, let us know. We prioritize integrations based on customer demand.
Contact us at tech@vernix.one with the integration you need and we’ll let you know our current roadmap for it.
Want to see how Vernix.one connects to your stack?
Book a demo and bring your current toolchain. We’ll show you exactly how Vernix.one discovers and models your infrastructure — with the tools you already use.