Usage, SDK, integration, and self-hosting guides built from the repo itself.
Sankofa Docs covers the actual surfaces that ship today: the official Flutter SDK, direct HTTP ingestion, analytics concepts, and the self-hosted Go + ClickHouse stack.
Quickstart
Initialize the Flutter SDK, send your first events, and verify ingest.
Flutter SDK
Track, identify, set people properties, and wire replay in one client.
HTTP ingestion
Use the direct v1 endpoints when you need custom server or pipeline integrations.
Self-hosting
Run Sankofa with Docker Compose, ClickHouse, and the Go engine.
Shipped surfaces
Official today: Flutter SDK, replay helpers, direct HTTP ingestion, Go engine, ClickHouse analytics store.
Enterprise labels: session replay storage, billing and subscriptions, SAML/SSO, and audit routes are marked explicitly where relevant.
Not documented as official SDKs: JavaScript, iOS, Android, and web SDKs are omitted because they do not exist in this repo today.
Browse by section
Getting Started
Install, initialize, and send your first events.
SDKs
Official Flutter support and custom ingest patterns.
Integrations
HTTP ingestion, aliasing, and custom pipelines.
Usage
Concepts, properties, sessions, and analysis surfaces.
Self-hosting
Run Sankofa on your own infrastructure.
Enterprise
Replay, billing, SSO, and audit capabilities.
Send your first event into Sankofa with the Flutter SDK, then verify the path from client to engine.
Official Flutter support for event tracking, identity, offline queueing, and session replay.
Send events, people updates, and aliases directly to the Sankofa engine over the v1 ingest API.
Run Sankofa on your own infrastructure with the engine, ClickHouse, and a small environment surface.
Repo-backed
Every guide points back to the actual SDK, engine, env vars, or compose files that exist in this repository.
Mixed core + EE
Enterprise-only routes and features live alongside the core docs with explicit labels instead of a separate docs site.
Search-ready
Content is stored as MDX with typed metadata, so the site can grow into search or versioning later without a rewrite.
Operator-first
The docs are written for product teams, integrators, and operators who need exact setup and reference details, not a marketing summary.