SaaS marketing site hosting where a leaked form is a lost deal.
Your marketing site is a lead capture surface with an A/B test running on it. The two things that must never fail are the form reaching your CRM and the cache not serving the wrong variant to everybody.
Everything a demand-gen site asks of a host.
This site's job is measured in submitted forms. Everything below is about not losing one and not corrupting the experiment measuring them.
A/B tests that do not poison the cache
Experiment assignment is part of the cache key rather than something that happens after the page is served, so a visitor in variant B never receives a cached copy of variant A.
Form submissions that reach the CRM
Posts to your CRM are queued and retried rather than fired once and forgotten, so a momentary API failure at their end does not become a lead that never existed.
Launch day at edge speed
Pages serve from 14 edge regions, so a post that reaches the front page of somewhere does not turn your origin into the bottleneck during the one hour it mattered.
Staging that matches production
Rebuild a pricing page or trial a new hero on a clone, then push it live. Marketing changes stop being deployments you schedule around.
Backups before every campaign
Daily snapshots replicated off the origin, plus a restore you can run yourself when a last-minute change to the pricing page went the wrong way.
Protect the number you report on.
For this site the failure that matters is not downtime — it is a week of experiment data that turned out to be contaminated, or a form that was quietly failing.
- One-click admin login, no shared passwords
- CRM delivery failures surfaced, not silent
- Plugin and core updates with per-item status
- Restore any daily backup from the dashboard
The page a paid click lands on.
Every visitor here arrived from an ad, a search result or a launch post. The page has one chance and it is being measured against its own bounce rate.
What we change for a SaaS marketing site
These differ from a standard marketing site on the same plan, because this one is simultaneously a cached brochure and a measured experiment.
| Setting | What we do | Why |
|---|---|---|
| Experiment cache key | Variant assignment included in the cache key and resolved at the edge | Assigning a variant in the browser after a cached page has already been delivered means the visitor briefly sees one version and is counted in another, which quietly invalidates the test rather than breaking it visibly. |
| CRM form delivery | Submissions queued locally and retried against the CRM API | A form that posts straight through loses the lead entirely whenever the CRM is briefly unavailable, and nothing in the site's own records shows that the submission ever happened. |
| Edge cache lifetime | Long-lived at the edge with instant purge on publish | Marketing pages change rarely but must change immediately when they do, so a short lifetime spends origin capacity continuously to solve a problem that a purge solves at the moment of publication. |
| Tracking script loading | Analytics and ad tags deferred behind the page's own render | The page is judged on how fast it paints for someone who arrived on a paid click, and third-party tags are the largest thing on it that the visitor did not ask for. |
| Documentation subpaths | Routed separately so docs traffic does not share the marketing cache policy | Docs are read by existing customers, updated far more often and searched rather than browsed, so applying the marketing site's caching to them serves stale answers to the people least tolerant of them. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can I run A/B tests without breaking the cache?
What happens if my CRM is down when someone submits a form?
Will the site hold up if we get on the front page of somewhere?
Should our docs live on the same site?
Do analytics tags slow the landing page down?
Run a marketing site that never loses a lead.
Free migration, experiments that stay clean, and forms that reach your CRM.