Works on any host, no rebuild, no client JS
Lume is CDN-agnostic and server-side. Report your traffic from the edge, from CDN logs you already emit, or with one SDK call, on any host, multi-CDN, or origin-direct. However you install, you see your whole audience: humans, bots, and AI agents, told apart.
The SDK is optional
Worried about another dependency, more client JS, or added latency? Start with a path that has none of that. The edge and CDN-log integrations add zero client JS and zero latency. Lume reads the logs and edge events you already produce, after the response is on its way to the visitor. The TypeScript SDK is there when a single server-side call is the easiest thing to ship: one option, not a requirement.
SDK & API
One server-side call: the lowest-overhead path when you can add a line of code.
Edge & platform
Report from the edge or your platform with no app rebuild, most with zero code.
Cloudflare (no-code connector)
Paste a read-only API token and Lume pulls your Cloudflare traffic. No Worker, no deploy, nothing at the edge.
Set it up →Cloudflare Worker
Report edge traffic from your own Cloudflare zone: no SDK, no app changes, no added latency.
Set it up →Vercel middleware
One middleware file, zero added latency, and it works on serverless and edge isolates where the SDK can’t.
Set it up →WordPress
A drop-in, zero-dependency plugin: no code, reports after the response, never blocks a page load.
Set it up →CDN logs
Point logs you already emit at Lume. Zero client JS, zero added latency, config-only.
Fastly
Point Fastly’s Real-Time Log Streaming straight at Lume: config-only, no code, no extra infrastructure.
Set it up →Akamai
Push Akamai DataStream 2 request logs to Lume: config-only in Property Manager, no code.
Set it up →AWS CloudFront
Forward CloudFront real-time logs to Lume via Amazon Data Firehose HTTP delivery.
Set it up →Google Cloud
Route external Application Load Balancer (Cloud CDN) logs to Lume via a Pub/Sub push subscription.
Set it up →Cloudflare Logpush
For Enterprise Cloudflare zones that want zero code at the edge: batched request logs via Logpush.
Set it up →Why not just my CDN’s own analytics?
Your CDN only sees traffic behind its own edge
Cloudflare’s analytics stop at Cloudflare; CloudFront’s stop at CloudFront. Move a property, add a second CDN, or serve some routes origin-direct and the picture fragments. Lume sits above the CDN, so one dashboard covers all of it.
Portable: you’re not locked to one edge
Because Lume works on any host, multi-CDN, or origin-direct, your traffic history follows you when you switch or add providers. The measurement doesn’t die the day you leave the edge that produced it.
One classification, verified, across every source
Every path (edge, logs, SDK, or REST) feeds the same catalog-based classification and, where a visitor IP is available, the same cryptographic verification. You get one consistent human / bot / AI-agent split instead of a different vendor’s definitions per CDN.
See how it works, or the full field lists and code on the developer docs.
Wire Lume in however you ship.
Free plan, one ingest token. Pick the path that fits your stack, from a no-code connector to one SDK call.
Start for free →