A public body's website is quiet until a storm, a closure or a deadline. On that day it is not a marketing asset, it is infrastructure.
Everything here answers to a duty rather than a funnel, and the failure modes are correspondingly different.
A weather event or a service closure sends an entire population to one notice at once. That page is served from the edge, so demand arriving in minutes does not take the site down.
Public information has retention obligations measured in years. Old pages and their versions stay online and backed up rather than being pruned to keep the install tidy.
Accessibility is a legal requirement here, not a preference. The platform adds no interstitials, overlays or injected scripts that would undo work your team has done to meet it.
Procurement asks where the data sits and who else can reach it, and needs the answer on paper rather than in a sales call.
Public bodies run dozens of sites across services and teams. They share a platform and stay separated, with roles that match who is responsible for what.
Commercial sites plan for campaigns. A public body plans for the day a road closes, a school shuts or a deadline falls, when the site is the only channel that scales.
The load pattern is not gradual growth. It is a single notice going from a hundred views a day to a hundred thousand in twenty minutes.
The requirements come from statute rather than from a growth plan, and the configuration follows them rather than a conversion rate.
| Setting | What we do | Why |
|---|---|---|
| Surge handling | Notice and alert pages pinned to the edge | Demand arrives when something has gone wrong in the real world, and it goes from nothing to everything inside twenty minutes on a single URL. |
| Retention | Content and versions kept for years by default | Public information carries statutory retention, so tidying an install by removing old pages destroys a record somebody is obliged to hold. |
| Injected assets | None added by the platform | Accessibility conformance is assessed on what the page actually renders, and a script the host adds can undo work a team was legally required to do. |
| Residency and access | Documented in writing for procurement | A public body has to record where data is held and who can reach it, and cannot accept an answer given verbally. |
| Multi-department separation | Sites isolated with roles per service | One authority runs dozens of sites owned by different teams, and a shared login model makes accountability impossible to establish afterwards. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the public site across — migration is free, archives included.