SaaS architecture guide

SaaS Edge Economics: Egress Cost, Availability and Compliance

Evaluate delivery as a combined cost, availability, tenant-isolation, and evidence problem. A lower origin bill can coexist with higher edge, replication, or observability spend.

Published: Jul 15, 2026
Updated: Jul 15, 2026
Reading time: 13 min read

On this page

There are no universal savings from caching, shielding, multi-region delivery, or an edge platform. SaaS teams need to measure real request paths and billing meters while preserving tenant isolation, write authority, and data-handling evidence.

Overview

Outcome

Create a route- and tenant-aware decision model that joins delivery cost, availability objectives, cache safety, origin protection, and residency evidence.

Attribute cost to a real unit of service

Classify traffic by route, service, region, cache outcome, response size, tenant or plan where appropriate, and data class. Directly allocate dedicated traffic; use a documented allocation policy for shared CDN, WAF, DNS, logs, and support costs. FOCUS provides a normalised vocabulary for cost, usage, account, region, resource, tag, and allocation data.

SaaS edge decision inputs

Request class
Public read, authenticated read, mutation, webhook, or administration is identified.
Data authority
Tenant, region, write owner, and permissible cache state are declared.
Delivery controls
Cache, rate, routing, shield, and origin path implement the contract.
Evidence
Billing, telemetry, exercises, and data-flow records verify the decision.

Delivery economics and availability must be calculated alongside tenant correctness and evidence for the path actually serving data.

Make tenant isolation an invariant

Tenant identity comes from verified identity or a trusted workload credential, not a client header. Tenant-specific, financial, account, and authorisation responses should default to private or no-store unless an explicit isolation design is tested. Vary can distinguish representations but is not an authorisation system.

Route class	Cache and routing posture	Required test
Public documentation or assets	Public cache contract	Same representation is safe across viewers
Tenant API read	Private by default	Cross-tenant request fails at cold and warm edge
Mutation or webhook	No shared cache; explicit authority	Retry and failover do not duplicate effect
Admin or export	Strict origin authorisation	Direct origin and alternate route are denied

Representative SaaS evidence record

route=/v1/tenant/{id}/reports cache=private authority=EU-primary
allocation_driver=delivered-bytes + requests
failover=read-only-public-path-only
negative_test=tenant-B cannot retrieve tenant-A response
data_flow_version=approved-2026-07-15

Choose availability from data authority

Traffic steering cannot make multi-writer state correct, create standby capacity, or satisfy a recovery objective by itself. Begin with RTO, RPO, write authority, dependency capacity, and jurisdiction constraints. Exercise progressive failover for a representative journey, with rollback; public cacheable reads are usually a safer first candidate than authenticated writes.

Keep residency evidence with the route policy

Map primary data, replicas, cache objects, request logs, edge telemetry, DNS metadata, keys, backups, support access, and subprocessors. An EU region label is not a GDPR compliance conclusion. Keep the approved region and transfer policy versioned with the service and change it when delivery products or exports change.

Troubleshooting

SaaS edge economics failures

Presenting an allocated shared cost as an exact per-tenant invoice fact.
Treating a cache key or UUID as tenant authorisation.
Failing traffic to a healthy region that lacks compatible data, payment, or dependency capacity.
Recording database location but not cache, logs, support, or export paths.

Authoritative references

Connect SaaS delivery spend to safety and evidence

Optimi can help map cost drivers, route contracts, origin controls, and cross-provider delivery evidence for SaaS workloads.

Assess SaaS edge economics