Step 1. Prepare a VPS & Verify Prerequisites
Before launching the installer, provision a clean VPS/VDS (either from your own provider or via the recommended partners in /vps and /cabinet):
- Operating System: Clean Debian 13 (recommended) or Debian 12 x86_64. Avoid pre-installed control panels or conflicting firewall rules.
- Access Credentials: Public IPv4 address, SSH port (usually
22), username (rootor a sudo-enabled user), and either an SSH password or an OpenSSH/PEM private key (-----BEGIN OPENSSH PRIVATE KEY-----). - Domain (Optional before install): You can bind a custom domain and issue TLS certificates directly inside the Apium Cloud OS admin panel right after deployment.
- License Slot (Optional): If you plan to use Pro (up to 100 users, full REST API, Cascade) or Ultra (up to 1,000 users), purchase a lifetime slot in /cabinet beforehand—or start free on Lite (up to 25 users) and upgrade later.
Step 2. Launch the Zero-Disk SSH Wizard in Cabinet
Sign in to /cabinet (2FA supported), choose «Install on my server», and fill out the deployment form:
- Enter the server IP / Host, SSH Port, and SSH User.
- Select authentication type: SSH Password or Private SSH Key. Credentials remain strictly in memory for the active SSH session and are never written to disk (Zero-Disk architecture).
- Optionally select an unassigned paid license slot (Pro or Ultra) to auto-bind during provisioning, or leave it on Lite.
- Click «Install Apium Cloud OS on server» and watch the live progress console.
Step 3. The 4 Automated Installation Stages
What Happens During Deployment
Automated PipelineThe wizard executes four deterministic stages on your target Debian server and streams real-time logs to your Cabinet.
| Stage | Identifier | Actions Performed on Target VPS |
|---|---|---|
| Stage 1 | SSH Preflight & OS Check | Verifies SSH reachability, root/sudo privileges, Debian 12/13 compatibility, and available system resources. |
| Stage 2 | Prepare Apium Cloud OS Environment | Configures repositories, installs system dependencies, tunes kernel networking parameters, and prepares isolated directories. |
| Stage 3 | Bootstrap Runtime & Panel | Deploys the Rust control daemon, systemd services, Xray/Hysteria2/accel-ppp/strongSwan engines, nftables rules, and binds your license if selected. |
| Stage 4 | Health & Readiness Verification | Runs service health checks across core daemons and outputs your one-time panel URL, admin username, and temporary password. |
Step 4. First Login & Initial Panel Configuration
Once Stage 4 finishes, save the one-time credentials shown in the wizard output and open your admin console URL:
- 1. Secure Your Admin Account: Sign in with the temporary credentials and immediately update the administrator password.
- 2. Select Operating Mode: Keep Cascade VPN for multi-protocol internet & upstream relay routing, or enable Corporate Gateway for an isolated database, X.509 CA, AD/RADIUS, and segment ACLs.
- 3. Configure Domain & Protocols: Point your DNS A-record to the VPS IP, bind your domain in panel settings for TLS (Windows SSTP / HTTPS console), and enable the protocols you need (
VLESS Reality,Hysteria 2,Windows SSTP,L2TP/IPsec). - 4. Set Firewall & Shaper Profiles: Choose an
nftablestier (Basic,Restricted, orParanoidto block P2P/SMTP) and configure per-grouptcbandwidth limits.
Step 5. Managing, Importing & Transferring Licenses
- Auto-Bind via Wizard: Licenses selected in Step 2 activate automatically on the node during Stage 3.
- Manual Import (Standalone Servers): Copy your Server Identifier from the admin panel header, generate
license.keyin Cabinet, and import it in the panel. - One-Click VPS Migration: Moving to a new server? Click Unbind from server in Cabinet to revoke the old binding and reuse your lifetime slot on the new VPS.
Step 6. Post-Install Verification Checklist
Technical Health Check
- Confirm all required Tunnel Services show ONLINE on the Apium Dashboard (MS-SSTP, L2TP, strongSwan, sing-box/Xray).
- Verify real-time CPU, RAM, and channel load telemetry are updating.
Client & Routing Verification
- Create a test account, verify quota/speed limits, and test connectivity from your target client (app, Windows SSTP, or MikroTik/Keenetic).
- If using Upstream Relay, verify 15s health probes pass for your country exit nodes.