Infrastructure on request.Not on ticket.
Verlocx lets teams create, operate and retire virtual machines on their own — on your Proxmox and VMware clusters, inside your rules.
- Proxmox VE
- vSphere
- Windows Server
- Linux
- Active Directory
- Entra ID
- PostgreSQL
Turn VM requests into self-service, with rules for access and quotas.
Stop handling VMs ticket by ticket. Without a portal, every request means hypervisor access, a checklist, a domain join by hand and a spreadsheet of who owns what.
Faster to provision. Pick a template; size, quota and name are checked live against the project's rules.
The same every time. Clone, boot, rename, domain join and your own steps — in order, with each step on record.
Simpler to run. One portal for requests, rules, snapshots and consoles, on the cluster you already run.
Visible from day one. Every request, change and command lands in the audit log — in the UI and the API.
Request in minutes. Roll back in seconds.Every step on record.
From the request to the running VM, and every change after it — in one place, for the people who own the VMs.
Ask for a VMThe rules answer, not a ticket
Templates, sizes and owners are checked live against the project's rules. Confirm, and the clone starts on your cluster.
Create a new virtual machine
Set the VM size within the caps configured for this template.
- Template allowed in this project: passed3 templates allowed · windows-server-2025
- Size between the template minimum and the project's cap: passed2–16 vCPU · 4–64 GB · 60–250 GB
- Fits the project quota: passed58/64 vCPU · 208/256 GB · 1770/2000 GB
- Name follows web-prod-<2100–2199>: passedprefix and number match the template's rule
- VMID 2104 from the name: passedfree on the cluster, not recently freed
VMID 2104
A simulation in your browser — nothing is created.
Watch it come upStep by step, live
Clone, boot, rename, domain join and your own steps — each with its own status and timer while it runs.
Change a fleetSee the result before it runs
Building blocks and your own scripts on many VMs at once, with a dry run that shows what would change.
| VM | Disable IPv6 on all adapters | C:\Verlocx\info.txt | Windows Time running + automatic | Firewall HTTPS inbound | Example Root CA | Refresh group policy |
|---|---|---|---|---|---|---|
| web-prod-01 | ||||||
| web-prod-02 | ||||||
| web-prod-03 | ||||||
| app-prod-01 | ||||||
| app-prod-02 | ||||||
| db-prod-01 |
Click a cell for its message and output. changed = something was (or in check mode would be) changed · ok = already as wanted.
Undo what went wrongSnapshots per VM, for owners
Snapshot trees, rollback and backups per VM — without anyone needing access to the hypervisor.
Windows Server 2022 · pve-prod · pve-02 · IP 10.20.4.50
5 snapshots
| Name | Description | Size | Created | By | Actions |
|---|---|---|---|---|---|
clean-installPVE | Server 2022, sysprepped | — | Oct 2, 08:14 AM | Jonas Weber | |
domain-joinedPVE | Joined corp.example | — | Oct 3, 09:40 AM | Jonas Weber | |
pre-updatePVE | — | — | Oct 9, 05:05 PM | Mara Koch | |
kb-rolloutPVEcurrent | — | — | Oct 14, 06:30 AM | Jonas Weber | |
iis-testPVE | IIS role trial | — | Oct 11, 11:22 AM | Mara Koch |
Control who gets what, per project. Enforce rules and quotas before anything is cloned.
Roles + rights. Who may request, power, open a console or delete — set per project.
Agent in every VM. VMs dial out to your backend — no inbound port on the guest, and only a backend with the pinned key is accepted.
Rules. Requests outside the project's rules stop before anything is cloned.
Quotas. VMs, vCPU, memory and disk per project — with costs alongside.
Audit log. Every change, who made it and when — in the UI and through the API.
Runs on your servers
Team and Enterprise run the portal, its database and the backend on your infrastructure, next to your hypervisor and directory.
Company sign-in
People sign in with the company accounts they already have; what each of them may do is set per project.
Start with one project, grow to every team, and stay in control without tickets.
Rules, placement and clean-up are set once by administrators and then apply to every request.
Read the docsPlacement across nodes
New VMs join the right backup job and HA rule for the node they land on.
Leases
End dates with warnings, suspend and complete removal — so nothing is forgotten.
Quotas and costs
Limits per project, with what each VM costs alongside — no surprises at month end.
Deletion protection
Protected VMs can't be destroyed until someone with the right removes the flag.
Stay in sync with your fleet in real time.Every action is logged. Every change is visible.
CPU Usage
Daily CPU % · average, low–peak range · last 30 days
Activity
| Time | Actor | Action | Result |
|---|---|---|---|
2m ago Oct 20, 10:40:00 | Anna Keller | Created VM lab1-252 | allowed |
6m ago Oct 20, 10:36:00 | Marie Lang | Ran script on build-07output | allowed |
14m ago Oct 20, 10:28:00 | Lisa Braun | Delete VM web-prod-01 | denied |
23m ago Oct 20, 10:19:00 | Tom Richter | Took snapshot “before-upgrade” of sql-02 | allowed |
41m ago Oct 20, 10:01:00 | System | Lease expired — powered off VM “qa-web-03” | allowed |
58m ago Oct 20, 09:44:00 | Jonas Weber | Opened VNC console on sql-02 | allowed |
1h ago Oct 20, 09:27:00 | Tom Richter | Rebooted VM build-07 | allowed |
1h ago Oct 20, 09:06:00 | Anna Keller | Granted Operator to qa-team | allowed |
2h ago Oct 20, 08:32:00 | System | Group lease “Lab clean-up” — notify on lab1-217 (day 30) | allowed |
3h ago Oct 20, 07:40:00 | Jonas Weber | Resized VM sql-02 to 8 vCPU / 32 GB | allowed |
4h ago Oct 20, 06:42:00 | Lisa Braun | Open SSH console on db-01 | denied |
5h ago Oct 20, 05:37:00 | Marie Lang | Rolled back web-prod-04 to “pre-patch” | allowed |
- Live metrics from the agent. CPU, memory and every disk volume, reported from inside the guest.
- Spot full disks early. Alerts per volume, so the fullest drive is the one you hear about.
- Activity per VM. Power, snapshots, scripts and their output — on the VM's own timeline.
- Query it through the API. The same data over the REST API, with keys that carry their own rights.
A small agent in every VM.Outbound only, pinned key, updates itself.
Small and quiet. One service in the VM template; it reports, runs what it's asked and stays out of the way.
Outbound only. It dials out to your backend and trusts only the pinned key — no inbound port.
Updates itself. New versions are downloaded, checked against their hash and swapped in with a service restart.
Start free.Pay per VM when it matters.
Free runs in our cloud. Team and Enterprise run on your own infrastructure — with a 30-day money-back guarantee.
Free
For a lab or a small team getting started — in our cloud.
- Hosted in our cloud — nothing to install
- Up to 25 managed VMs
- 1 Proxmox VE cluster
- Self-service VMs, console & snapshots
- Verlocx agent for Windows guests
- Community support
Team
Fits 40 VMsFor platform teams running self-service in production.
30-day money-back guarantee
- Self-hosted on your infrastructure
- Proxmox VE and VMware vSphere
- Up to 1,000 VMs · unlimited projects
- Deployment & configuration workflows
- Leases, power schedules & alerts
- Roles, groups & Microsoft sign-in
- REST API & full audit log
- E-mail support
Enterprise
For several clusters, sites and strict requirements.
30-day money-back guarantee
- Everything in Team
- More than 1,000 VMs
- Multiple clusters & sites
- HA placement & backup-job integration
- Onboarding & migration support
- Priority support with SLA
30-day money-back guarantee. Not satisfied with a paid plan? Tell us within 30 days of your first payment and we refund it in full.
Questions, answered.Or ask us directly.
It depends on the plan. Free runs in our cloud for Proxmox VE clusters — nothing to install, you connect your cluster and start. Team and Enterprise run on your own infrastructure: the portal, its database and the backend sit on your servers and talk to your hypervisor and directory directly.
No. Neither the portal nor this website collects usage data, and framework telemetry is switched off. This site sets no cookies for visitors (only the portal's log-in uses a session cookie) and loads no third-party scripts.
A Windows service in the VM template. It only opens an outbound connection to your backend and accepts it only if the backend proves its pinned key — no inbound ports on the guest.
Administrators, per project: allowed templates, size limits, quotas, naming and VMID ranges, network defaults and the deployment workflow each template runs.
Paid plans come with a 30-day money-back guarantee. If you're not satisfied within 30 days of your first payment, tell us and we refund it in full — no questions asked.
Owners are warned in advance and can extend it. Otherwise the VM is suspended and later destroyed — disks, HA rule and the computer object in Active Directory.