Business Continuity & Disaster Recovery
Witboost's on-premises deployment model gives customers full control over business continuity and disaster recovery strategies.
Platform Resilience
Witboost is designed for high availability:
| Capability | Implementation |
|---|---|
| Microservices Architecture | Individual components can be scaled and recovered independently |
| Kubernetes Native | Leverages K8s self-healing: automatic pod restart, rolling updates, health checks |
| Stateless Services | Application services are stateless; state is stored in PostgreSQL and the secrets manager |
| Horizontal Scaling | Components scale horizontally to meet demand |
| Health Monitoring | Liveness and readiness probes for all services |
Backup & Recovery
In an on-premises deployment, the customer has full control over:
| Parameter | Customer-Controlled |
|---|---|
| Backup Schedule | Frequency of database and configuration backups |
| Retention Policy | How long backups are retained |
| RPO | Recovery Point Objective — how much data loss is acceptable |
| RTO | Recovery Time Objective — how quickly the platform must be restored |
| Backup Location | Where backups are stored (on-site, off-site, cloud) |
| Encryption | Backup encryption method and key management |
What to Back Up
| Component | Backup Strategy |
|---|---|
| PostgreSQL Database | Standard PostgreSQL backup tools (pg_dump, continuous archiving) |
| Git Repositories | Already versioned; mirror to secondary Git server if needed |
| Secrets Vault | HashiCorp Vault backup / Kubernetes Secrets backup |
| Kubernetes Config | Helm values, ConfigMaps, and deployment manifests in Git |
| Custom Templates | Stored in Git — inherently version-controlled |
Agile Lab provides guidance and best practices for backup configuration.
Incident Response
Agile Lab maintains documented incident response procedures:
- Defined roles and escalation paths for security incidents
- Communication plan for notifying affected parties
- 72-hour breach notification capability under GDPR Article 33
- Post-incident review process to identify and remediate root causes
Support & SLA
| Support Tier | Availability |
|---|---|
| Standard Support | Business hours (CET/CEST) |
| Premium Support | Extended hours with defined response times |
| Critical Patches | Security patches delivered outside the regular release cycle |
For full details on support processes, escalation paths, and SLAs, see Agile Lab Customer Support.
Platform Independence
Because Witboost runs on the customer's infrastructure:
- No vendor lock-in — The platform uses standard technologies (Kubernetes, PostgreSQL, Git)
- No single point of failure — Agile Lab's availability does not affect the platform's operation
- Full data portability — All metadata, templates, and configurations are stored in standard formats (YAML, JSON, SQL)
- Graceful degradation — Even without Agile Lab support, the platform continues to operate