← Elido vs the field
Elido vs Rebrandly
Plain REST without the workspace-in-header workarounds.
Rebrandly built its reputation on branded links per domain. Elido moves the workspace-first model and wraps it in a predictable REST API — no `apikey` header, no `workspace` shadow header.
Where Elido wins
- Bearer auth instead of `apikey` + `workspace` headers
- OpenAPI 3.1 spec with 44 endpoints
- EU data residency by default
- Free tier with 90-day analytics retention (Rebrandly: 1 month)
- Conversion tracking from Stripe / Shopify (Rebrandly: not native)
- Wildcard subdomains on Business
Where it's a wash
- Custom domain count on entry tier
- QR code branding
- Webhook delivery semantics
Where Rebrandly still wins
- More mature mobile-app deep-link tooling
- Wider integration catalog (Zapier, etc.)
- More premium short domains in inventory
Side by side
| Feature | Elido | Rebrandly |
|---|---|---|
| Auth model | Bearer token | apikey + workspace headers |
| Free tier — links | 50 | 500 |
| Free analytics retention | 90 days | 30 days |
| Pro tier price | €9 / mo | $29 / mo |
| Pro tier — clicks/mo | 100,000 | 5,000 |
| Conversion tracking | Native | Via integrations |
| Wildcard subdomains | Business | Enterprise |
| OpenAPI spec | 3.1, 44 endpoints | Custom |
| Self-host | Apache 2.0 | Not available |
Ready to switch?
Each migration guide covers the CSV import, the custom-domain CNAME flip (zero downtime), and the API mapping line by line.