Multi-tenant portal infrastructure

Run your portal.
Not your plumbing.

Red Route is the operational backbone behind partner and client-facing portals. Referrals, jobs, placements, safeguarding — under your brand, on your domain, scoped to the right people. Configured, not coded.

1×
Platform, many tenants
0
Code changes to add a tenant
4
Roles, scoped server-side
100%
Your brand, your domain

Built for operators who can't afford to get it wrong

One hardened platform. Every tenant gets their own brand, domain, roles and modules — without a single fork of the codebase. You configure; the platform delivers.

01

Multi-tenant by design

Each business runs its own portal — branding, domain, roles and feature modules driven entirely by config. Adding a tenant never touches core code.

02

Role-scoped access

Four fixed roles, renamed to fit your world. A partner never sees another partner's data — scoping is enforced server-side, not in the browser.

03

Modules as feature flags

Referrals, placements, safeguarding, admin. Switch modules on per tenant. The same codebase serves a charity, a roofing firm, or anything else.

04

Safeguarding, always separate

A dedicated, always-public route with its own data path. Critical reports are never buried and never mixed with operational records.

05

Private data layer

The portal never touches your database directly. Every read and write passes through a tenant-aware backend that validates, scopes, then returns only safe records.

06

Your domain, your brand

Verified custom domains, runtime brand colours and logos. Partners see your name — not ours. Red Route is the infrastructure, not the storefront.

Three steps from brief to live portal

No procurement marathon. No bespoke build. We configure your tenant against the platform and route your domain.

Step 01

Configure

Your tenant is defined in config — name, brand, roles, modules and webhooks. No tenant logic ever lives in core platform code.

Step 02

Connect

Point your domain at the platform and verify ownership by DNS. Your private backend and data tables are wired up out of public reach.

Step 03

Go live

Partners log in with a code, land on a role-appropriate dashboard, and start submitting. You watch it all from a scoped admin view.

One platform. Different operations.

The roles and modules flex to the work. The guarantees — scoping, privacy, separation — stay fixed.

Referral partners

Intake organisations submit referrals and track status — received, matched, placed — seeing only their own submissions, never anyone else's.

Charities · CICs · Social orgs

Service delivery

Delivery partners manage their placements or jobs, log outcomes, and flag no-shows. Safeguarding sits one click away, always.

Providers · Subcontractors

Operations admin

A scoped command view of every referral, partner, placement and alert across your tenant — approvals, status, oversight in one place.

Org admins · Super admins

Rules the platform won't break

Role scoping is absolute

Every private query is filtered server-side by the authenticated partner. No cross-partner leakage, ever.

Safeguarding stays separate

Own route, own data path, always public. Never rendered alongside operational records.

PII is anonymised in lists

Dashboards show reference numbers, not names. Full identities appear only at the point of entry.

No secrets in the browser

Database tokens and credentials never reach the frontend. The portal talks only to a guarded backend.

Bring your operation onto Red Route

If you run a partner or client-facing operation and you're tired of spreadsheets, inboxes and half-built portals — let's talk.

Become a tenant