The documents our clients actually use — launch, migration, hardening and the API.
Kick-off to DNS cut-over in six steps, including the content checklist that decides whether the project slips.
12 pages · PDFMoving an existing site to our hosting without breaking search rankings or losing form submissions.
8 pages · PDFHeaders, TLS settings, WAF rules and the five mistakes we find on almost every inherited site.
10 pages · PDFHow we set a Core Web Vitals budget before design starts, and what happens when a page exceeds it.
6 pages · PDFDeploys, cache purge, form submissions and uptime data. Token auth, JSON, no SDK required.
Web · OpenAPIHosting uptime, response targets and credit schedule, in one page.
1 page · WebWe list every page, who owns the copy, and which products need structured data. This is the week that decides the timeline.
Templates, CMS model, forms and integrations. You review on a staging URL that is behind a password, not a screenshot deck.
Core Web Vitals, keyboard navigation, contrast. Anything over budget is fixed before launch, not after.
Scheduled in a window you choose. Old site stays reachable until the new one answers correctly from three regions.
Thirty days of daily monitoring, form-delivery checks and a shared channel with the engineer who built it.
Clients can also raise requests in the client portal.