Core Concepts
Understanding how VeloxaHost models cloud infrastructure will help you make better architectural decisions from the start.
Instances
An instance is a single compute unit — either a system container or a full virtual machine (VM). Both types share the same API, console UI, and billing model.
Virtual machines are not available in veloxa-us-east-1 yet. That region runs container servers only.
| Property | System Container | Virtual Machine |
|---|---|---|
| Startup time | Under 3 seconds | Under 30 seconds |
| Kernel isolation | Shared host kernel | Own kernel |
| SSH access | ✅ | ✅ |
| Docker support | ✅ (Docker-ready config) | ✅ |
| Snapshot speed | Instant | Seconds |
| Use case | Most workloads | Custom kernels, full isolation |
For most workloads, use system containers. They start faster, use less overhead, and behave identically to a full Linux server, and Docker runs inside them. Choose VMs, where a region offers them, when you need a custom kernel, GPU passthrough, or complete hardware isolation.
Organizations
An organization is your account's namespace. All resources (instances, storage, IP addresses, API keys) belong to an organization, and billing is per organization. You name your organization when you sign up.
- Resources in different organizations are fully isolated from each other
- You invite team members to the organization with a role: owner, admin, member, or viewer. See Teams & Roles →
Regions
A region is a physical data center location. All resources you create are bound to a region. Today the only open region is veloxa-us-east-1 (Washington, DC area); more are planned. See Regions & Availability →
Networks
In veloxa-us-east-1, servers are reached through a block of ports on the region's shared IPv4 address, and you can add a dedicated IPv4 address to any server. Servers are port-isolated from each other on the shared bridge, so one customer's server cannot reach another's over the internal network. Private networks are not available in veloxa-us-east-1 yet. See Networking guide →
Plans & Resources
Every instance is created from a plan that defines its CPU cores, memory, and root disk size. You can resize CPU and memory on a running server; disk size is fixed once the server is created.
Start small — CPU and memory can be raised later, but disk size can't be changed, so pick a disk that fits your data without over-provisioning.