Deploy PraiseDynasty
We host whatsapp for like whatsapp
Just deployed
/var/lib/postgresql/data
Redis
Just deployed
/data
evolution-api
Just deployed
Deploy and Host PraiseDynasty on Railway
PraiseDynasty is an AI-assisted conversational sales operating system for WhatsApp-first businesses. It combines a multi-tenant FastAPI backend, Supabase/pgvector-powered RAG, and a six-state Sales Progression Engine to qualify leads, follow up automatically, and move conversations toward a sale — entirely over WhatsApp, with a Next.js dashboard for oversight and billing.
About Hosting PraiseDynasty
Hosting PraiseDynasty means running a multi-tenant FastAPI backend connected to a Supabase Postgres database with pgvector enabled for RAG-based reply generation, alongside an Evolution API instance that handles the WhatsApp connection for each tenant. The backend runs the Sales Progression Engine, which tracks each lead through a six-state follow-up playbook and triggers automated messages and escalations. A Next.js dashboard gives each tenant visibility into conversations, analytics, and billing, which is processed through Paystack. Because it's multi-tenant, one deployment can serve multiple WhatsApp-first businesses at once, each isolated by tenant.
Common Use Cases
- Real estate lead qualification and automated follow-up (e.g. property inquiries via WhatsApp)
- General WhatsApp-first SMB sales automation and conversational checkout
- Service businesses managing and progressing inbound WhatsApp leads
- Multi-tenant SaaS deployments serving several client businesses from one instance
Dependencies for PraiseDynasty Hosting
- Supabase (Postgres + pgvector) — primary database and vector store for RAG
- Evolution API — WhatsApp connectivity layer for sending/receiving messages
- Paystack — payment processing and billing
- An LLM provider (e.g. Gemini or an OpenAI-compatible endpoint) — powers RAG completions and reply generation
Implementation Details (Optional)
Left out for now — add a snippet here if you want to show, e.g., a sample webhook payload or a Sales Progression Engine state transition.
Why Deploy PraiseDynasty on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying PraiseDynasty on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
PGDATA
Filesystem path where Postgres stores its data files inside the container.
PGPORT
Port Postgres listens on (default 5432).
POSTGRES_DB
Name of the database Evolution API and other services should connect to.
POSTGRES_USER
Username Railway creates for this Postgres instance.
SSL_CERT_DAYS
Validity period (in days) for the auto-generated SSL certificate used for secure Postgres connections.
RAILWAY_DEPLOYMENT_DRAINING_SECONDS
How long Railway waits for existing connections to drain before stopping the service during a deploy.
Redis
redis:8.2.1REDISPORT
Port Redis listens on (default 6379).
REDISUSER
Username for authenticating to Redis (default is usually default).
evolution-api
evoapicloud/evolution-api:latestPORT
Port the Evolution API server listens on inside the container.
REDIS_URI
Redis connection string used by Evolution API for session/state caching.
SERVER_URL
Public URL of this Evolution API deployment. Used to generate correct webhook and QR/connection URLs — set this to your Railway-assigned domain.
CORS_ORIGIN
Allowed origin(s) for cross-origin requests to the API. Use * to allow all, or a specific domain for tighter security.
DEL_INSTANCE
Time (or flag) controlling whether a disconnected WhatsApp instance is automatically deleted.
QRCODE_LIMIT
Maximum number of QR code generation attempts allowed per instance before requiring a restart.
REDIS_ENABLED
Whether Evolution API uses Redis for general caching (true/false).
CACHE_REDIS_URI
Redis connection string specifically used for the caching layer (may differ from the main Redis URI).
DATABASE_ENABLED
Whether Evolution API persists data to a database (true/false).
DATABASE_PROVIDER
Which database engine Evolution API should use (e.g. postgresql).
CACHE_REDIS_ENABLED
Whether Redis-based caching is turned on for Evolution API (true/false).
AUTHENTICATION_API_KEY
Secret API key required to authenticate all requests to this Evolution API instance. Rotate this before production use.
CACHE_REDIS_PREFIX_KEY
Prefix added to all Redis cache keys created by Evolution API, to avoid collisions if Redis is shared.
DATABASE_CONNECTION_URI
Full connection string Evolution API uses to reach its Postgres database.
CONFIG_SESSION_PHONE_NAME
Display name shown for the linked device/session in WhatsApp's "Linked Devices" list.
CACHE_REDIS_SAVE_INSTANCES
Whether WhatsApp instance state is persisted to Redis so instances survive restarts (true/false).
CONFIG_SESSION_PHONE_CLIENT
Client name identifying this app/session to WhatsApp (shown during the linking/QR process).