Raydium

Appearance

Effortless Multi-Tenancy ​

WordPress has always promised simplicity, yet the moment your agency graduates from one site to dozens, that promise falters. Repositories multiply, table prefixes blur together, and the same security patch is repeated like a ritual. Raydium arrives with a refreshing proposition: keep WordPress vanilla, slip a feather-light framework in front of it, and let that framework shoulder every multi-tenant burden before WordPress even wakes up.

A Framework You’ll Hardly Notice ​

Open a Raydium project and you won’t be greeted by custom themes, proprietary plugins or sprawling boilerplate. Instead you’ll see a modest bootstrap file, a handful of human-readable configs, and a service container humming quietly in the background. That’s deliberate. Raydium’s goal is to stay invisible to WordPress, not to reinvent it.

How the Magic Happens ​

  1. Request arrives. The framework reads the host name—say, client-alpha.example.com—and looks it up in a simple tenant map.

  2. Tenant chosen. That map points to a tenant ID. Instantly, Raydium loads an environment for that tenant, filling PHP’s environment with the correct database credentials, table prefix, cache namespace and feature flags.

  3. Services configured. Database, cache, logger and any other shared resources are built from that tenant-aware environment. There’s no global $wpdb guesswork; each service already knows where it belongs.

  4. WordPress boots. Only now does the project include WordPress’s loader. From WordPress’s perspective, it’s a perfectly ordinary single-site install—just one whose constants have been pre-loaded with the right values.

Because the framework finishes its work before WordPress starts, every site you serve stays cleanly siloed. Yet all those sites share a single codebase, a single deployment pipeline, and a single set of quality gates.

What That Means for You ​

  • One push, many updates. Fix a bug once; every tenant benefits.
  • True isolation. Separate databases, caches and logs without the complexity of a full WordPress Network.
  • Friction-free onboarding. Add a tenant by drafting an env file and a JSON line in your tenant map, no repository cloning or custom scripts.
  • Plugin compatibility intact. Because Raydium never patches core, nearly every plugin behaves exactly as it would on a standalone site.

Still Beta ​

Raydium is labeled Beta for a reason. File names can shift, new middleware hooks may appear, and edge-case documentation is catching up to feature velocity. But that also means your feedback carries weight. Early adopters are shaping the polish, stability and road-map priorities that will lead to a 1.0 release.

Try It in an Afternoon ​

Spin up a demo project, add two tenants, point each to its own database, and browse both domains side by side. You’ll see the same WordPress dashboard—unchanged in appearance quietly drawing data from completely different databases. That first taste often sparks the realisation: “We could run our entire client roster from one repository.”

If that possibility excites you more than it scares you, Raydium is ready for a test-drive. Grab the repo, skim the quick-start, and experience calm and simplified multi-tenancy.