Funnels
See exactly where users drop off, broken down by any property.
Funnels, retention, and live events inside your Discoflare workspace. Your SDKs will barely notice. Your analytics invoice probably will.
One app, the SDKs you know
No second control plane and no separate analytics deployment. Add the app to the workspace you already own.
The install button takes you straight to Analytics in your Discoflare account.
Discoflare enables the app and its schema inside the deployment it already manages.
Choose the adapter for the SDK you already ship and send the first event to your workspace.
Everything product teams actually use
See exactly where users drop off, broken down by any property.
Weekly cohorts that tell you if the product sticks.
Anonymous visits merge into one person the moment they sign up.
anon_7f3a…anon_c912… maria@acme.devServe from your own subdomain. Survives ad blockers, keeps cookies on your domain.
Raw events sit in D1. Query them, export them, join them — no API quotas.
SELECT name, count(*) AS n FROM events WHERE timestamp > '2026-09-01' GROUP BY name ORDER BY n DESC;
Ingest runs within milliseconds of every user, on Cloudflare’s global network.
Kill the event tax
Analytics runs in the Discoflare deployment you already own. There is no separate per-event analytics bill.
Illustrative infrastructure estimate using Workers Paid + D1 list prices with batched ingest. Your incremental cost depends on the rest of your Discoflare workload.
Ownership by architecture
analflare.com is the public landing page and SDK-adapter playground. Events go from your product to the Analytics app in your own Discoflare deployment.
Discoflare Workerworkspace · analytics · authKeep your tracking plan
Already on PostHog or Segment? Use the matching adapter and keep every event name, property, and identify call you’ve built up.
Adapter guideimport posthog from 'posthog-js'
posthog.init('afk_live_9f2c…', {
// Point your existing SDK at the Analytics app
api_host: 'https://discoflare.acme.dev',
})
posthog.capture('signup_completed', { plan: 'pro' })The honest comparison
AnalFlareSaaS analyticsDedicated analytics stackQuestions
Unfortunately, yes. The Analytics app is more serious than the person who named the landing page.
No. AnalFlare is the public face of the Analytics app inside Discoflare. Install and manage it from the Discoflare app catalog.
No. SDK traffic goes to the Analytics app in your Discoflare deployment and event data stays in the D1 database in your Cloudflare account. analflare.com is the landing page and adapter playground.
That is the point. Use the matching adapter and keep the tracking plan, event names, properties, and identify calls you already ship.
Yes. The install button opens the Analytics app in your Discoflare account. If you do not have a workspace yet, Discoflare will guide you through creating one.
There is no separate AnalFlare infrastructure or analytics subscription. The app runs in your Discoflare deployment, and you pay Cloudflare for the resources that deployment uses.
The Analytics app follows the same installation and update lifecycle as the rest of your Discoflare deployment.

Add the Analytics app to Discoflare, then connect the SDK you already ship.