PipeKit is a mobile SDK and dashboard that combines four things teams normally buy from three separate vendors: feature flags, kill switches, remote flows, and session replay.
Chain functions that already shipped in your binary into remote flows and run them on production devices. Nothing is downloaded, and only functions you explicitly marked can run. Every run comes back with the session replay, console logs and network calls from the device that executed it, tied to the action that caused them.
Flags register themselves. You declare one in code — @PipeFlag var isMaintenanceMode = false in Swift, or a pipeFlag() delegate in Kotlin — and it appears in the dashboard on first run, already typed. There is no separate step to create the flag in a web UI and no string keys to keep in sync with your code. Flip one off and it reaches every device in about a second.
Native SDKs for iOS (Swift) and Android (Kotlin) share one dashboard, one wire format and AES-256-GCM payload encryption. Role-based access control, an audit trail on every action, and separate dev, staging and production environments.
Unlike web-first feature flag platforms, PipeKit is built for teams whose release cycle is gated by App Store and Play Store review, where a bad feature stays live until the next binary ships.