If the phone rings, we answer. Even when something breaks.
An agent that is down is worse than no agent at all — it silently swallows the calls you were already paying for. Redundancy is not an upsell here; it is the architecture.
Four nodes, one private network
Redundant application tier, isolated data tier, and a load balancer that knows how to drain a node without hanging up on your customer.
Load balancer
Nginx terminates TLS, health-checks both app nodes, and drains traffic from an unhealthy node without dropping a live call.
- TLS 1.3
- Health checks
- Rate limiting
Application node A
Serves all traffic under normal conditions. Sized to carry full production load on its own.
- Primary upstream
- Health checked
Application node B
An identical clone of the primary, kept deployed and idle. Nginx promotes it automatically when node A fails its health check.
- Standby upstream
- Automatic promotion
Database
A dedicated PostgreSQL node reachable only from the application tier over the private mesh, never from the public internet.
- PostgreSQL
- Private-only access
Every hop between nodes travels over a private WireGuard mesh. No service port is exposed to the public internet except the load balancer, and database traffic never leaves the encrypted tunnel.
Built for the 2am no-heat call
The value of an always-on agent collapses the moment it is not on. These are the properties that keep it up.
Redundant application tier
Two identical application nodes sit behind a health-checking load balancer. If the primary stops passing checks, nginx fails traffic over to the standby without manual intervention.
Private encrypted mesh
Application, database, and monitoring nodes talk only over WireGuard. The database has no public interface and no inbound rule that permits one.
Measured, not assumed
Answer latency, transfer success and booking rate are tracked per call, so what the agent is doing for you is a number you can look at rather than a claim we make.
Hardened by default
Key-only SSH, host firewalls that default-deny, and rate limiting at the edge on every endpoint that takes a credential.
- Application nodes
- 2, load balanced
- Failover
- Automatic
- Public database access
- None
- Deploys
- Rolling, with rollback
Your customers' conversations, handled like they matter
Recorded calls are some of the most sensitive data a business holds. We treat them that way, and we will walk your security reviewer through every control.
- TLS 1.3 in transit, and third-party tokens sealed with AES-256-GCM at rest
- Role-based access, and an account revoked stops working on the next request
- Audit log of every call, message, and configuration change
- Recording is off until you turn it on, and the disclosure is spoken before it starts
- Retention and BAA scoped per deployment, on request
- Secrets held outside the repository, injected at runtime
Watch it book a slot on your own calendar.
Bring your fit rules and connect a calendar. We will configure an agent on the call, dial it together, and you watch the appointment land on a slot you actually had free.
No slide deck. No procurement gauntlet.