Uptime commitments, downtime credits, and support response times for all PARAMANT relay plans.
Monthly uptime percentage is calculated as: (total minutes − downtime minutes) / total minutes × 100
Uptime is measured per calendar month across the primary relay endpoint assigned to your plan. All five sector relays (health, legal, finance, IoT, relay) are covered.
If PARAMANT fails to meet the monthly uptime commitment, you may request a service credit. Credits are applied to the next billing cycle and are the sole remedy for downtime.
| Monthly uptime | Community credit | Enterprise credit |
|---|---|---|
| 99.5% – 99.9% | — | 5% |
| 99.0% – 99.5% | — | 15% |
| 95.0% – 99.0% | — | 30% |
| Below 95.0% | — | 50% |
Initial response times are best-effort targets during business hours (09:00–17:00 CET, Mon–Fri).
| Tier | Channel | Initial response | Scope |
|---|---|---|---|
| Community | GitHub Issues | Best effort | Bug reports, documentation questions |
| Enterprise | Email + dedicated channel | 4 business hours | Priority escalation, compliance docs, DPO contact, custom contracts |
The following are not counted as downtime for SLA purposes:
PARAMANT does not yet run an automated uptime monitor against every relay. What runs today: the /status page fetches GET /health on all five relays from your own browser and keeps the result for 24 hours. An hourly end-to-end check of the site and the main relay (relay.paramant.app) is built and public in the open-source repository as the heartbeat workflow: a page load in a real browser, a transfer sent and read back, a document signed and its signature verified. It runs hourly once enabled, and it is switched off until its credentials are in place, so nothing on this page rests on it yet. A run that fails opens an issue in the repository. The four sector relays (health, legal, finance, IoT) are reached only to confirm that a retired route stays refused there, so their uptime is not measured.
Historical uptime data is not yet published; the /status page shows the last 24 hours as measured from your browser. Self-hosted operators can verify relay health independently via the /v2/ct/log API endpoint.
PARAMANT may update this SLA with 30 days' written notice. Continued use of the service after the effective date constitutes acceptance of the revised SLA. Material reductions to uptime commitments entitle existing paying customers to terminate their subscription and receive a pro-rated refund for the remaining term.
For SLA credits, support escalations, or enterprise contract inquiries:
privacy@paramant.app
PARAMANT — Hetzner DE (NBG1)
EU/DE jurisdiction · GDPR Art. 28 compliant · No US CLOUD Act exposure
*.paramant.app. Self-hosted deployments are governed by the BUSL-1.1 license and carry no uptime warranty. See self-hosting documentation on GitHub for HA configuration guidance.