Features
Everything a creator page needs. Nothing it does not.
Each feature below says what it does, how to use it and where the full guide lives.
Publishing and snapshots
Edit freely. Publish when it is right.
You work on a draft. Visitors only ever see the last published snapshot, so a half-finished edit never goes live.
- Publish writes an immutable snapshot and refreshes the cached page. If that refresh call fails, the publish still succeeds and the page catches up within the 60-second cache lifetime.
- Publishing needs a display name and at least one visible link. Otherwise the API answers 422 with the missing fields.
- A version counter on the draft rejects stale edits, so two browser tabs cannot overwrite each other.
- Unpublish takes the page offline and keeps the snapshot, so republishing is instant.
Counted redirects and analytics
Know which links work.
Every link on your page points at /r/{linkId}. It answers 302 to the real URL and counts one click on an hourly counter.
- Read daily counts for the last 7 days (the default) or 30, grouped in your profile’s current time zone.
- Download the same data as CSV: date, link, category, count. Cells that could run as spreadsheet formulas are escaped.
- Counting happens after the 302 is sent. A rate-limited click still redirects; it is just not counted.
curl -sS "$API/api/analytics?range=30" -H "Authorization: Bearer $TOKEN" -H "X-Requested-With: linkweave"
curl -sS "$API/api/analytics/export?range=30" -H "Authorization: Bearer $TOKEN" -H "X-Requested-With: linkweave" -o clicks.csvPrivacy by design
Count clicks without tracking people.
Visitor data is one table of hourly counts: the link, the UTC hour, a referrer category and a count. There is nothing personal in it to leak.
- No IP address, user agent, referrer URL, visitor id or cookie is stored.
- The public page, the feed and /r set no cookies.
- The rate limiter keys counters by an HMAC of the IP under a random per-process salt, held in memory only.
- Click rows are kept 400 days and deleted at once when the account is purged.
Webhooks
Let every publish do the busywork.
Each profile can have one outbound endpoint. Every publish sends it a signed profile.published event: rebuild a site, post an announcement or clear a cache.
- Signed with HMAC-SHA256 over the timestamp and the raw body. The signing secret is stored sealed with AES-256-GCM.
- Only public https targets are accepted. Loopback, private, link-local and metadata addresses are refused when you save the URL and again at every send.
- 5-second timeout, no redirects followed, up to 6 attempts with exponential backoff. A stable event id lets you drop duplicates.
curl -sS -X PUT "$API/api/webhook" \
-H "Authorization: Bearer $TOKEN" -H "X-Requested-With: linkweave" -H "Content-Type: application/json" \
-d '{"url":"https://hooks.example.com/linkweave"}'Atom feed
A feed for every page, with no extra work.
Every published page also has an Atom 1.0 feed at /your-slug/feed.xml, so readers and automations can follow it.
- The feed is built from the published page, never from your draft.
- Like the page, it sets no cookies.
- Anything unpublished, archived or unknown answers 404.
API and typed client
Script everything the dashboard can do.
The dashboard uses the same API you do. It is described by an OpenAPI document generated from the routes, with a typed client generated from that.
- @linkweave/api-client exports the generated types, zod schemas, a fetch client and React Query hooks.
- pnpm generate:check fails CI if the routes and the committed client differ, so the contract cannot rot.
- Errors are problem+json with a requestId. An Idempotency-Key makes a retried create or publish safe.
pnpm generate # extract OpenAPI, then run kubb
pnpm generate:check # CI fails if the committed client is staleSecurity
Locked down by default, fails closed.
Several independent fences stand between the internet and your data.
- Zitadel sign-in with the OIDC authorization code flow and PKCE. Owners are identified by issuer and subject, never by email.
- An owner pin: any identity you have not allowed gets 403 on every /api route before a handler runs.
- In production the only way in is Cloudflare: a request that goes straight to the origin gets 403.
- Postgres row-level security backs up the API’s own tenancy checks.
- Deployed stages refuse to boot if a required secret is missing or the edge lock is off.
You will wish you had it yesterday.
Run it locally in five steps, then ship it to your own domain.