Enterprise Service Terms
RevAddress publishes live operational health publicly and handles formal support commitments during enterprise onboarding. This page is intentionally conservative: it explains what we show publicly today and what moves into written commercial terms.
What we publish publicly
The status page and health endpoint show the current probe state, not a blanket public SLA.
Incidents and current degradation belong on the status surface. Public marketing pages should not overstate uptime or service-credit terms.
The support page is the public path for help, billing, and escalation into engineering.
Support posture by plan
| Tier | Support path | Notes |
|---|---|---|
| Free | Self-serve docs + status page | Best-effort access for proving the integration. |
| Starter / Growth | Email support | Use the dashboard, support inbox, and status page for current operational guidance. |
| Pro | Priority email + onboarding help | Protected workflows, BYOK, and higher-throughput planning support. |
| Enterprise | Direct engineering onboarding | Formal response windows, escalation paths, and commercial terms handled in written agreements. |
What moves into written enterprise agreements
For enterprise accounts, we can define support expectations in writing during onboarding. That can include response windows, escalation contacts, throughput shaping, onboarding milestones, and commercial remedies where appropriate.
Those terms are negotiated per account because RevAddress depends on upstream USPS services, account-specific licensing posture, and workload shape. We do not treat a public webpage as the source of truth for those commitments.
What is explicitly excluded from public promises
- USPS upstream outages or degraded performance
- Carrier-side rate limiting or licensing constraints
- Scheduled maintenance or controlled deploy windows
- Automatic service-credit schedules for all plans
- Blanket public uptime guarantees for free or self-serve tiers
Need enterprise terms?
Start with the free proof path, then talk to engineering when you need higher-volume access, written support commitments, or custom onboarding.