
Deploy useSend
Open-source email platform on your own Amazon SES (Resend alternative)
Just deployed
/var/lib/postgresql/data
Just deployed
Redis
Just deployed
/data
Deploy and Host useSend on Railway
useSend is an open-source email platform and a self-hosted alternative to Resend, SendGrid and Postmark. It sends transactional and marketing email through your own Amazon SES account, with a REST API and SDKs, domain verification, contacts, campaigns, webhooks and delivery analytics in one dashboard.
About Hosting useSend
useSend is a Next.js app that needs PostgreSQL for its data and Redis for its job queues. This template runs useSend v1.10.4 from a pinned official image, plus Railway Postgres and Redis on private networking with volumes. Database migrations run on every start. Before deploying, create a GitHub OAuth app for login and an AWS IAM user with SES and SNS access, and enter both when Railway asks. The first account to sign in becomes the admin; everyone else joins through a team invite. Then add your sending domain in useSend and publish the DNS records it shows.
Common Use Cases
- Sending transactional email (sign-up, password reset, receipts) from your apps through the REST API or SDKs
- Running newsletters and marketing campaigns with contact books and unsubscribe handling
- Tracking deliveries, bounces, complaints, opens and clicks across several domains and teams
Dependencies for useSend Hosting
- PostgreSQL (included, Railway Postgres)
- Redis (included, Railway Redis)
- An AWS account with Amazon SES, and a GitHub OAuth app for login
Deployment Dependencies
- useSend source and releases: https://github.com/usesend/useSend
- useSend self-hosting guide: https://docs.usesend.com/self-hosting/overview
- Amazon SES setup: https://docs.aws.amazon.com/ses/latest/dg/setting-up.html
- Create a GitHub OAuth app: https://docs.github.com/en/apps/oauth-apps/building-oauth-apps/creating-an-oauth-app
- Template repo and changelog: https://github.com/aalfath/usesend-railway-template
Implementation Details
The useSend service builds from aalfath/usesend-railway-template, so Railway offers you an update when the template moves to a newer useSend release (see CHANGELOG.md before applying). Set the GitHub OAuth app's callback URL to https://YOUR-DOMAIN/api/auth/callback/github. If you add a custom domain, change NEXTAUTH_URL to match. Optional settings from useSend's .env.selfhost.example can be added as variables: Google login (GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET), a fixed admin (ADMIN_EMAIL), image uploads in the email editor (S3_COMPATIBLE_*, any public S3-compatible bucket) and automatic cleanup of old email content (EMAIL_CLEANUP_DAYS). useSend's separate SMTP relay (apps/smtp-server upstream) is not part of this template.
Why Deploy useSend 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 useSend 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
GITHUB_ID
Client ID of a GitHub OAuth app (callback URL: https://YOUR-DOMAIN/api/auth/callback/github). useSend has no password login; the first account to sign in becomes the admin.
GITHUB_SECRET
Client secret of that GitHub OAuth app.
AWS_ACCESS_KEY_ID
Access key of an AWS IAM user with Amazon SES and SNS permissions. useSend sends all email through SES.
AWS_SECRET_ACCESS_KEY
Secret key of that AWS IAM user.
Redis
redis:8.2