Multi-brand operations
If you manage multiple brands, regional sub-brands, or client domains, you need predictable routing and naming that scales without cross-brand interference. Nimriz makes each domain fully isolated by design.
- Domain-bound slugs — same short code, completely different destinations per brand
- Strict host matching — no apex/www aliasing, no cross-client collisions
- Per-domain fallback configuration for root, not-found, and expired links
The same slug exists independently under each client domain — no collision.
What you get
Separate brands reuse the same slug conventions independently — no global namespace collisions.
Exact host matching — apex and www treated as distinct domains, no accidental aliasing.
Independent root, not-found, and expired link fallbacks per domain — each client controls its own.
Click analytics are scoped per domain — client A's traffic never appears in client B's data.
How it works
Domain isolation by design
Short link lookups use (domain_id, short_code) as the key — not just the slug. This means the same slug can exist on brand-a.to and brand-b.to as fully independent links with different destinations and separate analytics.
Predictable resolution order: reserved paths → short-code lookup → domain-configured fallback.
Redirects default to 302 so you can update destinations mid-campaign without stale browser caches.
Independent not-found and expiry fallback destinations per domain — each client handles broken links appropriately.
- Reserved paths are blocked globally so system-level paths never conflict with short codes.
- Workspace isolation means all client domains can be managed from one login without leaking data across clients.
Related use cases
Ready to get started?
Create your account and start using Nimriz in minutes. Starter is free — no credit card required.