Primary-standby replication with operator-initiated cutover (RTO under 60s) and near-zero recording gap. Keep video ingestion, AI inference, and Radha AI Copilot online through hardware and network failures.
Request HA Architecture ReviewFrom replication to planned DR drills, Visylix HA is built for SOC 2, ISO 27001, NDAA, and HIPAA regulated environments.
Continuous bidirectional replication of recordings, metadata, configuration, RBAC state, and evidence locks. Near-zero gap for committed frames.
An operator runs a documented cutover to promote the standby. DNS cutover or L4 load balancer redirection brings traffic to the new primary. Fully automatic failover is on the roadmap and is not shipping today.
Liveness probes monitor CPU, memory, disk, service status, and camera connectivity with custom thresholds per environment.
Trigger controlled failover from the admin console to validate DR runbooks. Required for SOC 2, ISO 27001, NDAA, and HIPAA audits.
Works with the load balancers, DNS providers, and network topologies you already use.
Recordings stream to both nodes in parallel. A camera frame that reaches the standby survives a primary crash with no re-ingestion.
Works with Route 53, Cloudflare, HAProxy, F5, AWS NLB, and any health-aware L4 load balancer.
Primary and standby both live inside your air-gapped network. Replication uses private IP with no internet dependency.
Bounded replication lag with alerting if the standby falls behind. Always know your actual RPO in real time.
Enterprise surveillance can't pause for hardware. Visylix HA keeps every camera, every AI model, and every Radha conversation online through failures.
Visylix HA pairs a primary server with a standby that continuously receives replicated recordings, metadata, and configuration. Primary failure triggers operator-initiated cutover (RTO under 60s) via DNS or L4 load balancer redirection, with a near-zero recording gap for frames committed before the failure.
RPO (recovery point objective) is effectively zero for recordings committed to the standby replica stream. RTO (recovery time objective) is typically under 30 seconds depending on your DNS TTL or load balancer health-check interval. Configurable health checks monitor CPU, memory, disk, and service liveness.
Yes. Primary and standby nodes can both live inside your air-gapped network. Replication uses private IP and does not require any internet connectivity. License validation also supports fully offline operation.
Yes. Visylix includes a planned-failover mode that drains traffic from the primary, promotes the standby, and switches back after verification, with a near-zero recording gap. This enables regular DR drills required by SOC 2, ISO 27001, and NDAA compliance programs.
Yes. Evidence locks, SHA-256 hashes, audit logs, RBAC state, and all case-management data replicate to the standby alongside video. Chain of custody is preserved through a failover event, and the audit log captures the failover itself as a timestamped event.