All Help Articles

FAQ

What is the SLA and uptime commitment for paid plans?

Revenue Proven targets high availability for paid customers, with infrastructure monitoring and disk alerts in place; formal SLA terms for enterprise customers are available on request.

2 min read

Revenue Proven runs on a four-server production architecture in Singapore with a Caddy load balancer distributing traffic across two web instances. This means a single server restart does not take the product down for users. The system includes automated health checks, disk monitoring, and infrastructure alerting.

Infrastructure reliability measures

  • Load balancer with active health checks routes traffic away from unhealthy instances within seconds
  • Daily database backups to self-hosted RustFS with Backblaze B2 fallback
  • Continuous write-ahead log archiving for point-in-time database recovery
  • Disk usage alerts at 70 percent warning and 85 percent critical thresholds
  • Infrastructure status pushed to an internal admin dashboard every 60 seconds

Formal SLA

A formal, percentage-based SLA is available for Enterprise customers and is part of the Enterprise contract negotiation. Standard paid plans (Pro through Agency) do not currently include a written SLA, though Revenue Proven works to maintain the highest availability possible within its infrastructure design. If you require a specific uptime guarantee in writing, discuss this with the team as part of an Enterprise agreement.

Current help workflow

This answer was refreshed against the current Revenue Proven product and its exact /pricing route. It is written for the Shawn Brown demo workspace, whose pages contain real connected-system data in some areas and seeded examples in others.

Current product screen relevant to faq-sla-uptime
Current product screen relevant to faq-sla-uptime. Captured from /pricing.

Use this screenshot as the route-specific visual reference for “What is the SLA and uptime commitment for paid plans?”. Labels, plan gates, roles, asynchronous loading, permissions, and available controls can vary with the signed-in workspace.

When troubleshooting, first confirm the active workspace, selected account, connections, date range and entitlement. Treat Save, Send, Sync, Publish, Resume, Reconnect and Delete controls as state-changing actions, and consult the current route before relying on older screenshots or navigation instructions.