orphl.ink
Join waitlist

How it works

From POST to redirect in one round trip.

Three things happen between a short link and a click: we create it, we resolve it through your targeting rules, and we record what happened. Here's what each step actually does.

  1. Step 1

    Create

    You POST a destination URL. We assign a short slug, run the destination through a Workers AI content classifier, and store the link. The slug is yours the moment the API returns, even while moderation is still running.

    bash
    curl -X POST https://api.orphl.ink/links \
  -H "Authorization: Bearer olk_<your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "destination_url": "https://example.com/post",
    "redirect_mode": "direct"
  }'
  2. Step 2

    Resolve

    When a visitor hits orphl.ink/<slug>, we run the targeting pipeline — A/B variant, then geo (cf-ipcountry), then device (CF-Device-Type), falling back to your default destination. We append your UTM parameters without overwriting any that already exist. If your workspace has GDPR consent enabled, the visitor sees a branded consent gate first. We then either 302 to the destination, render a branded interstitial, or proxy the content through orphl.ink so the visitor never leaves your domain.

  3. Step 3

    Analyse

    Every non-suspicious click increments a KV counter and writes a row to Cloudflare Analytics Engine. The dashboard surfaces timeseries, top referrers, geo and device breakdowns, A/B variant performance, and link-health alerts. Suspicious clicks (rolling-window IP hashing) stay in the audit log but never inflate your numbers.

Redirect modes

One short link, three ways to deliver it.

Set the default per workspace; override per link.

Direct

direct

Visitor sees

A 301 or 302 redirect to the destination. Fast, invisible, lands on the target domain.

You control

Redirect code (301 vs 302), UTM parameters, A/B variant, geo + device targeting, expiry, password gate.

Interstitial

interstitial

Visitor sees

A branded transfer page with your logo, colours, and tagline — then a configurable delay, then the destination.

You control

Workspace branding (logo, colours, custom CSS), interstitial copy, delay (0 to 30 seconds), plus everything Direct offers.

Proxy

proxy

Visitor sees

The destination content served through orphl.ink. URL bar still reads your short domain. Live viewer counts.

You control

Cloaking rules (regex find/replace on the proxied HTML, priority-ordered), workspace branding, live ProxySession tracking, plus everything Direct offers.

What makes OrphLink different

Built for teams that route traffic, not for analytics dashboards on autopilot.

Proxy mode

Full content proxy through orphl.ink with workspace branding and per-workspace cloaking rules — not just a redirect.

GDPR consent flow

Per-workspace branded consent gate. Visitors who decline still reach the destination; only an anonymous counter increments.

Click-fraud detection

Rolling-window IP hashing flags suspicious clicks. Flagged events stay out of your counters and dashboards.

Audit log with retention

Every mutation recorded with before/after diffs and actor. Retention is plan-configurable, from 30 days to 1 year.

Link-in-bio landing pages

Each workspace gets a public landing page at orphl.ink/@<slug> with featured links, fully branded.

Join the waitlist.

Free for 50 active links. No credit card. No tracker.

Join the waitlist See the API