A suspiciously serious Discoflare app

Product analytics that lives in your Cloudflare.

Funnels, retention, and live events inside your Discoflare workspace. Your SDKs will barely notice. Your analytics invoice probably will.

discoflare.acme.dev Live
Events today1,248,392+18.2%
Active users38,912+6.4%
Signup → paid12.8%+1.1pt
p50 ingest9 msat the edge
Weekly active usersLast 30 days · all platforms
Web iOS
Drop-in compatible with the SDKs you already ship
PostHog Segment Amplitude RudderStack HTTP API

One app, the SDKs you know

Turn on analytics inside Discoflare.

No second control plane and no separate analytics deployment. Add the app to the workspace you already own.

  1. 01

    Open Discoflare Apps

    The install button takes you straight to Analytics in your Discoflare account.

  2. 02

    Add Analytics

    Discoflare enables the app and its schema inside the deployment it already manages.

  3. 03

    Point your SDK

    Choose the adapter for the SDK you already ship and send the first event to your workspace.

Everything product teams actually use

The analytics you need. Already in your workspace.

Funnels

See exactly where users drop off, broken down by any property.

Visited pricing
100%
Started signup
61%
Created project
38%
Sent first event
27%

Retention

Weekly cohorts that tell you if the product sticks.

Identity stitching

Anonymous visits merge into one person the moment they sign up.

anon_7f3a…anon_c912… maria@acme.dev

First-party ingest

Serve from your own subdomain. Survives ad blockers, keeps cookies on your domain.

api.analytics-vendor.com e.yourapp.com

It’s your SQL

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;

Edge-fast everywhere

Ingest runs within milliseconds of every user, on Cloudflare’s global network.

300+cities

Kill the event tax

Pay Cloudflare cents, not vendor dollars.

Analytics runs in the Discoflare deployment you already own. There is no separate per-event analytics bill.

1M10M100M1B
Typical per-event SaaS$1,992/mo
Analytics in Discoflare$10/mo
You keep$23,784every year

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

We can’t see your data. By design.

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.

  • Installed and updated through Discoflare Apps
  • Analytics access follows workspace roles
  • analflare.com never receives your production events
discoflare.comapp catalog · install · updates

Keep your tracking plan

Change one endpoint. Keep your SDK.

Already on PostHog or Segment? Use the matching adapter and keep every event name, property, and identify call you’ve built up.

Adapter guide
import 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

The convenience of an app. The control of your deployment.

AnalFlareSaaS analyticsDedicated analytics stack
Where your events liveYour Discoflare deploymentVendor cloudYour servers
Infrastructure to runYour existing Discoflare stackNoneClickHouse, Kafka, Postgres, Redis
Time to first eventAdd one appMinutesDays
Pricing modelCloudflare usagePer event, per seatYour ops team
First-party ingest domainBuilt inReverse proxyManual
Workspace access modelDiscoflare rolesVendor rolesBuild it yourself

Questions

Good questions, straight answers.

Is that really the name?

Unfortunately, yes. The Analytics app is more serious than the person who named the landing page.

Is AnalFlare a separate product to deploy?

No. AnalFlare is the public face of the Analytics app inside Discoflare. Install and manage it from the Discoflare app catalog.

Do you ever see our event data?

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.

Can I keep my PostHog or Segment SDK?

That is the point. Use the matching adapter and keep the tracking plan, event names, properties, and identify calls you already ship.

Do I need Discoflare first?

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.

What does it cost?

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.

How do updates work?

The Analytics app follows the same installation and update lifecycle as the rest of your Discoflare deployment.

Analytics belongs
in your workspace.

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

© 2026 AnalFlare · Inchi LLC · A suspiciously serious Discoflare app