VeloxaHost makes deploying cloud infrastructure fast and intuitive. In this guide you'll go from registering an account to having a fully configured cloud instance running in under five minutes.
Prerequisites: A VeloxaHost account (sign up free at console.veloxahost.com) and an SSH key pair. Run ssh-keygen -t ed25519 if you don't have one yet.
Step 1 — Create Your Organization
The sign-up form asks you to name your organization. Think of it as your workspace — all your instances, IP addresses, and storage live inside it. Give it a meaningful name (your company or project name works great).
Your organization comes pre-configured with a Starter plan which includes a 14-day free trial. No credit card required to begin.
Step 2 — Add an SSH Key
Navigate to Settings → SSH Keys and paste your public key (~/.ssh/id_ed25519.pub). VeloxaHost will inject this key at deployment time so you can SSH in immediately without passwords.
# Print your public key
cat ~/.ssh/id_ed25519.pubStep 3 — Create an Instance
Click New Server from the dashboard. You'll configure:
- Name — a hostname for your instance (e.g.,
web-prod-01) - Type — container (ultra-fast, shared kernel); VMs are not available in
veloxa-us-east-1yet - Image — Ubuntu 22.04 LTS is a safe default for most workloads
- Region —
veloxa-us-east-1, the only open region today - Size — start small (1 vCPU / 1GB RAM); CPU and RAM can be raised later without a restart, but disk size is fixed
Then click Create Server.
Tip: Containers start in under 3 seconds and use far less memory than VMs, and Docker runs inside them. VMs, for workloads that need kernel-level access, are planned but not available in veloxa-us-east-1 yet.
Step 4 — Configure a Firewall
Until you attach a firewall, traffic to your server is allowed (only outbound TCP port 25 is blocked by default). Go to Firewalls → New Firewall and use Add Rule for the ports your app needs:
- Port
22(SSH) — your IP only - Port
80(HTTP) — anywhere (0.0.0.0/0) - Port
443(HTTPS) — anywhere
Attach the firewall on your server's page and it takes effect within seconds. Once it is attached, inbound traffic that no rule allows is dropped; outbound traffic stays allowed unless you add a rule that drops it.
Step 5 — Connect via SSH
Your server is reached through a block of ports on the region's shared IPv4 address, shown on the server page. The first port of the block forwards to SSH (port 22):
ssh -p <port> root@<shared-ip>You're in. From here you can install packages, deploy your application, or run your provisioning scripts.
What's Next?
Now that your instance is running, explore the rest of the platform:
- Harden your instance — secure SSH, firewall rules, auto-updates
- Run Docker containers — multi-service stacks on VeloxaHost
- Automate deployments — GitHub Actions → VeloxaHost CI/CD
- Set up alert rules under Alerts in the console so you're notified of issues before users are
Have a question? Open a support ticket from your VeloxaHost console or email us at support@veloxahost.com.