Skip to content
comark

Dedicated servers we run, with HA and DR where needed.

For high-traffic sites and systems the business depends on. Servers of your own that we set up, harden, monitor and run. Where the workload needs it, we add load balancing, database replicas, backups and a recovery plan, scoped in the proposal.

High availability and DR
Designed in where needed
Servers we manage
40+
Sample dedicated fleet: a load balancer, two application servers, a PostgreSQL primary and replica and a Redis cache, with CPU, memory and disk use and last night's backups. The replica's disk is at 81 percent, with a cleanup scheduled.

Four tiers

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

Dedicated servers are ours to run from the hardware to the operating system and monitoring. Backups, high availability and application support are added when the workload needs them.

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 we build and run

Servers first. The rest when the workload needs it.

Every setup starts with the servers. The other parts are added when the workload needs them, and scoped in the proposal.

  • Dedicated servers

    Whole machines for your workload, with predictable CPU, memory and disk.

  • Load balancing

    Nginx in front of two or more application servers, when one server is not enough.

  • Database replicas

    MySQL or PostgreSQL with a replica for reads and failover, where downtime is costly.

  • Caching and queues

    Redis for sessions, cache and background jobs, sized for the traffic.

  • Cloudflare in front

    CDN, WAF, SSL and DNS ahead of every request that reaches the servers.

  • Backups and DR

    Off-site backups, verified restores and a written recovery plan, when they are in scope.

Dedicated servers

Whole machines for your workload, with predictable CPU, memory and disk.

Load balancing

Nginx in front of two or more application servers, when one server is not enough.

Database replicas

MySQL or PostgreSQL with a replica for reads and failover, where downtime is costly.

Caching and queues

Redis for sessions, cache and background jobs, sized for the traffic.

Cloudflare in front

CDN, WAF, SSL and DNS ahead of every request that reaches the servers.

Backups and DR

Off-site backups, verified restores and a written recovery plan, when they are in scope.

High availability

No single point of failure, where the workload needs it.

A typical setup for a system where one failed server would stop sales or operations. Which of these parts a system needs is agreed at the architecture stage and written into the proposal.

Example high-availability setup: users reach a load-balancer pair through Cloudflare, traffic is spread over three application servers that share a Redis cache, the primary database streams to a replica, and backups are stored off-site and restored on a separate server to test them. Monitoring runs on every node.

How we build it

Designed on paper, built, tested, then run.

Designed on paper, built and load tested, then run.

  1. Architecture

    We map traffic, data and what must keep working if a server fails, and agree with you which HA and DR parts the setup needs.

  2. Build and load test

    Servers provisioned and hardened, the application deployed, then load tested against the busiest traffic you expect.

  3. Failover and recovery tests

    Where HA and DR are in scope, we stop servers on purpose, promote a replica and restore from backup, and write down every step.

  4. Run and review

    Monitoring, patches and capacity reviews continue. On setups with a DR plan, recovery tests are repeated so the plan stays current.

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

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
VPS

Tier 3

This page

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

Tier 4

This page

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

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.

FAQ

Questions about dedicated infrastructure.

When does a business need dedicated infrastructure rather than a VPS?

When traffic is high most of the time, the database is large or busy, one server going down would stop sales or operations, or isolation is a requirement. Our guide “Shared hosting, VPS or dedicated” on our blog covers the signs in more detail.

What does high availability mean in practice?

No single server whose failure takes the system down: two or more application servers behind a load balancer, a database replica that can be promoted, and backups off-site. It is not part of every setup. Which parts a system needs is decided with you at the architecture stage and written into the proposal.

Can you run all of it, including the application?

Yes. On a fully managed setup we run every layer, from the hardware to application support, and the engineers who answer for the servers also know the code. You can also keep the application with your own developers and have us run the infrastructure under it.

How do you know the recovery plan works?

When a DR plan is part of the setup, we run it: backups are restored to a separate server, replicas are promoted, and the steps and timings are written down. A recovery plan that has never been run is a guess.

Do you work to a security standard?

Yes. Comark is certified to ISO/IEC 27001, 27018 and 27019, and the infrastructure we run follows those processes: access control, encrypted communication and monitoring on every setup, and backups as agreed for each system.

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