Skip to main content
Documentation
Trust and reliability

Architecture and Resilience

How WarpLink serves redirects from an edge cache and records clicks through a queue, so cached links keep redirecting through disruptions.

Cached links keep redirecting when the database is down, and keep redirecting when the dashboard and API are down. This page describes the design in plain terms.

Two paths

WarpLink runs two separate paths, so a problem in one does not take down the other.

PathWhat it servesWhat it depends on
Redirect pathShort-link taps from visitorsThe edge key-value cache. The database only on a cache miss.
API and dashboard pathThe dashboard, the REST API, the MCP server, and the SDK calls for link resolution and attributionThe database, and the same edge network

How a redirect works

  1. The visitor taps a short link. The nearest edge location receives the request.
  2. The redirect service reads the link's configuration from the edge key-value cache. For a custom domain it first reads the domain's serving status from the same cache.
  3. It screens the user agent, chooses the destination for the visitor's operating system, and returns a 302.
  4. After the response is on its way, it puts one click event on a queue and, for mobile visitors, stores the deferred-link payload in the cache. Neither step makes the visitor wait.

Every link is written to the database first and then to the cache, and a repair queue keeps the two in sync.

Click recording

A separate consumer reads click events from the queue in batches of up to 100 and writes them to the database. Click uniqueness is decided in the database at write time. Each event carries the time of the click, so a late write still lands in the correct billing period and the correct day of your analytics.

Availability

Redirects are served from the edge cache with a database fallback, and click events are queued for processing. The dashboard and API run separately from the redirect path.

On the Scale and Unlimited plans, link redirects and the API, including the SDK endpoints, carry a 99.9% monthly uptime commitment with service credits. The terms are in section 5 of the Terms of Service, and live status and incident history are on status.warplink.app.

Request limits for SDK calls

An SDK key can call only the four SDK endpoints: key validation, link resolution, attribution match, and referral claims. Every other route refuses it.

SDK calls are limited to 60 requests per minute per key per client IP address. API keys, which servers and CI jobs use, are limited to 60 requests per minute per key. See Rate limiting.

Health checks

The redirect service exposes /health for liveness and /health?deep=1 for readiness. The deep check probes the database and the cache, each with its own deadline.

For measured redirect timings, see Performance and methodology.