Skip to content
comark

VPS with reserved resources and root access.

For online stores, web applications and systems that need resources and software of their own. You get a virtual server with root access. We set it up, and you decide which layers we run: patches, backups, monitoring, or all of them.

Root access
Always yours
Management
Add-ons, server by server
Sample VPS panel: four vCPUs, 8 GB of memory and 160 GB of disk with current use, a root shell showing Nginx running, and who runs each layer on this server: hardware, patches and backups by Comark, monitoring and application support by the client's team.

Four tiers

The question isn't where it runs. It's who is responsible for it.

A VPS is the step where the server becomes yours: we always run the hardware, and you choose which other layers we take on.

Shared hosting

Business sites

Hardware and networkData centre, power, network
Comark
OS and security patchesInstall, hardening, updates
Comark
Backups and restore testsOff-site copies, restores proved
Comark
Monitoring and alertsUptime, resources, security events
Comark
Scaling and high availabilityCapacity, load balancing, replicas
Add-on
Application supportUpdates and fixes to your code
Add-on

VPS

Apps and stores

Hardware and networkData centre, power, network
Comark
OS and security patchesInstall, hardening, updates
Add-on
Backups and restore testsOff-site copies, restores proved
Add-on
Monitoring and alertsUptime, resources, security events
Add-on
Scaling and high availabilityCapacity, load balancing, replicas
Add-on
Application supportUpdates and fixes to your code
Add-on

Dedicated

High traffic

Hardware and networkData centre, power, network
Comark
OS and security patchesInstall, hardening, updates
Comark
Backups and restore testsOff-site copies, restores proved
Add-on
Monitoring and alertsUptime, resources, security events
Comark
Scaling and high availabilityCapacity, load balancing, replicas
Add-on
Application supportUpdates and fixes to your code
Add-on

Managed

Critical systems

Hardware and networkData centre, power, network
Comark
OS and security patchesInstall, hardening, updates
Comark
Backups and restore testsOff-site copies, restores proved
Comark
Monitoring and alertsUptime, resources, security events
Comark
Scaling and high availabilityCapacity, load balancing, replicas
Comark
Application supportUpdates and fixes to your code
Comark
  • Comark runs it
  • Optional add-on

The final split is written into each service agreement.

What you get

A server of your own, set up for the application on it.

A server of your own, set up for the application that will run on it.

  • Reserved resources

    vCPU, memory and disk allocated to your server, not shared with other accounts.

  • Root access

    Install what the application needs: workers, Redis, Node.js, scheduled jobs.

  • Server setup

    Linux, Nginx, PHP or Node.js, databases and the firewall, configured and documented.

  • Hardening

    SSH keys, firewall rules and access limits from day one, whoever runs it after.

  • Managed add-ons

    Patches, backups and monitoring run by us, chosen server by server.

  • Resizing

    More CPU, memory or disk when the load grows, usually with a short restart.

Reserved resources

vCPU, memory and disk allocated to your server, not shared with other accounts.

Root access

Install what the application needs: workers, Redis, Node.js, scheduled jobs.

Server setup

Linux, Nginx, PHP or Node.js, databases and the firewall, configured and documented.

Hardening

SSH keys, firewall rules and access limits from day one, whoever runs it after.

Managed add-ons

Patches, backups and monitoring run by us, chosen server by server.

Resizing

More CPU, memory or disk when the load grows, usually with a short restart.

Setup

How a VPS is set up.

From sizing to handover, with the configuration written down.

  1. Size it

    We look at the application, its traffic and its data, and choose CPU, memory and disk with room to grow.

  2. Build and harden

    Linux installed and patched, SSH keys, firewall and users set up, then the web server, runtime and databases.

  3. Deploy and test

    The application deployed, scheduled jobs and workers running, and a backup restored once to prove it works.

  4. Hand over or run

    You get root access and the documentation. Your team runs the server, or we take on the add-ons you chose.

Plans

Sized to the system, not to a price list.

Starting points for each tier. The final configuration and price follow a short technical review of what you run.

Tier 1

Shared hosting

For company sites and landing pages.

  • A tuned server we run
  • SSL and scheduled off-site backups
  • Uptime and security monitoring
  • Migration from your current host
Hosting

Tier 2

This page

VPS

For web apps, stores and APIs.

  • Reserved CPU, memory and disk
  • Root access, always yours
  • Initial setup and hardening
  • Patches, backups and monitoring as add-ons

Tier 3

Dedicated servers

For high-traffic platforms and heavy databases.

  • Whole machines for your workload
  • OS, patching and hardening by us
  • Monitoring and alerts on every server
  • Backups and a recovery plan as options
Dedicated infrastructure

Tier 4

Managed infrastructure

For systems your business can't run without.

  • Architecture designed with you
  • High availability where the workload needs it
  • A tested recovery plan, when it is in scope
  • Every layer run by us, including the application
Dedicated infrastructure

01 / 04 · swipe

No prices on this page: we quote after a short technical review. Hosting for systems we build can be bundled with a managed website plan.

What is the difference between your hosting and a VPS?

On hosting, your site has an account on a server shared with other sites, and we run everything on it. A VPS is a server of its own, with reserved resources and root access, so it can run software a hosting account cannot. Our guide “Shared hosting, VPS or dedicated” on our blog compares them side by side.

Managed or self-managed: which should we choose?

If someone on your team patches servers, watches alerts and tests restores, self-managed works. If not, take at least patches, backups and monitoring as add-ons, because those are the three that get skipped when nobody owns them.

Do we keep root access if you manage the server?

Yes, root access stays with you either way. On a managed server we agree how changes are made, so our patches and your changes don't step on each other.

What happens when we outgrow the VPS?

We resize it, usually with a short restart. When the load needs more than one server, or the database needs a machine of its own, the next step is dedicated infrastructure with replicas and failover.

Can you move our application from another provider?

Yes. We build the new server, deploy and test the application on it, and switch DNS once it works. The database is copied last, so records written during the move are not lost.

Infrastructure review

Tell us what you run today. We'll tell you which tier fits.

An engineer reviews your setup and recommends a tier, including when you don't need to move at all.

In the review

  1. Current setup: servers, traffic, databases and backups today
  2. Risks we see: single points of failure, untested restores, outdated software
  3. Recommendation: tier, architecture and a migration plan if one is needed