Skip to content
Infrastructure

How we run the platform

High availability, continuous monitoring, and a disaster recovery plan, from the database up.

Architecture overview

  • Next.js on Vercel (Edge + Serverless)
  • PostgreSQL with automatic failover
  • Backblaze B2 for document storage (S3-compatible)
  • Pooled, health-checked database connections

High availability

  • Primary + backup database configuration
  • Automatic failover on primary failure
  • Automatic connection retries with exponential backoff
  • 5-minute health checks
  • Graceful degradation (continues on backup if primary fails)

Monitoring & observability

  • Continuous database health monitoring
  • Response time tracking
  • Infrastructure event logging for post-incident review
  • StatusPage integration for public incidents
  • Public health check endpoint

Disaster recovery

  • Database failover (primary → backup)
  • Automated recovery detection
  • Event logging for all failover events
  • Manual recovery controls for our operations team

Performance

  • Edge caching via Vercel
  • Response caching for third-party API calls
  • Image optimization (Next.js Image)
  • Connection pooling for database efficiency

Infrastructure FAQs

We do not currently offer a contractual SLA. Our measured uptime is published live on the Trust Center overview (/trust) and on our public status page (status.xclause.com). Our infrastructure includes primary and backup databases, automatic failover, continuous health checks, and graceful degradation.

Our system automatically fails over to a backup database within seconds. We monitor health every 5 minutes and attempt automatic recovery when the primary is restored.

We watch several things at once: regular database health checks, connection status tracking, response time monitoring, infrastructure event logging, StatusPage integration for public incidents, and a public health check endpoint.

We automatically create incidents on our StatusPage for high-priority issues, and our system attempts automatic failover to backup resources. We maintain event logs for post-incident analysis.

Scheduled maintenance is announced on our StatusPage in advance. We use Vercel's zero-downtime deployments for most updates. Database migrations are performed during low-traffic windows with backup readiness. We provide estimated duration and impact level for each maintenance window.

Our DR plan includes: database failover (primary → backup), automated recovery detection, event logging for all failover events, manual recovery controls, automatic connection retries, and backup data replication. We are working on automated backup restoration for faster recovery.

Start running your contracts the modern way.

Build, send, e-sign, and manage every MSA and SOW in one platform. Start today, no demo required.

Free trialCancel anytimeNo long-term contract