Coming soon

Usage analytics for plugins, apps, and extensions.

Once your plugin, app, or extension ships, the feedback loop ends. You get the usage signal back — which features run, why people deactivate, what environments they're on. WordPress plugins, mobile apps, CLI tools, and extensions. Privacy-first, no DIY telemetry stack.

php
1use Beaconstat\Client;
2
3// Call once — plugin bootstrap.
4Client::configure(
5 publicKey: 'bcs_pub_...',
6 hmacSecret: '...64-char-hex...'
7);
8
9Client::track(
10 'feature_used',
11 properties: [
12 'feature' => 'export',
13 ]
14);
swift
1import Beaconstat
2
3// Call once — app launch.
4Beaconstat.configure(
5 publicKey: "bcs_pub_...",
6 hmacSecret: "...64-char-hex..."
7)
8
9Beaconstat.track(
10 "feature_used",
11 properties: [
12 "feature": "export"
13 ]
14)

the problem

You have users. You have no data.

You ship a plugin to 50,000 sites. A browser extension to 20,000 users. An iOS app to thousands. Download counts. Support tickets. Guesswork.

SaaS companies get Mixpanel. You get a messy MySQL table and wp_options hacks.

what you get

Analytics built for distributed software. Finally.

Automatic environment detection

OS version, device info, app version, locale, runtime — collected automatically. Zero configuration.

Consent-gated collection

You build the opt-in flow in your own UI. The SDK takes a yes/no consent value and collects nothing until it reads yes.

Custom event tracking

Instrument feature usage, user actions, and workflows — anything you can name. Lightweight API that batches events and sends them async.

Deactivation feedback

Capture why users deactivate — not just that they did. Structured surveys, not freeform text.

Event-based pricing

Pay per event, not per "monthly tracked user." Inactive installs cost you nothing.

Privacy-first architecture

No PII collected by default — environment data only, unless you send more. Nothing is collected until your consent value reads yes. Full opt-out with deletion on request.

honest comparison

Why not just use Mixpanel?

Mixpanel, Amplitude, and PostHog are built for SaaS. They weren't designed for software that runs on someone else's infrastructure — whether that's a WordPress server or an end user's phone.

Runs outside your infrastructure

general: Not the model beaconstat: The whole point

Consent gating

general: DIY beaconstat: Built into the SDK

Deactivation surveys

general: DIY beaconstat: Built-in

Auto environment detection

general: Manual beaconstat: Automatic

Pricing model

general: MTU-based beaconstat: Event-based

Privacy / GDPR

general: Self-service beaconstat: No PII by default

sdk roadmap

One API. Five runtimes.

Two functions — configure() and track() — across every runtime we ship.

available at launch

PHP At launch
Swift At launch

coming later

Node.js / JavaScript Coming soon
Python Coming soon
Go Coming soon

pricing

Pay for events, not users.

Your plugin has 100,000 installs and most are inactive.
You shouldn't pay for all of them.

Free

$0 /month
  • 500K events/mo
  • 90-day retention

Starter

$49 /month
  • 2M events/mo
  • 6-month retention

Pricing may adjust before launch. It will stay tied to the events you actually send, not to users we guess at.

faq

Common questions

How is Beaconstat different from Mixpanel or PostHog?

Mixpanel and PostHog are built for SaaS — they track users on your own website or app backend. Beaconstat is purpose-built for distributed software: plugins, extensions, mobile apps, and CLI tools that run on someone else’s infrastructure. We handle consent gating, environment detection, and event-based pricing out of the box.

How does Beaconstat handle GDPR?

GDPR compliance is a shared job, so here is exactly what we handle. No personally identifiable information is collected by default. Nothing is collected at all until your integration passes a yes consent value — you build the opt-in flow in your own UI, and the SDK acts on the answer. Users can fully opt out, and all of their data is deleted on request. What you send beyond that, and how you collect consent, stays under your control.

What data does Beaconstat collect automatically?

Environment data like OS version, app version, device info, locale, and runtime — with zero configuration. No PII is collected unless you explicitly send it. Everything is opt-in by default.

How does event-based pricing work?

You pay for the events you actually track, not for "monthly tracked users." If your plugin has 100K installs but only 5% are active, you pay for the 5%. The free tier includes 500K events per month.

When does Beaconstat launch?

We’re currently in development. Join the waitlist to get early access. We’ll notify you as soon as the beta is ready.

What happens if I exceed my event limit?

We’ll notify you before you hit your limit, so there are no surprises. Events past your plan’s limit are designed to be buffered rather than dropped. Changing plans will be self-serve when invites start rolling out; it isn’t built yet.

Analytics for the software you ship. Not the software you rent.

We're in early access. Leave your email and we'll let you in — the free tier starts at 500K events a month.