Linux virtual machines on Cloud EA
Cloud & VPS

Cloud & VPS
servers you can actually manage.

Patolink provides virtual private servers and cloud infrastructure through Cloud EA.

Services / Cloud & VPS

What this service is

Cloud & VPS is the Patolink service line for virtual private servers and cloud infrastructure delivered through Cloud EA. Customers choose a plan by the resources they need: vCPU, RAM, storage, operating system, IP addresses, bandwidth, backup, and billing cycle.

The published Linux packages are Starter, Growth, Pro, Enterprise, Apex, and Custom. Pro is the default for a real application stack. Apex is the published best-value step when you already know you will fill the memory. Custom is the quote when none of those shapes fit.

A Cloud EA VPS is also a product: a named plan with a billing cycle. This service page is the practice around it — design, order, provision, and the option to retain the estate under Managed Services. You can buy the VM alone, or the VM plus a retainer.

Provisioning and payments are platform capabilities. They are not sold as their own customer-facing service. The hypervisor stays on the backend. Write to Nairobi if the public cards are the wrong shape: info@patolink.com · +254 709 343 000.

Who typically buys it

  • —A first project, staging box, or low-traffic site that should not wait three weeks for hardware.
  • —A 3CX or Yeastar host that should not live in a cupboard.
  • —An application stack that already knows it will need 8 GB or more.
  • —A custom specification when the public cards are the wrong shape.

What a VPS plan can include

vCPU / CPU cores

The number of virtual cores allocated to the instance — 2 through 6 on the published matrix, or a custom count.

RAM

Allocated server memory, from 2 GB on Starter to 32 GB on Apex.

Storage

Allocated virtual disk — SSD on the published matrix, from 100 GB to 700 GB.

Operating system

Ubuntu 24.04 LTS or Debian 12 on published plans. Further images when we publish them.

IP address allocation

Public or private addresses where the plan includes them.

Bandwidth

Network and traffic allowance for the instance.

Backup options

Daily backups are included on published plans; extra retention can be quoted.

Billing cycle

Monthly on the public cards. Quarterly, annual, or another cycle when configured.

How an order runs

  1. Step 01

    Select the plan

    Choose a published Linux plan or ask for Custom. Pick Ubuntu 24.04 LTS or Debian 12.

  2. Step 02

    Account and invoice

    Create or sign into a Patolink account. An order and invoice are raised for the plan and cycle you chose.

  3. Step 03

    Pay, then provision

    After payment is verified, the backend creates the instance, applies CPU, RAM, storage, networking, and the OS, and starts the server.

  4. Step 04

    Credentials and portal

    Credentials are issued securely. Email — and WhatsApp where configured — tells you it is up. The instance appears in the customer portal.

What sits on the order

The public Linux matrix is the exception on this site: those monthly KES figures are published. Custom work and retainers are still quoted.

edit_note

The plan

Starter through Apex with published resources and price, or Custom on request.

edit_note

Operating system

Ubuntu 24.04 LTS or Debian 12, plus any extra resource the plan allows.

edit_note

Managed retainer

Optional. Patching, hardening, and a named on-call sit on Managed Services — they are not automatic with the VM.

edit_note

Other products

A 3CX, Yeastar, Sophos, or Microsoft licence on the same quotation stays on its own line.

What you can do in the portal

View servers and status. Start, stop, and reboot. Read assigned IPs, CPU, RAM, storage, operating system, specifications, billing, and renewals. Only the management actions the platform exposes securely are available.

This website never talks to the hypervisor directly. You see the plan, the invoice, and the credentials. Service levels — including the 99.9% monthly availability target, daily backups, and credits — are published on the SLA.

What is not on the VM line

Managed patching, hardening, and a named on-call are not automatic. Those sit on a managed-services retainer if you do not want to operate the instance yourself.

A Sophos, 3CX, or Microsoft licence is a separate product when the VM is only the host. Three catalogue lines, one project, readable renewals. Acceptable use of the infrastructure is published on the AUP.

Related

Start with a VPS plan

Review the Cloud EA plans, or write to Nairobi if you need a specification that is not on the public matrix.