Vloxt Guide

Ordering

Choose an active server plan, location, and compatible free Linux image or application. Current stock is checked before invoicing, after payment, and immediately before deployment. Payment never guarantees inventory. If a paid configuration becomes unavailable, Vloxt pauses deployment and asks you to approve an exact alternative or completes an unfulfilled-order payment correction.

Billing

Servers and add-ons are prepaid monthly. Renewal invoices are issued seven days before renewal and are due 24 hours before renewal. A missed due time does not shorten the paid term. Stopping a server does not stop billing. Cancellation ends service at the paid-term boundary.

Management and recovery

The client area shows only actions currently supported for your server. Reinstall, rebuild, destructive restore, SSH-key reinstall, and immediate destruction can erase data and require recent Authenticator verification plus typed confirmation. Keep independent recovery material and test restores.

Backups and snapshots

Automatic backups follow the schedule shown in the client area. Snapshots are customer-created point-in-time images and are not automatic backups. Add-ons activate only after their invoice settles and normally share the server renewal boundary.

Networking and credentials

Reverse DNS, additional addresses, network usage, and console access appear only when supported. Additional addresses have account and per-server limits. Initial service passwords may be revealed after recent Authenticator verification. Never send passwords or private SSH keys in tickets.

Applications and support

Applications installed on your server are managed by you. Vloxt tickets cover server and platform issues. Include the affected service, observed time, expected result, actual result, and safe reproduction details. Do not attach credentials.