Parity & roadmap
Living checklist of implemented vs planned platform capabilities. Canonical repo copy: docs/PARITY_CHECKLIST.md.
Core deploy pipeline
- GitHub App, manual deploy, auto-deploy, path filters, deploy hooks: documented
- Build/runtime logs, deploy queue, zero-downtime, rollback, health checks: documented
- Cancel deploy: documented
- Clear build cache: documented
Service types
All seven types implemented: see Service types.
Known gaps (stubs / planned)
- Native workflows
- AWS integration (credentials only; no ECS deploy)
- DDoS protection (use Cloudflare edge)
- Compliance certifications (self-hosted responsibility)
- Multi-region (metadata API; single-region deploy today)
Recently shipped
- Coding agents / MCP: MCP server in
packages/mcp - API rate limiting: global
/v1throttle via@fastify/rate-limit - Maintenance mode
- One-off jobs
- Log streaming export
- SAML SSO
- Inbound IP rules
- Platform TLS for custom domains via Cloudflare for SaaS
- Pluggable platform SMTP (password reset + team invites)
Partial features (documented honestly)
- Custom domain platform TLS: available when
CF_API_TOKEN+CF_ZONE_IDare set (100 free hostnames) - gVisor: opt-in via
./scripts/setup-gvisor.sh+ISOWARD_DOCKER_RUNTIME=runsc - Horizontal scaling / autoscaling: redeploy loop, not true LB
Infrastructure
- Cloudflare wildcard tunnel: manual operator setup; see Cloudflare tunnel setup
- GitHub App credentials: manual; see Connect GitHub