Enterprise

Route serious traffic.

Control who touches your links, put the uptime floor in writing, and keep every byte in the EU — with a named engineer beside you from migration through security review.

99.99% SLAEU residency — FrankfurtSSO · SCIM · RBACDedicated Slack channel
Building the case?
Control & scale

SSO, scoped roles and a forensic audit log — enough to convince your own security team before ours ever joins a call.

Reviewing for procurement?
Compliance & terms

The artifacts you're scanning for, on one page — SLA with credits, DPA, EU residency as legal fact, support in writing.

Governance

One control plane, every team.

Enforce SSO across the org, provision through SCIM, and scope exactly who can create, edit or export — per workspace.

SSO — SAML & OIDCOktaMicrosoft EntraGoogle Workspace

Enforceable org-wide — no password stragglers, no shadow accounts.

SCIM provisioning

Joiners get the right role on day one. Leavers lose access the minute HR flips the switch — not at the next quarterly review.

Role-based access, per workspace

Agencies see their campaigns and nothing else. Owner, Admin, Editor, Viewer — scoped to the workspace, not the org.

acme3 workspaces · 42 members · SSO enforced
Marketing12 members
lena@acme.comOwner
sarah@acme.comEditor
Product22 members
jonas@acme.comAdmin
eng-team · 8 seatsEditor
Agencies · external8 members
partner@studio.coViewer · link-only

roles scoped per workspace · every change lands in the audit log ↓

The audit log

Who did what, from where — already on file.

Every admin action lands in an immutable log the second it happens. This is the artifact your security review reads.

Illustrative audit log: six admin events with time (UTC), actor, action, target, origin IP and channel — a role grant, an SSO session, a CSV export via API key, a domain added, an SSO policy enforcement, and a SCIM deprovisioning. Four fields are annotated: the actor (a named human, API key or IdP — never “someone”), the origin (source IP and channel on every entry), the change (object, action and outcome, spelled out) and the timestamp (immutable, UTC, exportable for two years).

Actor

A named human, API key or IdP — never “someone”.

Origin

Source IP and channel captured on every entry.

Change

Object, action and outcome, spelled out.

Timestamp

Immutable, UTC, exportable for two years.

Reliability

Frankfurt-fast. Contractually up.

Anycast edge, EU-resident storage, and an uptime floor that lives in the contract — not on a marketing page.

p50 redirect latencymeasured from region
Frankfurt11 ms
Amsterdam16 ms
London19 ms
Virginia88 ms
Singapore152 ms
99.99% monthly uptime floor — service credits below it, spelled out in the SLA
Anycast network — the nearest edge answers, Frankfurt stays the system of record
Public status page with 90-day history — subscribe your ops channel
In writing

What the contract actually says.

Procurement doesn't buy adjectives. These are the numbers as they appear in the Enterprise agreement — same figures as the pricing page.

Service level agreement — excerpt
Monthly uptime target99.99% — measured per calendar month, across all edge regions
Below 99.99%10% service credit of the monthly fee
Below 99.9%25% credit · below 99% — 50%
ExclusionsScheduled maintenance only, announced ≥ 7 days ahead
Support model — enterprise
P1 response1 hour, 24/7 — a human who can ship a fix
ChannelDedicated Slack channel with our engineers
OnboardingNamed engineer through migration and first 90 days
CadenceQuarterly review — usage, roadmap, renewals without surprises
Compliance

The checklist, pre-checked.

Forward this section to whoever owns the questionnaire — most of it is already answered.

EU data residencyEvery byte stored and served from Frankfurt, Germany — no US mirror.In force
GDPR / DSGVOProcessor terms, sub-processor list and TOMs in the DPA.In force
DPAStandard template, countersigned in days.Via sales
Security reviewSend the questionnaire — engineers answer it, not autoresponders.Via sales
SOC 2 Type IIThird-party attestation in progress — ask for current documentation.In progress
Migration

Bring everything, lose nothing.

Bulk import keeps slugs, tags and destinations intact — and every old link 301s forever. A named engineer runs the cutover with you.

50,000
links imported
0
broken redirects
99.99%
uptime floor, in the SLA
11 ms
p50 redirect from Frankfurt
2 yrs
audit-log retention
24/7
P1 cover, 1-hour response
Talk to us

Bring the questionnaire.

Thirty minutes with an engineer who can actually answer it — SLA, migration plan and rollout timeline included.

Need the DPA or security review first? Same call — or sales@rii.link sends both ahead of it.