Countly vs Metabase

Countly is an open-source product analytics platform you self-host (or run as their managed cloud), ingesting events over a REST Data API keyed by a per-app `app_key` rather than a private secret — a live unauthenticated POST to a running Countly server (try.count.ly/o) confirmed the endpoint only demands `app_key`, returning a `missing_api_key` JSON error otherwise. The Community Edition is free and self-hostable under an AGPLv3-derived license; Countly also sells a paid Enterprise Edition with SSO, extra data sources, and dedicated support.

Metabase is a self-hosted (or Metabase Cloud) open-source BI tool whose REST API is documented via an interactive OpenAPI/Scalar reference at `/docs/latest/api`; current docs describe generating an `x-api-key` from Admin settings for programmatic access, correcting auth from "None" to "API Key" (the older session-cookie login flow still exists but keyed API access is now the documented path). Its own `MB_DISABLE_CORS_ON_LOCALHOST` config option (default `false`) confirms the server sends CORS headers by default, consistent with cors "yes". The core server is free and open-source to self-host, with paid Pro, Enterprise, and hosted Cloud tiers layered on top.