The public website and documentation are separate from app.getralti.com. Hosted Ralti runs through Cloudflare and Render, with independent web and background-worker services, a restricted PostgreSQL application role, and shared private attachment storage. It does not depend on a personal Mac tunnel. Publishing the marketing site does not deploy the application or distribute a native build.

Prepare a separate deployment#

For another environment, use the application’s checked-in render.yaml and release runbooks as the configuration baseline. Use Node24, separate administrator credentials for reviewed migrations, restricted runtime credentials for web and workers, and a private shared storage driver. Preserve existing records, attachments, identity bindings, and encryption keys when migrating. Docker Compose remains a separate self-hosting path.

bash
node --import tsx scripts/render-service.ts check
# Run the service roles only after release admission:
node --import tsx scripts/render-service.ts web
node --import tsx scripts/render-service.ts worker

The Render launcher checks verified database TLS, restricted role permissions, exact migration versions and checksums, and private storage readiness before starting either service. It does not perform production DDL. Web binds the provider’s PORT; the worker accepts no incoming traffic. Preserve streaming and do not cache authenticated HTML or API responses. Runtime readiness is not continuous provider monitoring.

Keep origins and recovery consistent#

  • Add the public site and app hostnames to their respective hosts; use the exact DNS records those hosts return.
  • Choose a canonical apex or www website host and permanently redirect the alternative. Preserve existing mail DNS.
  • Update ATLAS_PUBLIC_ORIGIN, Clerk authorized origins, and exact registered email OAuth callbacks.
  • Update the website’s canonical, sitemap, structured-data, social-image, and app-link origins.
  • Verify TLS, sign-in, record persistence, files, worker outcomes, device access, and a restored backup.

Match the application to its schema#

The current Agent Member release uses schema40, following Apps migrations038 and039. A binary expecting an older exact ledger cannot simply be restarted against the newer database. Use a reviewed compatible release or forward fix; preserve completed work and uncertain external-action receipts. A healthy marketing site or process-liveness endpoint is not proof of database, worker, or provider readiness.