Rolling 30-day uptime
99.95%
Status: OperationalPublic beta project health report
Project health for AI-built projects that run in the real world
Incidents and health checks are trigger signals. The product is improving project health over time: smart deploy ramps, tiny reversible patches, fast recovery, and clear next-step recommendations with Approval mode or Auto control.
Methodology updated: February 27, 2026 at 10:30 AM UTCScope: Platform-wide metrics
Project health outcomes snapshot
Current production outcomes across the last 30 days.
Median recovery time (MTTR, 30d)
4m 12s
Deploys with rollback path prepared
100%
Largest spike absorbed (30d)
12.4x baseline traffic
Who approves what: Approval mode vs Auto
Patcho can operate in Approval mode or Auto mode. Prodwise keeps those control boundaries explicit so action speed and risk stay aligned.
| Action | Mode | How it works |
|---|---|---|
| Connect a repository and grant permissions | Approval mode | You explicitly choose the repo scope in GitHub. |
| Approve Patcho recommendations | Approval mode | Patch proposals are reviewed before merge. |
| Create preview deploys and ramp releases | Auto | Each push can be validated and gradually promoted before full live rollout. |
| Trigger recovery actions from production signals | Auto | Health checks, runtime telemetry, and policy rules trigger rollback or patch workflows. |
Trigger log and recovery actions
Window: last 30 days| Date | Severity | Impact | Recovery time | Root cause | Follow-up |
|---|---|---|---|---|---|
| February 18, 2026 | P2 | Elevated latency in one region | 6 minutes | Database connection pool saturation | Added concurrency guard and pool alerting threshold |
| February 6, 2026 | P2 | Delayed deploy queue for a subset of projects | 9 minutes | Worker contention during dependency install burst | Introduced per-queue backpressure controls |
Project health FAQ
Common questions teams ask when moving from preview links to stable production.
How does Prodwise keep AI-built projects healthy after launch?
Prodwise turns production signals into action: deploy ramps, continuous health checks, tiny reversible patches, rollback-first recovery when risk rises, and improvement recommendations that prevent repeat issues.
What inputs does Patcho use to decide actions?
Patcho uses health checks, runtime telemetry, deployment events, and user-provided context to propose or trigger the safest next action.
Does Patcho always need human approval?
No. You can run in Approval mode or policy-driven Auto mode, depending on risk level and your operating preference.
Signals, methodology, and limits
Uptime: share of successful request handling over a rolling 30-day window.
Recovery time: incident detection to confirmed healthy state.
Trigger signal: user input, health-check degradation, deploy failure, or runtime anomaly that starts a recovery workflow.
Current limitation: metrics are platform-wide during beta and not yet per-project.
Status and support
Status updates: prodwise.com/reliability
General enquiries: contact@prodwise.com
Incident support: support@prodwise.com
Security disclosure: security@prodwise.com