Hyper Vorser
API-first control plane for isolated Linux runtimes, wildcard domain routing, TLS automation, backups, firewall policy, and SSH access orchestration.
Hyper Vorser Control Plane
Use Compute to provision and manage VMs, then use Domains & Routes to map hostnames and HTTPS ports.
For operators: Security manages firewalls, Storage handles buckets/backups, and Users & Access controls API keys and identity.
Issue magic links, change role, rotate password, revoke sessions.
Grouped by VM name prefix (`-`, `_`, `.`).
Per-VM counters, alert feed, and control-plane event trail.
TOKEN=$(curl -sS -X POST /api/v1/auth/login \
-H 'content-type: application/json' \
-d '{"email":"admin@example.com","password":"..."}' | jq -r .session_token)
Pass token via `Authorization: Bearer $TOKEN`.
POST /api/v1/vmsProvision VM with SSH keyGET /api/v1/vms/{id}/connectionResolve SSH host, port, and commandsPOST /api/v1/auth/magic/requestRequest one-time magic login linkPOST /api/v1/auth/magic/consumeExchange magic token for sessionPOST /api/v1/users/{id}/magic-linkAdmin issue login link for userPUT /api/v1/users/{id}Update user role, email, or passwordPOST /api/v1/vms/{id}/publishProvision domain + TLS + VM port mappingPUT /api/v1/routes/{route_id}Update HTTP/HTTPS mappingPOST /api/v1/vms/{id}/backupsCreate backup to storageGET /api/v1/storage/bucketsList object bucketsVMs expose hostname plus SSH mapped port via connection endpoints. HTTP/HTTPS routes are hostname-driven with managed TLS.
Use route mapping editor to change target VM, port, protocol, and TLS mode without recreating hostnames.