Status and limitations

• GitHub OAuth source selection for one repository.
• Manual deployment of an exact branch commit when the detected application matches an enabled deployment profile.
• Enabled profiles: Static SPA, Express HTTP, Node application runtime, FastAPI HTTP.
• Release history and manual rollback to an earlier verified stateless release.
• Railpack planning and rootless BuildKit execution.
• Evidence-bound connection to an existing Supabase backend for repositories that otherwise match an enabled application profile. Provider readiness remains separate from application verification.
• Source-built single-service server runtimes exactly as published by Express HTTP, Node application runtime, FastAPI HTTP. Runtime verification covers artifact startup and the platform-owned framework probe, not application behavior or external services.
• Node SSR currently uses one replica. In-memory cache and ISR state are not durable across restart. A Next.js revision change can invalidate Server Action IDs in already-open tabs, which must be reloaded. Recreate deployment avoids mixed revisions but introduces a short cutover. Read the Next.js deployment guide.
• Constrained Dockerfile or single-service Compose source normalization for Vite SPAs using reactsveltevue. The resulting static files run on the runtime published by the enabled profile. Published source contracts: docker-spa-v4.
• Static builds use only the enabled profile's published contracts: railpack-static-npm-v4 with package-lock.jsonrailpack-static-bun-v4 with bun.lockrailpack-static-pnpm-v4 with pnpm-lock.yaml.
• A private per-project image in your personal GHCR account.
• Environment phases and component shapes exactly as published by each enabled profile.
• One HTTPS platform hostname with external revision verification.

• Multiple repositories or unsupported multi-service graphs.
• Arbitrary container runtimes, multi-service Compose, additional required processes, Cloudflare service bindings, workers, or scheduled jobs unless an enabled profile explicitly includes them.
• RunYour.App-managed databases, generic external PostgreSQL, automatic production migrations or RLS changes, Supabase Edge Function deployment, persistent volumes, or other stateful resources. Connected external services remain operated by their provider, and application behavior against them is not verified.
• Published but not yet enabled: Additional Node SSR frameworks, External PostgreSQL.
• Retired historical profiles (not planned or available): Static SPA (retired runtime), Static SPA, Static SPA, FastAPI HTTP.
• Deploy-on-push, preview environments, custom domains, or custom replica counts.
• Live logs, repair automation, billing, or an SLA.

Launches are user-initiated. A pipeline can stop when the repository is unsupported, a credential expires, a runtime value is missing, or an external route cannot be verified.

Public-beta workloads use one replica and are not a fit for production systems that require high availability, persistent state, regulated workloads, or guaranteed recovery times.

If a run stops, use the safe failure code and remediation shown in the project view. For public-beta support, email [email protected].