Skip to content

Self-hosted server management made clearer

Run websites and services on your own physical or virtual server. Dexlinkx gives a simpler control plane while your files stay on the machine.

Dexlinkx server dashboard showing server health, resources, quick actions and system status
Server status and resources together in the Dexlinkx portal.

Own the machine, simplify the control plane

Self-hosting means your workloads run on hardware or a VM you control. Dexlinkx helps with installation, pairing and day-to-day management through a web portal.

It is not a managed hosting provider that stores your site files in Dexlinkx cloud storage.

Typical uses

Personal servers, home labs, project and staging environments, and small self-hosted websites built with static sites, PHP, WordPress or Laravel.

You can still use SSH and install software outside Dexlinkx-managed paths.

Where Dexlinkx helps

Guided install via Dexlinkx Manager, status and resource views, website and database workflows in the managed area, and permitted system actions based on the access profile.

Prepare and verify your server

Begin with a supported host, independent recovery access and a small test workload. Confirm status in the portal before adding more services.

  1. Plan the host

    Choose a dedicated machine or VM and check compatibility in the current beta instructions. Back up existing data before installation.

  2. Install and connect

    Add the server, follow Dexlinkx Manager and confirm that the intended host connects.

  3. Review the access profile

    Check which actions the portal may perform and use the least access needed for the workload.

  4. Test one workload

    Create a small website or supported service, verify connectivity and resource use, and rehearse recovery.

Keep responsibilities clear

Use the portal for supported website, database, application and status workflows. Host operating-system maintenance, network exposure and a tested backup plan still need an owner.

Check what each available action covers before relying on it. A service restart is not a recovery plan, and an online status does not prove that every application is healthy.

  • Review disk space, resource use and relevant application logs.
  • Keep backups separate from the host and verify restoration.
  • Test changes before applying them to important workloads.
  • Keep local or SSH access available if portal connectivity is interrupted.

Realistic expectations

  • You are responsible for the host OS, network exposure and backups outside what Dexlinkx manages.
  • Beta access is staged; not every advanced automation feature is available on every profile.

Apply for the closed beta

Apply for access and install your first server with Dexlinkx Manager once approved.