
Deploy Nestled.js Starter Kit
Production infrastructure for Nestled.js
Postgres 18
Just deployed
/var/lib/postgresql/data
Redis 8.2
Just deployed
/data
Just deployed
Just deployed
Deploy and Host Nestled.js on Railway
Nestled.js is a production-ready NestJS + React starter template with authentication, organizations/teams, RBAC, Stripe billing, an admin panel, and a fully generated GraphQL SDK. It gives you a clean foundation so you only build your custom features.
About Hosting Nestled.j
This template deploys four services: a PostgreSQL 18 database, Redis 8, a NestJS GraphQL API, and a React web app. Database migrations run automatically before each API deploy, and the Prisma client and both apps are built for you.
You'll need to set environment variables for your URLs, cookie domain and email, and optionally for OAuth providers (Google, GitHub), Stripe billing, and file storage (ImageKit, S3, Cloudinary). If your API and web app are on different subdomains (for example api.myapp.com and app.myapp.com), set API_COOKIE_DOMAIN to .myapp.com on both the api and web services, so signing out clears the session everywhere.
The first user to register automatically becomes the super admin.
Common Use Cases
- SaaS applications requiring multi-tenant organizations, team invitations, and role-based access control
- Subscription-based products with Stripe billing, plan management, and webhook handling
- Internal tools and admin dashboards with audit logging, user management, and generated CRUD APIs
Dependencies for Nestled.js Hosting
- PostgreSQL 18 and Redis 8 (provisioned automatically by this template)
- Node.js 22 with pnpm (pinned in the repository; Railway picks it up automatically)
Deployment Dependencies
- Nestled.js Documentation - full setup guide, schema configuration, and feature documentation
- Stripe Dashboard - for billing keys, webhook secrets, and product configuration
- Google Cloud Console - for Google OAuth (optional)
- GitHub Developer Settings - for GitHub OAuth (optional)
- An email provider (SMTP, SendGrid or Mailgun) for transactional emails
Why Deploy Nestled.js 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 Nestled.js 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
Postgres 18
ghcr.io/railwayapp-templates/postgres-ssl:18Redis 8.2
redis:8.2APP_URL
https://api.myapp.com | The public URL where your API is hosted. Railway provides this after deployment.
APP_NAME
Your application's display name. Shown in emails, 2FA authenticator apps, and browser titles.
SITE_URL
https://myapp.com | The public URL of your frontend application. Used for generating links in emails and redirects.
APP_EMAIL
hello@myapp.com | The "From" address for all outgoing emails. This is what users see as the sender.
ALLOWED_ORIGINS
CORS allowed origins. Your frontend URL(s). Comma-separate multiple origins: https://myapp.com,https://admin.myapp.com,https://www.myapp.com
APP_ADMIN_EMAILS
admin@company.com | Comma-separated list of admin email addresses. Receives contact form submissions and system notifications.
API_COOKIE_DOMAIN
.myapp.com | Auto-detected | Cookie domain for authentication. Set this if your API and frontend are on different subdomains (e.g., api.myapp.com and app.myapp.com). The leading dot allows sharing across subdomains.
APP_SUPPORT_EMAIL
support@myapp.com | The "Reply-To" address for emails. Also used in some default 'Need Help?' links.
VITE_API_URL
Your api url - https://api.yourdomain.com
API_COOKIE_DOMAIN
.myapp.com | Auto-detected | Cookie domain for authentication. Set this if your API and frontend are on different subdomains (e.g., api.myapp.com and app.myapp.com). The leading dot allows sharing across subdomains.