Multi tenant event routing
Isolate tenant data while sharing infrastructure across your platform.
Your platform grows to fifty tenants.
Each one needs event routing.
You build isolation logic.
Then metering. Then billing hooks.
Tenant data leaks across boundaries.
Your team fixes it. Weeks lost.
npayload isolates every tenant from day one.
You focus on your product, not plumbing.
See how it flows
Tenant isolation
Every tenant gets their own scoped channels and subscriptions. Data never crosses tenant boundaries.
Usage metering
Track events per tenant for billing. npayload meters everything. You decide how to charge.
API first integration
One API call provisions a tenant. No custom infrastructure, no manual setup.
Ecosystem growth
Tenants discover and subscribe to each other through events. The ecosystem grows without your team building integrations.
How it works
Connect your platform once
One integration gives every tenant on your platform real time event capabilities.
Tenants are isolated automatically
Each tenant gets scoped channels and subscriptions. No data leaks between tenants.
Meter and bill per tenant
npayload tracks events per tenant. You access metering data and bill however you choose.
Multi Tenant Event Routing: Before and After
Without npayload
- Tenant data isolation requires custom scoping logic in every service
- A noisy tenant overwhelms shared infrastructure and degrades service for everyone
- Billing per tenant requires custom metering code that drifts from actual usage
- Adding event capabilities to your platform means building pub/sub from scratch
- Debugging a tenant's event flow means searching through logs shared with every other tenant
With npayload
- Every tenant gets scoped channels and subscriptions with isolation enforced by the platform
- Per tenant rate limiting and backpressure prevent noisy neighbors from affecting others
- Built in metering tracks events per tenant, ready for your billing system
- One integration gives every tenant on your platform real time event capabilities
- Tenant scoped observability shows each tenant's event flow in isolation
npayload vs Building Multi Tenant Events Yourself
| Feature | npayload | Build it yourself |
|---|---|---|
| Tenant isolation | RLS enforced scoping per tenant at the infrastructure level | Application level scoping with risk of data leaks |
| Noisy neighbor protection | Per tenant rate limiting with configurable thresholds | Shared rate limits that punish all tenants equally |
| Metering | Automatic event counting per tenant via built in metering | Custom counters that drift from actual usage |
| Tenant onboarding | Provision channels and subscriptions via API in seconds | Custom provisioning workflow per tenant |
| Observability | Tenant scoped dashboards and tracing | Filter shared logs by tenant ID manually |
| Scale | Cells scale independently per tenant or group of tenants | Shared infrastructure with complex capacity planning |