rdyrct

rdyrct

Organization-based link shortener + QR codes, running entirely on Cloudflare's edge.

Use it at rdyrct.com or self-host it for free. If it's useful to you, a ⭐ helps other people find it.

---

Deploy in one click

Cloudflare copies this repository to your GitHub account, creates the database, storage and queues, and asks for one thing: the email of the account that becomes the platform admin. Leave every other value as it is. The first build serves your copy on its workers.dev address, generates the session key and applies the migrations; each push to your copy deploys it again. When you want your own domain, see Move to your own domain.

Prefer a terminal? bun run setup does the same from a clone: see Deploy to Cloudflare Workers.

---

Features

• Short links with custom or random slugs, optional UTM parameters (source, medium, campaign, term, content) applied at redirect time.
• Grouped link addresses: renaming a link keeps the old slug redirecting for 48 hours before it's freed, and a link can carry extra aliases that all redirect to the same destination.
• QR codes per link, with live preview and PNG/SVG download. Paid plans add a logo in the center and custom dot styles and colors.
• Custom domains (paid plans: 1 on Hobby, 5 on Pro): connect links.yourbrand.com via Cloudflare for SaaS, with slugs namespaced per domain.
• Link import and export: bring links in from Bitly, Short.io, Rebrandly, Dub or any CSV (paid plans, up to 20,000 rows), and export them to CSV.
• REST API and MCP server: API keys for the REST API (each acts as its account, with that account's roles), and a hosted MCP server at /api/mcp with OAuth. See /docs.
• Organizations with owner / admin / member / viewer roles: admins manage the team, domains, and billing; members manage links; viewers read.
• Magic-link invites: single-use, valid for 7 days, sent by email.
• Privacy-friendly analytics: clicks per day, top links, countries, referrers, devices. No IP addresses are ever stored.
• Per-user Free/Hobby/Pro billing through Polar, which acts as Merchant of Record and handles tax/VAT.
• Newsletters with consent kept in your database: two lists (product news, offers), each opted into on its own, sent from the app through Resend, with a one-click unsubscribe in every email.
• Secret-pinned superadmin console: the account matching SUPERADMIN_EMAIL gets a cloud-console panel for usage, org drill-down, and plan management. It 404s for everyone else.

---

Stack

rdyrct is built Cloudflare-first: the entire product runs in a single Worker with no separate backend to host:

• Cloudflare Workers: one Worker serves the API, the redirect hot path, and the static React app.
• D1: SQLite at the edge, source of truth for auth, orgs, links, clicks, and domains.
• KV: slug → destination lookups on the redirect hot path, so a click never waits on D1.
• R2: QR logo images, keyed by org, served immutable and cached.
• Cloudflare for SaaS: custom hostnames for paid orgs' own short-link domains.
• Workers Rate Limiting: separate abuse controls for auth, email, writes, uploads, domains, billing, and click recording.

Application layer:

• Hono for routing
• BetterAuth for email+password auth, with email-OTP verification and PBKDF2/WebCrypto hashing
• Drizzle ORM over D1
• React 19 + Vite + @cloudflare/vite-plugin
• Tailwind v4 + Base UI
• TanStack Query + TanStack Router
• Polar for billing, Resend for transactional email

---

Local development

What you need

• Bun 1.4 or newer.
• Node 24 or newer. Bun runs the scripts, but portless and wrangler run on Node.
• macOS or Linux. Dev servers run behind portless (installed with the project), which gives each one a stable HTTPS name instead of a port.
• Optional: the Polar CLI, only to receive sandbox billing webhooks.

First run

bun install

bun run dev

That is the whole setup. On the first run bun run dev:

1. creates .dev.vars from .dev.vars.local.example, with an auth secret of its own (every other value works locally as it is);
2. applies the local database migrations (it does this on every run, so a pull never leaves you a migration behind);
3. starts the app, a local email inbox and a local Google sign-in, each behind portless (portless may ask for your password once, to listen on port 443 and trust its own certificate);
4. prints the addresses once the app answers:

  rdyrct     https://rdyrct.localhost

scenarios https://rdyrct.localhost/__dev/scenarios inbox https://rdyrct-mail.localhost/emails (header: authorization: Bearer test_token_admin) google https://rdyrct-google.localhost

Then, in a second terminal, fill the database with fake organizations, links and clicks:

bun run db:seed:local

and open the scenarios page. It signs you in as a seeded account in each state the app has: pro-owner, showcase (a tidy Pro org for screenshots), hobby-owner, free-owner, fresh (a brand-new account), member, viewer, over-plan, grace-ended, locked-org, click-cap and admin. /__dev/scenarios/ ?to=/links opens a page directly.

Ctrl+C stops everything. If one of the three crashes, the other two stop with it.

Day to day

• One name per checkout. The main checkout is rdyrct, rdyrct-mail, rdyrct-google; a git worktree gets the branch in its names (rdyrct- , rdyrct- -mail…), so any number of checkouts run side by side. bun scripts/dev-hosts.ts prints this checkout's addresses.
• Email. Sign-up codes and every other mail land in the local inbox, never a real one:

  curl "$(bun scripts/dev-hosts.ts mail)/emails" -H 'authorization: Bearer test_token_admin'

• Google sign-in goes through the local emulator with two accounts, testuser@gmail.com and admin@gmail.com.
• The admin console. Open the admin scenario. (Or set SUPERADMIN_EMAIL in .dev.vars and sign up with that address.)
• Start the database over: bun run db:reset:local, then bun run dev and bun run db:seed:local again.
• rdyrct.com's own pages. The dev server runs the self-hosted app. Add VITE_RDYRCT_SITE=1 to .env to work on the landing and marketing pages.

From another computer or a phone

Switch portless to LAN mode once:

sudo portless service install --lan

The addresses then end in .local (https://rdyrct.local) and any device on the same network opens them; bun run dev says so when it starts. The first visit from another device shows a certificate warning, because that device does not trust portless's certificate: continue past it. Every name is a single word before .local on purpose: Windows finds only those on a network. On Linux, LAN mode needs avahi-utils.

Integrations

When something is off

• "`.dev.vars` sets this checkout's addresses": bun run dev works out APP_URL, APP_HOST, SHARED_LINK_HOST, RESEND_BASE_URL and GOOGLE_EMULATOR_URL itself. Delete the lines it lists from .dev.vars (an old copy has them).
• "Invalid origin" when saving or signing out: open the address bun run dev printed, not localhost: .
• A page will not load at all: bunx portless doctor checks the proxy, and bunx portless list shows what is running.
• The seed stops with a 500: the local database is busy (a browser test run, say). Run it again when it is quiet.

---

Tests

bun run test          # fast unit tests

bun run test:worker # Worker routes with local D1 and KV bindings bun run e2e:install # install Chro