Instances

VeloxaHost instances are your primary compute unit. They can be system containers (ultra-fast, shared kernel) or virtual machines (full hardware emulation). Both are managed identically from the console and API.

📌

Virtual machines are not available in veloxa-us-east-1 yet. That region runs container servers only, and Docker runs inside them (see below).

Containers vs Virtual Machines

Property	Container	Virtual Machine
Start time	Under 3 seconds	Under 30 seconds
Kernel	Shared with host	Own kernel
Disk footprint	10–50 MB base	1–5 GB base
Density	Very high	Medium
Isolation	Namespace isolation	Full hardware emulation
Use case	Web apps, microservices, CI	Databases, legacy apps, kernel modules

💡

Rule of thumb: Start with containers. If you need to load a kernel module, run a Windows workload, or need complete network namespace control, use a VM in a region that offers them.

Docker on a container server

Container servers can run Docker and Docker Compose. New servers are ready for it; on a server created earlier, open it and choose Enable Docker (the server restarts once). Then install Docker as usual, for example:

apt-get update && apt-get install -y docker.io docker-compose-v2
docker run --rm hello-world

Containers you publish with -p are reachable through your server's ports, the same way as anything else running on it.

Instance Sizing

Instance resources (CPU, RAM, disk) are set at creation time. CPU (1–32 vCPU) and memory (128 MB–64 GB) can be resized at any time from the instance detail page, and the change applies instantly. Disk size is fixed once the instance is created.

Pick one of the hourly sizes below (they create container servers; Veloxa 16 is available on request), or choose Custom resources within your plan's limits (defaults: 1 vCPU, 512 MB RAM, 10 GB disk).

Size	vCPU	RAM	Disk	Price
Veloxa Nano	1	1 GB	25 GB	$0.01/hour, max $4/month
Veloxa 1	1	2 GB	50 GB	$0.02/hour, max $8/month
Veloxa 2	2	4 GB	80 GB	$0.03/hour, max $15/month
Veloxa 4	4	8 GB	160 GB	$0.05/hour, max $30/month
Veloxa 8	8	16 GB	320 GB	$0.09/hour, max $60/month

Instance Lifecycle

Instances move through the following states:

Stopped — Created but not running. Resources are allocated but no compute happens.
Starting — Transitioning to running. Takes 1–30 seconds depending on type.
Running — Active and accepting connections.
Stopping — Graceful shutdown in progress.
Frozen — Suspended. Memory state preserved. Resume instantly.
Error — An operation failed. Check the console logs.

Exec & Web Console

You can get a shell inside an instance without SSH using the console tab in the instance detail page. This uses a secure WebSocket tunnel directly to the instance.

The API can also run a single command. The call is synchronous: it waits for the command to finish (or for timeout, in seconds) and returns its stdout and stderr. Only allowlisted commands are accepted; use the web console when you need a shell.

# From the VeloxaHost API
curl -X POST /api/v1/instances/web-1/exec \
  -H "Authorization: Bearer veloxa_..." \
  -H "Content-Type: application/json" \
  -d '{"command": ["uptime"]}'

# Optional fields: "environment": {"KEY": "value"}, "timeout": 30

📌

The web console is available even if your firewall blocks SSH. It's particularly useful for recovering access to a misconfigured instance.

Plan Limits

Each organization plan has instance, CPU, and memory limits. Attempting to create an instance that exceeds plan limits will fail with a clear error message. Upgrade your plan from Settings → Billing to increase limits.