More control.
Room to build.

Your VPS includes a browser-based Control Panel for the server tasks you need most: power controls, built-in firewall management, OS reinstalls, console access, supported password resets, server information, resource statistics and operation tracking. Optional paid backup plans add on-demand recovery points and, on eligible plans, automatic backup scheduling.

Open your service in the Control Panel to find the tools available for that server. You can handle common management tasks without opening a support ticket, while keeping your application configuration and software administration under your control.

Start with the requirements of the applications you want to run. Compare CPU, RAM, storage and monthly transfer together, then check the location, operating-system options and features shown for the plan. A website, database, game server and development environment can have very different resource needs.

Allow room for ordinary growth and decide who will maintain the software. If you need recovery points, include a paid backup plan in your budget. Tell us about your workload, current usage and expected audience if you would like help comparing the available server configurations.

Our listed VPS locations are Sydney in Australia, Montreal in Canada, London in the United Kingdom and Virginia in the United States. Choose a location in the server filters to see the configurations currently available there. Availability and feature choices can vary by plan and location.

Hosting closer to your main audience can help reduce the distance traffic travels. Consider where your customers, staff and connected services are located, along with your application and business requirements. Contact us before ordering if you need a particular location or are planning a move between countries.

Standard VPS orders enter automatic provisioning after payment verification and order approval. The service is then prepared with its selected resources, operating system and network settings. You can follow the actual work in Job Status and use your welcome email and service details when the server is ready.

An accepted order and a fully prepared operating system are different stages. Image installation, custom requests or additional verification can require extra time. Once provisioning completes, plan any application installation, DNS changes and migration checks needed before directing customers to the new server.

Yes. The service dashboard provides power controls for starting the VPS, requesting a graceful shutdown and rebooting, with a stop control available where appropriate. The controls reflect the server state and the actions currently available to your service, so routine power management can be handled from your browser.

Use a graceful shutdown or normal reboot when possible so the operating system can close applications and finish writes. A force stop is closer to disconnecting the power and can interrupt unsaved work. Check Job Status for a queued request rather than submitting the same action repeatedly.

The Console action opens your VPS display and keyboard session in a separate browser window. It gives you another way to reach the operating system without relying on an SSH or Remote Desktop connection into the guest. Access is launched through your authenticated service page.

Use it to inspect the login screen, watch the server start, or troubleshoot a configuration problem from the server itself. The console is particularly useful during maintenance and recovery. Your VPS must be in a usable state for the task, and you will still need the appropriate operating-system login.

Yes. If the VPS is running and console access is available, the browser console can help you investigate guest networking, an operating-system firewall, a stopped service or a login problem even when your usual remote connection is unavailable. You can inspect the server directly and work through the cause.

A console connection does not automatically fix an application or override account restrictions. Keep a known recovery route before changing network settings, and distinguish the built-in VPS firewall from any firewall configured inside the operating system. Contact support if the VM or console itself is unavailable.

Open Server Information for your service to review its hostname, assigned addresses and resource details. The page includes the saved service username and password where available, with controls to reveal or copy the password after you sign in. Use the username shown for your selected image.

Your VPS login is separate from your Control Panel account. Keep both private, limit who can administer the service and use a secure way to share credentials when access is necessary. If you reset or restore the server, check which saved credentials apply before trying to reconnect.

Yes, on supported services the Reset Password action updates the server login without replacing the operating system or rebuilding the VPS. The supported Linux workflow resets the vpsuser account: you can enter a new password or let the panel generate one, then check the saved service credentials after completion.

Start the server before requesting the reset. The operation depends on the supported image and management connection inside the guest, so it may be unavailable if those components are not working. It changes the operating-system login handled by that workflow, rather than passwords for every application hosted on the VPS.

Yes. The Firewall area lets you manage customer traffic rules for your VPS from the same Control Panel as your other server tools. You can review incoming and outgoing traffic policies, add rules and see whether saved changes are pending or have been applied to the VM.

This makes it easier to expose the services your business needs and restrict access to administration ports. It works alongside the operating system and application security you configure inside the VPS. Provider network protections remain in place independently of your customer rules.

Create named inbound or outbound rules, choose the traffic action, and match supported protocols, IP addresses or networks and ports. Rules can be enabled, disabled, edited and reordered; the first matching rule determines the action. You can also select a VM interface and configure the default action for unmatched traffic.

For example, you could allow public access to your website while limiting an administration port to trusted source addresses. The page provides rule search and filters, supported logging options and a JSON export of customer rules and default policies. Review the match conditions carefully before saving a restrictive policy.

Firewall changes are saved and queued for application. The page distinguishes pending changes from settings applied to the VM, and the current interface notes that application can take up to 60 seconds. Check that status before assuming a newly saved rule is already controlling traffic.

Add and verify the allow rules you need before blocking unmatched traffic. Include administration access and the services your customers use, and consider both IPv4 and IPv6 where relevant. Keep console access available while testing changes so you have a way to investigate an accidental loss of remote access.

You can pause and resume your customer firewall rules while keeping the saved rule set and default policies. Pausing is itself a queued change: when applied, customer rules stop matching and unmatched traffic is allowed until you resume them. This is useful for controlled troubleshooting, with the wider access implications kept in mind.

Provider protections are separate. Customer actions do not remove provider-managed SMTP restrictions or IP/MAC filtering. If your workload requires a network exception, discuss it with support; adding a customer allow rule does not override those provider settings.

VPS backups are an optional paid add-on. Choose an available backup plan to enable the recovery features for your service. Manual backups let you request a recovery point when you need one; automatic scheduling requires a backup plan that specifically includes automation.

The available choices and fees are shown with the service options or can be confirmed with our team. Your selected plan determines the backup allowance, retention and scheduling entitlement. Server-management tools and access to the Backups page do not mean that a free or unlimited backup service is included.

With an eligible paid backup plan enabled, open Backups and choose Create backup. You can add a short description, such as “Before application upgrade,” to identify the recovery point later. Submit the request and follow its progress until a completed backup appears in Saved backups.

A manual recovery point is useful before software updates, configuration changes or other planned maintenance. Confirm completion before beginning a destructive operation. Current activity, storage availability, cooldowns and the purchased backup policy can affect when another request can be accepted or processed.

Yes, when your paid backup plan includes automatic backups. In Automatic backups, enable a schedule and choose every day, selected weekdays or selected dates each month. Set the local time, timezone and start date, with an optional end date for a schedule that should finish automatically.

The panel shows the next scheduled request and the latest scheduled result. Timezone handling follows daylight saving changes, and monthly dates that do not exist are skipped. Schedule around your maintenance and business activity, then review completed recovery points rather than relying only on the presence of a saved schedule.

Yes. Pausing the automatic schedule stops future scheduled requests while retaining the saved settings for later use. A backup already in progress may still finish. On a plan with the relevant entitlements, manual backup requests remain available independently of whether the automatic schedule is enabled.

This can be useful during a planned migration or a temporary maintenance period. Remember to resume the schedule when appropriate and check its next request and latest result. Service status, plan changes and backup availability can also affect scheduling, so review the Backups page after changing your service.

Your paid backup plan determines the retained backup count and any age limits or request cooldowns. Manual and automatic recovery points share the service’s retention allowance. The Backups page shows the applicable allowance so you can choose a plan around the history your business needs.

Retention can remove older recovery points after a new backup succeeds, subject to the configured policy and protection settings. Treat this as a rolling recovery history rather than permanent archival storage. Keep separate copies of important application data and review your requirements before reducing the backup plan.

Open Saved backups, choose the completed recovery point you need and review the overwrite confirmation before selecting Restore. The operation is tracked through Job Status. Use the date and description to make sure you have chosen the right point for the incident or maintenance change you are recovering from.

A restore replaces current server data and restores the password saved with that backup. Changes made after the recovery point can be lost, and the service is interrupted while restoration takes place. After completion, check the saved login, applications and important business workflows before considering recovery finished.

Server recovery points are valuable when you need to recover the VPS, but their usefulness depends on when they completed and how your applications store data. A database, online shop or other busy service may also need application-aware exports or its own backup procedure to meet your recovery needs.

Combine the paid server backup option with a sensible application backup and verification routine. Decide how much recent work you can afford to lose and how quickly the service needs to return. Test recovery carefully and keep important copies separate instead of treating any single backup system as a complete business-continuity plan.

Yes. Reinstall OS lets you choose an available, compatible operating-system image and submit the rebuild from your service page. This is useful when starting a new project, replacing a damaged installation or returning to a clean environment without ordering another server.

Reinstalling erases existing VM disks, snapshots and data. Save anything you need first and confirm that any required backup has completed. The panel asks you to acknowledge the destructive change, then Job Status shows progress while the server is prepared with the selected image.

The supported reinstall workflow keeps the service’s hostname, location and assigned IP addresses while replacing the operating system. A new server login password is generated and saved with the service details. Your applications and files from the previous installation are not carried into the fresh environment.

Choose from the images offered for your exact plan. An image may require a compatible package or a billing upgrade, so availability is checked before installation. Review the new system’s requirements and check the resulting credentials and network access once the reinstall has finished.

Compatible upgrades can be requested through the service’s available upgrade options. Review the selected package or add-on pricing before ordering, then follow the server change in Job Status. This lets you plan growth around your workload rather than moving to a different product without first checking the available upgrade path.

Supported package changes can retain the server’s data and addresses, but resource changes may require a shutdown and restart. Virtual disks can be expanded on a supported upgrade; shrinking is not supported, and the guest filesystem may need its own expansion step. Check compatibility and follow Job Status before assuming a paid upgrade has finished applying.

Server Information lists the network addresses assigned to your VPS, including additional addresses where configured. On eligible services, extra public or internal IPv4 quantities can be selected through the available paid service options. The choices depend on the plan, location and available network resources.

Private networking can help separate supported internal service traffic from public-facing access, but connectivity and configuration depend on the environment supplied. Discuss your application and routing requirements before ordering. Additional addresses do not remove provider security controls, and moving between locations is a separate migration decision.

Statistics provides server-level graphs for CPU usage, memory usage, network traffic and disk I/O. You can choose daily, weekly, monthly or yearly views to review trends rather than relying on a single moment’s reading. New servers may need time to collect useful history.

Use these graphs to spot sustained resource pressure and to help decide whether a configuration or plan change is appropriate. They describe the virtual server’s resources; they do not replace application logs, website analytics or independent availability monitoring. Check those alongside the panel when investigating a performance problem.

Open Job Status from your service’s Actions menu to see recent requests and their saved progress. The panel describes stages such as preparing the operating system, setting up the network, creating a backup or restoring data, then shows the completed outcome or a message if attention is required.

Accepted work continues in the background after you leave the page. Return to check progress instead of repeatedly submitting the same operation. If a request fails or remains pending, read its message and contact support with the service and operation details before retrying an action that could overwrite data.

Common server-management tasks are available through browser forms: power actions, supported password resets, firewall rules, OS reinstalls, backups and progress checks. You can manage those parts of the service without constructing API requests or running the same administrative commands manually.

Installing applications, maintaining the operating system and diagnosing software inside the VPS may still require SSH, Remote Desktop or another application-management tool. If you mainly need a website and would prefer to work through cPanel, compare our web hosting plans as well as the VPS options.

The Control Panel gives you self-service tools for managing the virtual server and its recovery and network settings. It makes routine infrastructure tasks more accessible, but it does not automatically mean that our team maintains every application, database, plugin or custom component you install.

Plan who will handle software updates, access, configuration, application backups and monitoring. If you need ongoing administration or help with a particular workload, discuss the scope with us before ordering so the service and any additional assistance match your business requirements.

They serve different purposes. The VPS Control Panel manages the server itself: its lifecycle, console, firewall, supported recovery tasks and resource information. cPanel is separate software for managing websites, domains, email and databases inside a compatible hosting environment.

You do not need to buy cPanel just to use the included VPS server-management tools. If you want cPanel for hosting websites on your VPS, check the compatible operating system and available paid licence options. Installing a control panel also brings its own software and maintenance requirements.

Check the Windows badge and the operating-system choices offered for the exact VPS plan before ordering. Compatible plans can offer Windows options, but a Windows licence is not included in the listed server price. Confirm the licensing requirements for your intended use and the image supplied.

Available guest-management functions can vary by operating system and image. Features described for a supported Linux workflow, such as resetting its service account, should not be assumed to work identically on Windows. Contact us if your application requires a particular Windows version or management feature.

Discuss the email workload and our service policies before choosing a server. Outbound SMTP on port 25 is provider-managed, and customer firewall rules cannot remove that restriction. Contact support if the application needs that access rather than assuming a new VPS includes unrestricted mail delivery.

Many applications can use a suitable external email-delivery service under its supported configuration. Whichever approach you choose, plan domain authentication, access security and ongoing maintenance. Running an email server also involves delivery and reputation responsibilities beyond having a server IP address.

Make an inventory of website files, databases, application versions, scheduled tasks, email services, DNS records and external integrations. Check the new plan and operating-system requirements, then prepare the application and test it before changing the addresses your customers use.

Set up firewall access, administrator credentials and a recovery plan early. Consider a paid backup option and keep a separate copy of important data, with the old service available during the planned cutover. Contact us to discuss migration scope and any fees before making changes to a live business service.