Production Setup

Prax can be deployed to cloud services or self-hosted on your infrastructure. Below are the main requirements and notes for production setup.

Requirements

  • Node.js or Docker-compatible host (e.g. Linux server, VPS)

  • PostgreSQL or SQLite (for persistent storage)

  • Reverse proxy (e.g. Nginx) if hosting under a domain

  • HTTPS configuration (via proxy or certbot)

Recommended Deployment Targets

  • Railway – One-click deployment, PostgreSQL integration

  • Render – Easy autoscaling for full-stack apps

  • VPS/Cloud Server – Docker-based manual deployment

  • Kubernetes – For container orchestration (advanced setups)

Environment Variables

In production, environment variables should be securely managed. Use Docker secrets, CI/CD env injection, or config management systems like Vault or Doppler.

At minimum, set:

  • OPENAI_API_KEY

  • DATABASE_URL

  • PORT

  • FRONTEND_URL

Optional variables include authentication toggles, memory store credentials, and third-party keys.

Persistent Data

Ensure that your volume mounts (or database connections) persist across container restarts. If you're using Docker:

  • Mount the database directory to a local or cloud volume

  • Back up flow data regularly

Reverse Proxy & HTTPS

If deploying on a public domain, route traffic via a reverse proxy (e.g., Nginx or Caddy) and serve HTTPS using Let's Encrypt or an SSL certificate provider.

PreviousRun LocallyNextCommon Issues

Last updated