Skip to content
Selah.fm
Now open source

Selah.fm is
open source

The entire platform — frontend, backend, payments, and automation — is now public. Build with us. Audit us. Trust us.

View on GitHubContribute

Why we open-sourced

Transparency

No black boxes. Every line of code is visible. You can see exactly how your data is handled, how payments flow, and how security works.

Trust

Open source means independent auditability. Anyone can verify there are no backdoors, hidden fees, or data leaks.

Community

The best ideas come from everywhere. Musicians, creators, and developers can now shape the platform they use every day.

What's open

Full platform code

  • • Next.js 14 frontend (22 pages, glassmorphism UI)
  • • 28 REST API endpoints
  • • Stripe payment + Connect integration
  • • Google OAuth authentication
  • • Real-time chat and notifications
  • • Admin dashboard

Testing & ops

  • • E2E test suite (Playwright, 43 tests)
  • • Database migrations and seeding
  • • Railway deployment with auto-deploy
  • • GitHub Actions CI/CD

Our business model

We add a 20% platform fee on top of the artist's CPM rate to keep the platform running and improving. Creators earn the full CPM. This covers hosting, support, payment processing, and the managed service at selah.fm.

FAQ

Does open source mean I don't have to pay the fee?

No. The 20% platform fee (added to artist CPM) applies to the managed platform at selah.fm. The code is free to use, study, and modify, but the hosted service has operating costs.

Can I host my own version?

Yes. The MIT license allows you to fork the code and run your own instance. You'll need your own Stripe account, database, and Google OAuth credentials.

How do I contribute?

Fork the repo, make your changes, and open a pull request. Check CONTRIBUTING.md for guidelines. We welcome bug fixes, features, documentation, and design improvements.

Is my data safe?

Absolutely. The code is public for transparency, but your data on selah.fm is private and protected. Database credentials and API keys are never exposed — they live in Railway environment variables.

Star us on GitHub

Every star helps more musicians and creators discover us.