Most common

Business Site

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

What this tier is

The difference between a static site and a business site is usually a contact form, an editor who is not a developer, and a database. This tier carries all three: an application runtime, a managed database schema on our data tier, and SMTP credentials so form submissions and notifications leave the building.

It includes a staging hostname on our domain. Point a browser at it, confirm the change, then promote. That single habit prevents most of the incidents we see on sites at this size.

Specification

Business Site specification
RuntimePHP-FPM or Node, selected at provisioning
Memory1 GB application memory
Storage10 GB application and media
DatabaseManaged MariaDB or PostgreSQL schema, 5 GB
Outbound mailAuthenticated SMTP relay credentials
EnvironmentsProduction plus staging hostname
BackupsDaily database dump and filesystem snapshot, 14-day retention
Domains2 primary plus subdomain aliases

What is included

  • PHP-FPM or Node application runtime, your choice at provisioning
  • Managed MariaDB or PostgreSQL schema included in the price
  • Authenticated SMTP relay credentials for outbound form mail
  • Staging hostname with the same runtime as production
  • Managed TLS, canonical hostname policy, and redirect handling
  • Daily database backup plus daily filesystem snapshot
  • Two domains plus subdomain aliases

Typical use cases

  • A small business site with a contact form and an editable page or two
  • A content platform where non-developers publish
  • A brochure site with a booking, quote, or enquiry workflow
  • A site being migrated off shared hosting that never quite worked

Responsibility split

Written down so there is no argument about it later.

We handle

  • Runtime installation, patching, and version upgrades
  • Database provisioning, credentials, backup, and restore
  • TLS, routing, staging hostname, and outbound mail authentication
  • Capacity monitoring and resource limit enforcement

You handle

  • Your application code, theme, or CMS and its plugins
  • Content, editorial workflow, and user accounts inside the application
  • Testing on staging before asking us to promote

How provisioning works

Operator-provisioned. We confirm runtime choice and database engine by email, stand up production and staging together, and hand over credentials once both respond correctly. Typical turnaround is one business day.

Order

Billing period

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

Leave blank if you want us to suggest one.

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

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

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

$79 /mo

  • Up to eight sites under one account and one invoice
  • Shared staging conventions and deploy tooling across the portfolio
  • Quarterly review of certificate, DNS, and dependency health

View details