Deploy Cap
Self-hosted Loom alternative: Cap Web, media server, MySQL and a bucket
media-server
Just deployed
cap-web
Just deployed
MySQL
Just deployed
/var/lib/mysql
Bucket
Bucket
Just deployed
Deploy and Host Cap on Railway
Cap is an open-source alternative to Loom. You record your screen and camera with the Cap desktop app (macOS, Windows) or in the browser, then share a link. Cap Web stores the recordings and serves the share pages, comments and the dashboard. This template runs your own Cap Web server on Railway.
About Hosting Cap
Cap Web is a Next.js server that needs MySQL and S3-compatible storage, plus a media server that runs FFmpeg for thumbnails, faststart and imports. This template deploys four pieces:
- both Cap services, built from our GitHub repo with the official images pinned by digest
- Railway MySQL on a volume
- a private Railway Bucket for recordings
Secrets are generated, and services talk over the private network. On start, Cap runs its database migrations and sets the bucket's CORS rule for your domain, so browser uploads work. You fill in nothing. To sign in, enter your email: the 6-digit code appears in cap-web's Deploy Logs until you add Resend for email.
Common Use Cases
- Async video updates, walkthroughs and bug reports shared by link, with your recordings kept on your own storage
- A self-hosted upload server for the Cap desktop app and Chrome extension
- Team screen recording with comments and per-video sharing settings, without per-seat SaaS pricing
Dependencies for Cap Hosting
- MySQL 8 (Railway MySQL, included)
- S3-compatible storage (Railway Bucket, included)
Deployment Dependencies
- Cap source and licence (AGPLv3): https://github.com/CapSoftware/Cap
- Cap self-hosting docs: https://cap.so/docs/self-hosting
- Template repo with Dockerfiles and changelog: https://github.com/aalfath/cap-railway-template
- Cap desktop app downloads: https://cap.so/download
Implementation Details
After deploying:
- Open the cap-web domain and enter your email. Copy the code from cap-web → Deployments → Deploy Logs ("VERIFICATION CODE").
- In Cap Desktop, set Settings → Cap Server URL to your domain.
- Before you share the URL, restrict sign-ups with
CAP_ALLOWED_SIGNUP_DOMAINS=yourcompany.comon cap-web. Anyone who can reach the server can otherwise create an account.
Optional variables on cap-web:
RESEND_API_KEYandRESEND_FROM_DOMAIN: email sign-in codesASSEMBLY_API_KEY,GROQ_API_KEYorOPENAI_API_KEY: transcription and AI summariesGOOGLE_CLIENT_IDandGOOGLE_CLIENT_SECRET, or the OIDC settings: single sign-on
For a custom domain, set WEB_URL to https://YOUR-DOMAIN and redeploy. Never change DATABASE_ENCRYPTION_KEY.
Updates: upstream publishes the server only under moving image tags, so we pin each tested build by digest in the template repo. When we bump it, Railway shows an update notice in your project. Read CHANGELOG.md, then apply the update. Migrations run on start.
Why Deploy Cap 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 Cap 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
