Welcome to Sankofa
One platform unifies eight products — strategize, ship, observe, and recover before users notice.
Sankofa is a closed-source SaaS platform for the full strategize → build → ship → observe → recover loop. Eight products run on a single engine and a unified set of SDKs, so a strategy initiative, a ticket, a flag, a deploy, a crash, and a survey share the same identity, the same cohorts, and the same audit trail.
The eight products
Strategy
Vision
Five-surface strategy workspace — Canvas, Roadmap, OKRs, Initiatives, Strategy Docs.
Engineering
Plan
Tickets, sprints, releases, and roadmaps bonded to deploys, replays, and revenue.
Engineering
Catch
Crash detection with auto-rollback in under 60 seconds.
Experimentation
Switch
Feature flags with cohort targeting, halt webhooks, variants, and experiments.
Engineering
Deploy
OTA releases gated by Catch and Switch signals.
Insights
Analytics
Events, users, cohorts, insights, funnels, flows, retention — plus replay and heatmaps.
Insights
Pulse
Surveys triggered by real user behavior and cohorts.
Experimentation
Remote Config
Typed values with cohort-targeted payloads, version history, and A/B item experiments.
How the pieces fit together
Sankofa is organized around three concepts you'll see throughout the docs:
Organizations and projects
Every customer has an organization. Inside an organization, you create projects for each app, service, or environment-isolated workload. A project is the boundary for events, flags, configs, deploys, surveys, RBAC, and billing.
Live and test environments
Each project has two environments —
liveandtest— each with its own API key. The engine resolves the environment from the API key on every request. There is no separate "test project" — the same configuration powers both, so you can promote with confidence.One handshake, every product
On app launch and resume, an SDK calls a single decision endpoint. The engine returns a snapshot of every flag, config, survey trigger, and deploy directive — keyed by cohort, ETag-cached, and replayed on the next crash. This is the seam that makes "one binary, zero glue code" possible.
What ships today
SDKs at a glance
The web ships as a multi-package monorepo so you only pay for what you use. Every other client platform (Flutter, RN, iOS, Android) ships as a single SDK that bundles every supported client product. Server SDKs (Node, Go, Java, Python) focus on Catch + tracing.
7 packages
Web
@sankofa/browser, catch, config, switch, pulse, replay-rrweb, react. Tree-shakeable.
Single SDK
Flutter
Six client products in a single pub.dev package (Analytics, Catch, Switch, Config, Pulse, Replay).
Single SDK
React Native
Bare and Expo. Config plugin included.
Single SDK
iOS
Swift first, Objective-C interop. SPM and CocoaPods.
Single SDK
Android
Kotlin first. Maven Central.
Single SDK
Node
Express and Fastify subpath exports.
Single SDK
Go
Server-side analytics, flags, and config.
Tooling
CLI
sankofa init, release, flags, config, demo.
Read the docs in this order
Quickstart
Send your first event in under five minutes. Pick your platform and follow along.
Concepts
Learn the data model — organizations, projects, environments, events, identity, sessions, the decision handshake, retention.
Products and SDKs
Pick the product or SDK you want to integrate and follow its dedicated guides.
API reference
For custom pipelines, server-to-server flows, or SDKs we don't yet ship, the REST API is fully documented.