Questions, answered plainly.

Proxy mode is the wedge. We can serve the destination through orphl.ink with your cloaking rules applied, so visitors stay on orphl.ink instead of bouncing to the destination. Most shorteners stop at a redirect. Past that, we name real features (GDPR consent flow, click-fraud detection, audit log with diffs) rather than slap "AI-powered enterprise" on a hero.

On a per-link basis you can choose direct redirect, branded interstitial, or full proxy. In proxy mode OrphLink fetches the destination and serves it through orphl.ink, applying your cloaking rules (regex find/replace) to the response. The address bar keeps showing the orphl.ink short link.

Not yet. Per-workspace custom domains (Cloudflare for SaaS, with DNS verification) are built but not switched on in production yet, so every short link currently lives on orphl.ink. Branded interstitials and proxy mode are the current way to put your own branding in front of visitors.

A transfer page rendered on orphl.ink with your workspace logo, colours, and tagline — no Orphnet chrome. Visitors see your brand for a configurable delay before being forwarded to the destination. The same branding applies to password, expired, blocked, and consent pages.

Yes. Add weighted variants to a single short link — weights must sum to 100 — and OrphLink splits incoming traffic accordingly. Per-variant click counts let you pick a winner from real traffic rather than guesswork.

One short link can fan out to different destinations by country (resolved from cf-ipcountry at the edge) or by device class (iOS, Android, desktop, with a fallback). Geo wins over device; device wins over default. Split-variant links bypass targeting entirely — variants take priority.

Yes — every workspace gets orphl.ink/@your-slug as a public landing page with featured links, branded. Toggle the page on or off and choose which links appear.

Requests are counted per client IP (the cf-connecting-ip header, which Cloudflare sets and clients cannot spoof) and per top-level path in a fixed 60-second window: 60 requests for unauthenticated calls, 300 when authenticated with a JWT or API key. Over the limit returns 429 with a Retry-After header.

Yes, for 3 events: link.moderation_complete, link.health_failed, conversion.recorded. There are no click, creation or expiry events. Each delivery is a JSON POST signed with an HMAC-SHA256 of the raw body, keyed with the endpoint's signing secret (shown once at creation) and sent as X-OrphLink-Signature: sha256=<hex>; the event name is in X-OrphLink-Event. Up to 3 delivery attempts: the first, then retries after 30s and 120s.

Drag a CSV into the dashboard with a destination_url column (slug, title, and description are optional). Each row goes through the standard creation pipeline including content moderation, so imports may finish "pending" before reaching active. Cap is 500 rows per upload. Export anytime as CSV or JSON — no lock-in.

Yes. The audit log records API keys created or revoked; members added, removed or given a new role; workspace deletion; conversions recorded. Each entry has the actor, the time and the before/after values. Link and branding edits are not audited yet. Retention is set per workspace, from 1 day to 10 years (90 days by default), and a daily job prunes older entries.

Not officially. The API is plain REST described by a public OpenAPI 3.1 document at https://api.orphl.ink/openapi.json — feed it to Postman, Insomnia, or a client generator. Community wrappers are welcome.

Yes — 50 active links, hourly click analytics, one workspace, and one member. No expiry, no nag. See the full breakdown on the pricing page.

No. Signing up needs only an email and password, and a card is only required if you upgrade to Pro or Team. Registration is invite-only during early access — join the waitlist to be told when it opens.

Only non-suspicious clicks count. Every click runs through fraud detection (rolling-window IP hashing); a click from an IP over your workspace threshold is flagged and kept out of your click counts, and workspace admins get a suspicious-traffic report of flagged clicks per link. The visitor still reaches the destination; only your numbers stay clean. Click counts update hourly: the dashboard, the stats endpoints and embed badges cover every completed hour, not the one in progress.

On Cloudflare. D1 holds relational data, R2 holds workspace logos and favicons, KV holds short-lived counters and rate limits, and Analytics Engine records click events. The platform runs on Cloudflare Workers, so requests are handled at the Cloudflare location nearest the visitor. Storage is not pinned to a single country.

Yes. Every new link's destination is fetched and classified by a Workers AI model before the redirect goes live. Rejected destinations never resolve — visitors see a branded blocked page. A daily cron re-scans links older than 30 days so a destination cannot be quietly repurposed for malware after launch.

You are responsible for the destinations you proxy. Proxy mode is a tool, not permission — you need the legal right (ownership, licence, or fair use) to serve the destination content through OrphLink. We block known malicious destinations via moderation, but copyright and ToS compliance is on the workspace owner.

Two layers. This marketing site sets no cookies and runs no trackers; the only personal data it collects is the email address you choose to submit to the waitlist, and it keeps your colour theme in a localStorage entry (nuxt-color-mode) that never leaves your browser. On short links, workspaces can enable a branded consent prompt — visitors who decline still reach the destination, but only an anonymous counter increments. Visitor IPs are never stored long-term; the fraud detector hashes them into a 1-hour rolling window.