Flared 0.2.0

Links

• Import links from a CSV file or a Flared export, in the app, the API (POST /v1/links/import), or MCP.
• iPhone and Android destinations: send phone visitors to an app link instead of the destination.
• A UTM builder in the link form.
• The links list is easier to search and act on, the short link shows before you create it, and link details and analytics are simpler.
• Daily clicks switch between a chart and a table.
• The MCP tool export_links.

Webhooks and automations

• Webhooks send a signed POST when a link is created, changed, turned off or on, or reaches a click milestone. The owner manages them in Settings → Webhooks. See webhooks.md.
• Automations run actions on a link when a trigger happens, including when the destination stops loading. An automation can send a webhook. See automations.md.
• New limits in Settings → Limits and usage: 10 webhook endpoints and 25 automations by default. A limit of 0 turns the feature off.

Look and feel

• A new look across the app: Figtree text, the pixel link mark, new colours and controls, and a phone layout with a bottom tab bar and sheets.
• Settings is split into Account and Workspace sections.
• Connections lists connected apps apart from AI assistants.
• Dialogs, menus, and the side panel open and close smoothly.

Upgrade

Most copies upgrade with a clean pull request. A copy whose Cloudflare resources Deploy renamed, such as a second copy in one account with queues named flared-clicks-2, gets an issue that names wrangler.jsonc this one time. Merge by hand as the issue shows, and in wrangler.jsonc keep your own Worker, database, and queue names and IDs, and take "max_batch_size": 3 for the click queue with its comment. From 0.2.0 on, the upgrade workflow does this itself; see upgrade.md.

Fixes

• The click queue takes at most 3 clicks per run, so one run stays within the 50 D1 queries of Workers Free.
• The upgrade workflow takes a release's wrangler.jsonc with your copy's own names and IDs when the release changes lines next to them, and opens an issue only when you changed something else in that file.

Recovery

• Changing AUTH_SECRET, or setting it on an installation that ran without it, changes every webhook endpoint secret. See recovery.md.

Database changes

• packages/data/migrations/analytics/0006_click_milestones.sql
• packages/data/migrations/identity/0020_webhook_limits.sql
• packages/data/migrations/identity/0021_automation_limits.sql
• packages/data/migrations/identity/0022_operator_oauth_clients.sql
• packages/data/migrations/routing/0007_device_destinations.sql
• packages/data/migrations/routing/0008_webhooks.sql
• packages/data/migrations/routing/0009_automations.sql
• packages/data/migrations/routing/0010_transports.sql
• packages/data/migrations/routing/0011_click_forwarding.sql
• packages/data/migrations/routing/0012_hooks.sql

Each one only adds tables or columns. bun run deploy applies them before it deploys the Worker. No new secrets or settings are needed.

Flared 0.2.0-rc.2

A release candidate for 0.2.0, to test the upgrade on a copy first. The upgrade workflow merges it only when you give it the tag v0.2.0-rc.2.

Links

• Import links from a CSV file or a Flared export, in the app, the API (POST /v1/links/import), or MCP.
• iPhone and Android destinations: send phone visitors to an app link instead of the destination.
• A UTM builder in the link form.
• The links list is easier to search and act on, the short link shows before you create it, and link details and analytics are simpler.
• Daily clicks switch between a chart and a table.
• The MCP tool export_links.

Webhooks and automations

• Webhooks send a signed POST when a link is created, changed, turned off or on, or reaches a click milestone. The owner manages them in Settings → Webhooks. See webhooks.md.
• Automations run actions on a link when a trigger happens, including when the destination stops loading. An automation can send a webhook. See automations.md.
• New limits in Settings → Limits and usage: 10 webhook endpoints and 25 automations by default. A limit of 0 turns the feature off.

Look and feel

• A new look across the app: Figtree text, the pixel link mark, new colours and controls, and a phone layout with a bottom tab bar and sheets.
• Settings is split into Account and Workspace sections.
• Connections lists connected apps apart from AI assistants.
• Dialogs, menus, and the side panel open and close smoothly.

Fixes

• The upgrade workflow no longer stops when a release changes wrangler.jsonc next to your copy's own names and IDs, such as the queue names of a second copy in one Cloudflare account. It takes the release's file with your names and IDs; see upgrade.md.
• The click queue takes at most 3 clicks per run, so one run stays within the 50 D1 queries of Workers Free.

Recovery

• Changing AUTH_SECRET, or setting it on an installation that ran without it, changes every webhook endpoint secret. See recovery.md.

Database changes

• packages/data/migrations/analytics/0006_click_milestones.sql
• packages/data/migrations/identity/0020_webhook_limits.sql
• packages/data/migrations/identity/0021_automation_limits.sql
• packages/data/migrations/identity/0022_operator_oauth_clients.sql
• packages/data/migrations/routing/0007_device_destinations.sql
• packages/data/migrations/routing/0008_webhooks.sql
• packages/data/migrations/routing/0009_automations.sql
• packages/data/migrations/routing/0010_transports.sql
• packages/data/migrations/routing/0011_click_forwarding.sql
• packages/data/migrations/routing/0012_hooks.sql

Each one only adds tables or columns. bun run deploy applies them before it deploys the Worker. No new secrets or settings are needed.

Flared 0.2.0-rc.1

A release candidate for 0.2.0, to test the upgrade on a copy first. The upgrade workflow merges it only when you give it the tag v0.2.0-rc.1.

Links

• Import links from a CSV file or a Flared export, in the app, the API (POST /v1/links/import), or MCP.
• iPhone and Android destinations: send phone visitors to an app link instead of the destination.
• A UTM builder in the link form.
• The links list is easier to search and act on, the short link shows before you create it, and link details and analytics are simpler.
• Daily clicks switch between a chart and a table.
• The MCP tool export_links.

Webhooks and automations

• Webhooks send a signed POST when a link is created, changed, turned off or on, or reaches a click milestone. The owner manages them in Settings → Webhooks. See webhooks.md.
• Automations run actions on a link when a trigger happens, including when the destination stops loading. An automation can send a webhook. See automations.md.
• New limits in Settings → Limits and usage: 10 webhook endpoints and 25 automations by default. A limit of 0 turns the feature off.

Look and feel

• A new look across the app: Figtree text, the pixel link mark, new colours and controls, and a phone layout with a bottom tab bar and sheets.
• Settings is split into Account and Workspace sections.
• Connections lists connected apps apart from AI assistants.
• Dialogs, menus, and the side panel open and close smoothly.

Recovery

• Changing AUTH_SECRET, or setting it on an installation that ran without it, changes every webhook endpoint secret. See recovery.md.

Database changes

• packages/data/migrations/analytics/0006_click_milestones.sql
• packages/data/migrations/identity/0020_webhook_limits.sql
• packages/data/migrations/identity/0021_automation_limits.sql
• packages/data/migrations/identity/0022_operator_oauth_clients.sql
• packages/data/migrations/routing/0007_device_destinations.sql
• packages/data/migrations/routing/0008_webhooks.sql
• packages/data/migrations/routing/0009_automations.sql
• packages/data/migrations/routing/0010_transports.sql
• packages/data/migrations/routing/0011_click_forwarding.sql
• packages/data/migrations/routing/0012_hooks.sql

Each one only adds tables or columns. bun run deploy applies them before it deploys the Worker. No new secrets or settings are needed.

Flared 0.1.1

Deploy

• Deploy on Cloudflare asks only for SETUP_SECRET: choose any value of at least 16 characters and type it once at /setup.
• APP_ORIGIN is optional. Without it, the address where you do the setup becomes the app address. Set it to move the app; see origin.md.
• AUTH_SECRET is optional. Without it, the Worker makes its own key and keeps it in the identity database. If your copy has AUTH_SECRET, keep it: without it, everyone must sign in again.

Update notices

• The owner can turn on update checks in the setup wizard or in Settings → Updates. They are off by default.
• While they are on, the app reads https://flared.page/releases/latest.json once a day. The request has no cookie, no version, and no data about your installation.
• A newer release shows a notice with its summary, its database changes, and the upgrade steps.

Upgrade workflow

• deploy/flared-upgrade.yml opens a pull request in your repository for each release, or an issue when you must act. Add it once as .github/workflows/flared-upgrade.yml; Settings → Updates opens GitHub with the file filled in.
• When GitHub does not let the workflow open pull requests, the issue links the pull request for you to open and the setting that allows it.
• Auto mode (FLARED_AUTO_UPGRADE=true, off by default) merges a clean upgrade unless a release in it is marked breaking.
• See the upgrade guide. A copy made from v0.1.0 needs the workflow file once; a copy made before 13 October 2026 needs the first upgrade by hand.

Fixes

• Copy fields, such as the MCP server URL, show the whole value.

Database changes

• packages/data/migrations/identity/0018_update_check.sql adds the update_check table.
• packages/data/migrations/identity/0019_installation_key.sql adds the installation_key table.

bun run deploy applies them before it deploys the Worker.

Flared 0.1.1-rc.2

Pre-release for testing. The Upgrade Flared workflow merges it only when you run the workflow with this tag; the daily run and the Deploy button keep v0.1.0.

Deploy

• Deploy on Cloudflare asks only for SETUP_SECRET: choose any value of at least 16 characters and type it once at /setup.
• APP_ORIGIN is optional. Without it, the address where you do the setup becomes the app address. Set it to move the app; see origin.md.
• AUTH_SECRET is optional. Without it, the Worker makes its own key and keeps it in the identity database. If your copy has AUTH_SECRET, keep it: without it, everyone must sign in again.

Update notices

• The owner can turn on update checks in the setup wizard or in Settings → Updates. They are off by default.
• While they are on, the app reads https://flared.page/releases/latest.json once a day. The request has no cookie, no version, and no data about your installation.
• A newer release shows a notice with its summary, its database changes, and the upgrade steps.

Upgrade workflow

• deploy/flared-upgrade.yml opens a pull request in your repository for each release, or an issue when you must act. Add it once as .github/workflows/flared-upgrade.yml; Settings → Updates opens GitHub with the file filled in.
• Auto mode (FLARED_AUTO_UPGRADE=true, off by default) merges a clean upgrade unless a release in it is marked breaking.
• See the upgrade guide.

Fixes

• Copy fields, such as the MCP server URL, show the whole value.

Database changes

• packages/data/migrations/identity/0018_update_check.sql adds the update_check table.
• packages/data/migrations/identity/0019_installation_key.sql adds the installation_key table.

Flared 0.1.1-rc.1

Pre-release for testing. The Upgrade Flared workflow merges it only when you run the workflow with this tag; the daily run and the Deploy button keep v0.1.0.

Update notices

• The owner can turn on update checks in the setup wizard or in Settings → Updates. They are off by default.
• While they are on, the app reads https://flared.page/releases/latest.json once a day. The request has no cookie, no version, and no data about your installation.
• A newer release shows a notice with its summary, its database changes, and the upgrade steps.

Upgrade workflow

• deploy/flared-upgrade.yml opens a pull request in your repository for each release, or an issue when you must act. Add it once as .github/workflows/flared-upgrade.yml; Settings → Updates opens GitHub with the file filled in.
• Auto mode (FLARED_AUTO_UPGRADE=true, off by default) merges a clean upgrade unless a release in it is marked breaking.
• See the upgrade guide.

Database changes

• packages/data/migrations/identity/0018_update_check.sql adds the update_check table.

Flared 0.1.0

The first release of the self-hosted Flared edition: one owner, one workspace, and one Worker in your own Cloudflare account. Workers Free works.

What it includes

• Short links with your own slugs, link editing, disabling, and QR codes.
• Click analytics: daily totals, referrers, countries, devices, browsers, and operating systems, kept for 30 days by default.
• Your own short-link domains through Workers Custom Domains.
• Members: the owner shares an invite link, and the member creates a username and password. The owner gives a member a password reset link when needed.
• API tokens, the flared CLI, and the MCP endpoint for AI assistants with OAuth.
• Configurable limits, export, and workspace deletion.
• Password recovery for the owner with bun run owner:reset-password, through your Cloudflare login. No email is needed.

Deploy

Use the Deploy on Cloudflare button and follow docs/self-hosting/deploy.md. The button copies this release.

Upgrade

Read docs/self-hosting/upgrade.md before you merge this tag.

• A copy created before 13 October 2026 came from a commit before this release. Its footer also shows 0.1.0. For its first upgrade, use the commands for older copies in the upgrade guide. They replace every file with this release and keep your wrangler.jsonc.
• This release has database migrations: identity 0001 to 0017, routing 0001 to 0006, and analytics 0001 to 0005. bun run deploy applies the missing ones before it deploys the Worker. A migration cannot be undone by deploying older code, so note the time for a Time Travel restore first.

License

AGPL-3.0-only. If you change the code and offer it to users, publish your version and set SOURCE_URL to it.