Frequently asked questions.

You add USD wallet balance first. Orders, renewals, upgrades and some administrative charges are then debited from that balance. Services do not renew if there is not enough balance.

The platform is designed around prepaid wallet balance. Crypto top-ups are handled through the integrated payment flow and confirmation is credited to your wallet after confirmation.

The upgrade is charged pro-rata for the remaining time until the current renewal date. The next renewal uses the new package price.

The downgrade credits the pro-rata difference back to your prepaid wallet. If the new disk is smaller, the VPS must be rebuilt and data will be erased after explicit confirmation.

Downgrade credits and bonuses are wallet credits. External refunds require manual review and depend on the Terms of Service.

Most template-based VPS orders are processed automatically after payment, IP allocation and image selection are ready.

Yes. Available actions depend on the current state. During provisioning or rebuilds, actions are disabled until the change is complete.

Yes. Add SSH keys in your account and select them during provisioning. The selected key is reused for reinstall workflows.

Yes. You can upload custom ISOs up to your quota, wait for approval, then mount approved ISOs to your VPS and boot from them.

Yes. VPS service pages include a secure web console with short-lived console access.

Packages can include IPv4 addresses. Allocated IPs are tracked in IPAM and attached to your service.

No. VPS networking is protected with allocated-IP filtering so only IPs assigned to the service should pass traffic.

Customer packages are shown as unmetered at the configured package port speed unless a package explicitly states otherwise.

IP management workflows are available from the panel. Some changes may require admin approval depending on policy.

Dedicated packages are matched with available hardware inventory. Power and reinstall workflows may be automated or queued for datacenter handling.

Yes. Dedicated servers appear in the same services dashboard with billing, ticket, status and management information.

At the renewal date the platform tries to renew the service from your prepaid wallet. If the wallet balance is too low, the service is suspended and kept for a 3 day retention period. After that retention period the service is queued for automatic removal.

Yes, while the service is still inside the suspended retention window you can add funds and extend the service. Once it is queued for deletion or removed, recovery is not guaranteed.

No. Terminated, cancelled and removal-queued services are hidden from the customer dashboard and services list. Admins keep an audit trail for support and administration.

No. Customer views use public service references and customer-safe logs. Infrastructure-only details are hidden from customer-facing pages.

Console access is generated per session and only for services owned by the signed-in user. The console route uses the public service UUID and validates account ownership before access is granted.

Customer ISO files are stored outside direct public access, count toward the account ISO quota and require approval before they can be mounted to a VPS.

Use the contact page or create a ticket while logged in. Logged-in users can attach the request to their account and services.

The public status page shows active incidents, maintenance windows and latency graphs. Admins manage these from the admin panel.

Customer logs show clear service actions such as create, restart, reinstall, package change and billing updates. Low-level platform details are hidden from customer views.