Planned surfaces
| Surface | Role | Status |
|---|---|---|
| Node.js SDK | Server event ingestion, reports, action queue workflows | Planned |
| Python SDK | Warehouse jobs, notebooks, analytics workflows | Planned |
| Web API | Server-to-server event and reporting access | Placeholder |
| Webhooks | Action and guardrail notifications | Placeholder |
| MCP server | Agent-readable growth context and proposed actions | Planned |
Integration posture
FloKit should not require a mobile SDK on day one. The first marketing promise can be: connect the systems you already use, validate the numbers, then turn on controlled actions.Copy direction
Use this section to make FloKit feel easy to adopt:- No app release required for first read-only setup
- Works alongside existing subscription infrastructure
- Starts with reporting and recommendations
- Moves to automation only when guardrails are trusted