Skip to content
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. 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 stays on orphl.ink.

  3. Step 3

    Analyse

    Every click writes an event to Cloudflare Analytics Engine, and every click that is not flagged counts towards the link. Counts roll up into click totals, an hourly timeseries and per-variant results, and scheduled health checks flag links whose destination is broken. Click counts update hourly: the dashboard, the stats endpoints and embed badges cover every completed hour, not the one in progress. Suspicious clicks (rolling-window IP hashing) are counted separately and 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), 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. The URL bar still shows the orphl.ink short link.

You control

Cloaking rules (regex find/replace on the proxied HTML, priority-ordered), workspace branding, a count of proxied page loads from the last 30 minutes (admins), 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

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.

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