Good tidings
from production.

Tidings is lightweight product analytics for developers and small product teams. Your application POSTs JSON events to one HTTP endpoint — there is no SDK to install — and you read them back as a live event feed, per-user histories, funnels, retention, and dashboards.

Free to start, no card. Events stay in the EU, in Amsterdam.

One POST request. That's the whole integration.

No SDK to vendor, no schema to negotiate. Send an event name and a distinct_id, any stable string that identifies the user, from anything that speaks HTTP. Add properties when you need them.

  • Authenticate with a per-project API key
  • Attach any JSON properties to an event
  • Events show up in the explorer within seconds
Send your first event
$ curl -X POST https://api.tidingshq.com/api/v1/events/ \
    -H 'Content-Type: application/json' \
    -H 'X-API-Key: td_your_key' \
    -d '{"name":"checkout_completed","distinct_id":"user_42"}'

{"accepted": 1}

Keys live in the project's Settings → API keys. Full reference: POST /api/v1/events/

The day's news from your product

What happened, who did it, and how often. Everything after the POST is built for reading, not configuring.

Every user, as a timeline.

Every event carries a distinct_id, so a person's history assembles itself. Open anyone and read it, first touch to last.

Funnels, retention, paths, sessions.

Pick the steps and read where people leave. Retention by cohort, the paths between screens, and how long a visit lasts, all from the same events.

Dashboards without the ritual.

Pin the counts and trends your team actually checks. A dashboard here is a page of answers, not a quarterly BI project.

Also: heatmaps drawn over page screenshots, saved insights and segments, annotations on every chart, CSV export.

Your coding agent reads it too.

Hand the integration to Claude Code or Cursor with one prompt: the docs ship an AGENTS.md and an llms.txt written for it. Then give the agent a personal access token and it reads the same funnels, retention and users your team sees, through the MCP server's eighteen tools. In the app, Ask Tidings answers a plain question the same way.

terminal: connect Claude Code
$ claude mcp add --transport http tidings https://api.tidingshq.com/api/v1/mcp/ --header "Authorization: Bearer tk_your_token"

Smaller than PostHog. Smaller than Mixpanel. On purpose.

Both are excellent, and both are platforms: session replay, experiments, report builders, warehouses. Tidings does event analytics and stops there. Here's the spec-level version, including the rows we lose.

One flat price, however many products you ship.

Free to start. Pro is per organization, not per seat, and hosted in the EU. VAT added where applicable.

Free

$0forever, no card

Everything you need to instrument a side project or an MVP.

  • 100k events / month
  • 1 project, 3 seats
  • 30-day event retention
  • Live explorer, funnels, retention, paths, sessions
  • Heatmaps and dashboards
  • CSV export
  • MCP server and personal access tokens
  • Ask Tidings — a few questions a day
Get started
Coming soon

Pro

$19per month

or $190 / year — two months free

One flat price per organization, for teams shipping weekly who want history and headroom.

  • 2M events / month included
  • Unlimited projects and seats
  • 13-month retention — year-over-year
  • Ask Tidings without the Free ceiling
  • AI “What changed this week” write-up
  • Heatmap screenshots
  • Priority support
Start on Free

Free while we're in beta — orgs that sign up now keep Pro free for six months after paid plans open.

Something else

Tell uswhat you need

More volume than Pro, longer retention, SSO, self-hosting? None of it ships today — but what gets asked for most is what gets built next. Tell us what would make Tidings work for you, and we'll tell you honestly whether it's close.

    Tell us what you need

    Questions people ask before they sign up

    Straight answers, including the ones about our competitors.

    Do I need to install an SDK to use Tidings?
    No, Tidings has no SDK and no client library. POST a JSON body with an event name and a distinct_id, with your project's API key in the X-API-Key header. Up to 500 events fit in one batched request.API reference →
    How is Tidings different from PostHog?
    PostHog is a broad platform: product analytics plus session replay, feature flags, experiments, surveys and a data warehouse, open source and self-hostable. Choose PostHog for those adjacent products in one tool, or to run analytics on your own infrastructure today. Choose Tidings for event analytics over plain HTTP, with nothing else to configure.Full comparison →
    How is Tidings different from Mixpanel?
    Mixpanel is a mature, closed-source event-analytics product with per-platform SDKs and a deep query surface. It fits large analytics teams with complex reporting needs. Tidings fits a small team that wants the common core (event explorer, user profiles, funnels, retention, paths, dashboards) over plain HTTP, instrumented this afternoon.Full comparison →
    How does Tidings handle my data?
    Tidings stores only what your code sends, plus your account email, name and organization name. It does not sell your data, share your events with advertisers, or use them to train models. Ad attribution is the one exception, only through Reddit's own click id and only for visitors who accepted the cookie banner.Privacy policy →
    Where is my data hosted?
    Tidings runs on Scaleway in Amsterdam (nl-ams), in the EU, and the database never leaves the EU. The AI features send query results to Anthropic's Claude API only once an organization owner turns them on. Events are kept for the project's retention window, and a daily purge deletes anything older.Privacy policy →