Uptime commitments, incident response times, and scheduled maintenance policies for every FORG plan tier. Effective from FORG v3 launch.
Last updated: June 2026 · Trust & Compliance
Uptime is measured monthly across Rule Engine, License Worker, and dashboard availability. Downtime is defined as two or more consecutive failed health checks over a 30-second interval.
| Plan | Monthly uptime | Allowed downtime | Incident ack | Maintenance notice |
|---|---|---|---|---|
| Solo$19/mo | Best effort | No commitment | Next business day | 24 hours |
| Professional$39/mo | Best effort | No commitment | Next business day | 24 hours |
| Team$199/mo | 99.0% | 7.3 hrs downtime/month | 4 business hours | 48 hours |
| Business$599/mo | 99.9% | 44 min downtime/month | 1 business hour | 48 hours |
| EnterpriseCustom | Custom | Minimum 99.9% | 30 minutes | 72 hours |
All incidents are classified at detection time. Response time targets apply to Business and Enterprise plans. Solo and Professional customers receive best-effort responses.
Complete service unavailability or data loss
Significant degradation affecting most users
Partial degradation, workaround available
Minor issues, minimal user impact
The following are not counted against your monthly uptime calculation:
If FORG fails to meet the monthly uptime commitment for your plan tier, you are eligible for a service credit applied to your next billing cycle:
To claim a credit, contact hello@forg.pro within 30 days of the incident. Credits are non-transferable and cannot be converted to cash. Maximum credit per month is 50% of your monthly fee.
Check live uptime, incident history, and scheduled maintenance at status.forg.pro