Customer workers
Dedicated edge delivery for eligible customer domains, with safe publication, verification, and rollback.
Release lifecycle#
- 1
Build
LocusVia creates an immutable release from the approved domain configuration. - 2
Verify
The candidate is checked for routing correctness, isolation, and required assets. - 3
Publish
A verified release becomes active without changing the customer-facing domain. - 4
Recover
A failed verification or unhealthy release restores the last healthy version.
Eligibility#
Static delivery is used only when the domain configuration can be represented safely at the edge. Dynamic policies, experiments, or other runtime-dependent behavior stay on the managed resolver.
Isolation and idempotency#
Domain scoped
A release is bound to one customer domain and its approved configuration.
Repeat safe
Publishing the same immutable configuration does not create a different release.
Health checked
Activation requires a successful smoke check on the published version.
Rollback ready
The previous healthy version remains available for recovery.
Note
Publishing changes delivery placement, not the public redirect contract.