Deploy BrightBean Studio
Self-hosted social media scheduler: web+worker, Postgres, media volume
Just deployed
/var/lib/postgresql/data
BrightBean Studio
Just deployed
/app/media
Deploy and Host BrightBean Studio on Railway
BrightBean Studio is an open-source, self-hostable social media management platform for creators, agencies and small businesses. You plan, compose, schedule, approve and publish posts, and watch comments and analytics, across Facebook, Instagram, LinkedIn, TikTok, YouTube, Pinterest, Threads, Bluesky, Google Business Profile, Mastodon and DEV.to, with no per-seat or per-channel limits.
About Hosting BrightBean Studio
BrightBean Studio is a Django app with three parts: the web app, a background worker that publishes scheduled posts and syncs inboxes and analytics, and PostgreSQL. This template runs the web app and the worker together in one service, built from a pinned upstream commit. The worker then reads the same uploaded media, on a Railway volume at /app/media, so media posts publish without S3. Migrations run and the first admin is created on every start. Signup is invite-only by default. After deploying, sign in with ADMIN_EMAIL and the generated ADMIN_PASSWORD, then add your own developer credentials for each social platform you want to connect.
Common Use Cases
- Schedule and auto-publish posts to several social networks from one calendar
- Run approval workflows with teammates and clients before posts go live
- Answer comments, mentions and messages from one shared inbox, and track post analytics
Dependencies for BrightBean Studio Hosting
- PostgreSQL (included, Railway's managed Postgres)
- A Railway volume for uploaded images and videos (included)
Deployment Dependencies
- BrightBean Studio on GitHub
- Pinned upstream commit 14b92fc
- Template repository, variables and changelog
- Platform credential setup (upstream README)
Implementation Details
- One prompt:
ADMIN_EMAIL.ADMIN_PASSWORD,SECRET_KEYandENCRYPTION_KEY_SALTare generated. CopyADMIN_PASSWORDfrom the service's Variables tab to sign in, then change it in the app. Never changeSECRET_KEYorENCRYPTION_KEY_SALTafterwards: they encrypt the stored platform tokens. - Defaults you can override with service variables:
APP_URL(the Railway domain; set it when you add a custom domain),ALLOWED_HOSTS(your domains, never*),SIGNUP_MODE=invite(openorclosedalso work). - Email: without SMTP, emails such as invitations and password resets are written to the deploy logs. Set
EMAIL_HOST,EMAIL_PORT,EMAIL_HOST_USER,EMAIL_HOST_PASSWORDandDEFAULT_FROM_EMAILto send them for real. - Social platforms: set
PLATFORM_*variables (see upstream's.env.example), or enter credentials in/admin/→ Credentials → Platform credentials. OAuth callbacks usehttps://YOUR-DOMAIN/.... - Updates: the service builds from the template's GitHub repo. When we move to a newer upstream commit, Railway shows an "update available" notice and you choose when to apply it. Migrations run on start, and your data stays in Postgres and on the volume. Check the repo's CHANGELOG.md before you update.
Why Deploy BrightBean Studio 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 BrightBean Studio 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
BrightBean Studio
aalfath/brightbean-studio-railway-templateADMIN_EMAIL
Email of the first admin account (Django superuser). Used on the first start only.
