What is Prodwise?
Prodwise is a managed production setup for AI-built projects. You connect a GitHub repository, define production context through onboarding, and Prodwise handles deploy flow, health checks, and safety guardrails.
Documentation
Everything you need to get your project online and keep it there.
Getting started
Deploying your project
Availability and reliability
High availability under traffic spikes
How Prodwise keeps your project available during sudden traffic increases.
Health checks and explainability signals
What we track, how bot-ready incident signals are emitted, and how recovery starts.
Backups and restore
How your data is protected and how to restore it.
Guides
Quick start
Connect GitHub, select a repository, answer onboarding questions, and review the generated PROD.md before it is committed. Once approved, your project is configured for production workflows with monitoring and rollback controls.
The PROD.md file
PROD.md documents how your project runs in production: domain, cloud provider, region, scaling mode, database, backup policy, and required secret names. It lives in your repo so humans and tools can use the same source of truth.
Connecting a GitHub repository
Prodwise uses GitHub access to read your repository, generate PROD.md, and run deployment workflows tied to your code changes. You select which repositories are connected during onboarding.
Custom domains
Map your own domain to your Prodwise deployment and keep domain configuration tracked alongside your production context. Domain changes are reflected in PROD.md to avoid configuration drift.
Environment variables and secrets
Secret values are not committed to git. PROD.md stores only required secret names so your runtime contract is explicit while sensitive values remain securely injected at runtime.
High availability under traffic spikes
Production workloads are designed to absorb sudden traffic increases with scaling controls and health-aware routing. Reliability reporting is currently platform-wide and expands to per-project visibility over time.
Health checks and explainability signals
Prodwise continuously evaluates service health and emits runtime signals that are consumable by automation and easy for teams to interpret. This shared signal layer makes rollback and recovery decisions explainable instead of tedious.
Backups and restore
Backup and restore practices are part of the operational baseline, including documented retention windows and restore drill reporting. This keeps recovery expectations explicit rather than implicit.