For teams whose first problem is speed and cost. Delivery done properly, with the security controls present but not yet the point.
INCLUDED
Best fit: content-heavy sites, marketing estates, early-stage platforms with predictable traffic.
Get an Edge quoteThe default for anything with a login page, a payment flow or a public API. Protection sits inline, and someone is awake when it fires.
EVERYTHING IN EDGE, PLUS
Best fit: SaaS, commerce, media, regional gaming, anything with a public API surface.
Get a Shield quoteFor estates where an incident is a board matter. Behavioural bot management, a security operations engagement of your own, and named people you can call.
EVERYTHING IN SHIELD, PLUS
Best fit: financial services, large-scale gaming, regulated platforms, anyone with a named adversary.
Get a Command quoteThis will not price your estate. It will tell you which package we would open the conversation with, and why, in about fifteen seconds.
The business scenario each capability actually addresses, next to the package that carries it.
| Capability | Edge | Shield | Command |
|---|---|---|---|
| CDN delivery & tiered cachingCuts origin load and page weight cost | Included | Included | Included |
| Managed DNS & TLS automationRemoves the two most common self-inflicted outages | Included | Included | Included |
| Origin shieldingKeeps a cold cache from taking down your origin | Included | Included | Included |
| Pulse observabilityAnswers "is it us or the network" without a war room | Standard | Extended | Full + custom |
| Multi-CDN route selectionRoutes around a degraded provider before users notice | Not included | Included | Included |
| L3/L4 DDoS absorptionSurvives volumetric floods without an origin outage | Not included | Always on | Always on |
| Managed WAFBlocks known application exploits at ingress | Not included | Included | Custom rules |
| Rate limiting & challengeContains credential stuffing and scraping | Not included | Standard | Adaptive |
| Behavioural bot managementSeparates sophisticated automation from real customers | Not included | Not included | Included |
| Sentinel SOC, named analystsSomeone accountable owns the incident, not a queue | Not included | Not included | Included |
| Edge computeMoves auth, rewrites and personalisation off the origin | Not included | Limited | Unrestricted |
| Incident response targetHow long before a human is on it | Business hours | 15 min, 24/7 | 5 min, 24/7 |
| Residency controlsKeeps regulated traffic inside a jurisdiction | Not included | Regional | Enforced in routing |
| Audit retention & evidence packsSurvives an audit or a regulator's question | 90 days | 13 months | Up to 7 years |
| Quarterly review & tabletopFinds the gap before an attacker does | Not included | Not included | Included |
Response targets and retention windows are the current draft commercial position. Confirm against signed service terms before publication.
Mid-incident takeover with a fixed engagement fee, convertible to a package afterwards.
Dedicated capacity in named facilities where public edge coverage is not enough.
Procurement, landing zones, migration and cost engineering as a separate workstream.
Questionnaire responses, control mapping and evidence assembly for your audit cycle.
Because the honest number depends on request volume, egress, cache behaviour, how many origins you have and how much of the security work you want us to own. A list price would either be padded to cover the worst case or quietly renegotiated later. We would rather quote from a week of your logs and stand behind it.
No, and we usually recommend you do not. Meridian sits above your existing providers and steers traffic between them. Keeping two networks under contract preserves your commercial leverage and gives us somewhere to route when one of them has a bad day.
You reach an on-call engineer directly. They will ask for DNS control or a prefix announcement, stand anycast ingress up in front of your origin, and absorb volumetric traffic first so the telemetry becomes readable. Application rules follow. You get a written report afterwards whether or not you become a customer.
Upward, at any time, prorated. Downward at renewal. We would rather you moved up because your traffic changed than sat on an oversized package because the paperwork was annoying.
You do. Logs are exportable in full for the whole retention window, and any custom rules written for your estate leave with you. We are not interested in holding your data as a switching cost.
Mechanically: no scrubbing detour, one dataset, and an analyst who can change the edge configuration without opening a ticket with a third party. Commercially: one contract and one escalation path, so an incident cannot become a dispute about whose SLA applies.
No obligation, no sales sequence. You get a recommended package, the configuration we would run and a price we will hold.