Zerct keeps deploys predictable by rejecting projects that are expensive or ambiguous to run.Documentation Index
Fetch the complete documentation index at: https://docs.zerct.com/llms.txt
Use this file to discover all available pages before exploring further.
Current guardrails
Cargo.lockis required.- A health endpoint is required.
- Apps must bind to
0.0.0.0:$PORT. - Secrets must stay in server-side environment variables.
- Builds may be queued when capacity is busy.
Planned guardrails
- Resource limits per deployment
- Idle cold starts for free deployments
- Rust lint and unsafe-code policy checks
- Database connection and migration safety checks