Multi-site Portfolio

Several sites, one operator, one invoice, one set of conventions.

What this tier is

Running eight sites across four hosting providers is a filing problem before it is a technical one. Certificates expire on somebody else's schedule, DNS lives in registrars nobody can log into, and the person who set up the third one has left.

This tier consolidates that. Every site in the portfolio uses the same routing, the same certificate automation, the same staging convention, and the same backup policy. We send one invoice and one quarterly health report covering certificate expiry, DNS configuration, runtime versions, and anything drifting.

Specification

Multi-site Portfolio specification
Sites includedUp to 8, static or dynamic
Memory8 GB pooled across the portfolio
Storage80 GB pooled
DatabasesOne managed schema per dynamic site
EnvironmentsProduction plus staging per site
ReportingQuarterly written health review
BackupsDaily, 30-day retention, all sites
SupportNamed operator contact, priority scheduling

What is included

  • Up to eight sites, static or dynamic, mixed freely
  • Shared managed database tier with a schema per site
  • Staging hostname per site with a consistent naming convention
  • One invoice and one operator contact for the whole portfolio
  • Quarterly written health report on certificates, DNS, and runtime versions
  • Priority scheduling for maintenance windows across the portfolio
  • Site additions and removals handled without renegotiating the contract

Typical use cases

  • An agency hosting client sites it does not want to operate individually
  • A business with a main site plus product, campaign, and support sites
  • A group of related organisations sharing an administrator
  • Consolidating sites scattered across several legacy hosting accounts

Responsibility split

Written down so there is no argument about it later.

We handle

  • All infrastructure, TLS, routing, and backups across every site
  • Runtime patching and coordinated maintenance windows
  • Quarterly portfolio health review and written report
  • Adding and retiring sites within the included allowance

You handle

  • Site code, content, and client relationships
  • Domain registration, or delegating registrar access to us
  • Telling us which sites matter most when we schedule maintenance

How provisioning works

Operator-provisioned with a kickoff call. We inventory the existing sites, agree a migration order, and move them one at a time with a rehearsal each. Portfolios usually complete within two weeks depending on DNS control and site count.

Order

Billing period

We use this for the invoice, provisioning updates, and account sign-in.

Migration deadlines, existing stack, constraints.

Payment is handled by Stripe. We never see or store card details. Continuing means you accept the Terms, Acceptable Use Policy, and Privacy Policy.

Ask a question first

Other tiers in Web hosting and sites

Entry

Static Site

A published build, served fast, with certificates that renew themselves.

$9 /mo

  • Managed TLS and canonical hostname policy
  • Deploy from Git or an uploaded build artifact
  • Daily snapshot of the published tree

View details

Most common

Business Site

A dynamic site with a runtime, a database, and somebody watching it.

$24 /mo

  • PHP or Node runtime with a managed database included
  • Authenticated SMTP so contact forms deliver
  • Staging hostname for changes before they are public

View details

WordPress with the maintenance treated as the actual product.

$32 /mo

  • Core, theme, and plugin updates applied on a monthly window
  • Staging clone refreshed from production on request
  • Restore tested, not merely configured

View details