Question 1

What is PipeKit?

Accepted Answer

PipeKit lets you control and fix your mobile app after it ships. It lets you register Swift functions as safe actions, combine them into step-by-step flows, and run those flows remotely on production devices — without releasing a new version.

Question 2

How is PipeKit different from feature flags or remote config?

Accepted Answer

Feature flags toggle static values. Remote config swaps predefined settings. PipeKit orchestrates actual runtime logic — pre-registered Swift functions that execute on-device.

Question 3

Can PipeKit execute arbitrary code on devices?

Accepted Answer

No. PipeKit can only run actions that were defined in your application at build time using the @Rewire macro. There is no eval, no dynamic code loading, no remote script execution.

Question 4

What platforms are supported?

Accepted Answer

PipeKit currently supports iOS (13.0+) with Swift Package Manager. It works with both UIKit and SwiftUI. Android (Kotlin) support is coming soon.

Question 5

What is a node?

Accepted Answer

A node is a Swift function annotated with @Rewire that registers itself with PipeKit at app launch. Once registered, it can be triggered remotely — individually or as a step in a flow.

Question 6

What is a flow?

Accepted Answer

A flow is an ordered sequence of nodes that PipeKit executes on a target device. Flows are defined in the dashboard and dispatched over WebSocket.

Question 7

Does session replay affect app performance?

Accepted Answer

Session recording captures at 1 frame per second with low bitrate compression. The SDK runs on a background thread and uses less than 1% CPU.

Question 8

Is PipeKit safe for production?

Accepted Answer

Yes. Only approved actions can run, role-based permissions control who can trigger flows, every action is audited, and a kill-switch can disable all remote actions instantly.

Question 9

Is PipeKit GDPR compliant?

Accepted Answer

Yes. You control what data is collected, users can be informed and consent obtained, and you can delete user data on request.

Question 10

How is usage measured?

Accepted Answer

Usage is measured by flow executions per month. Session recording and telemetry are included in all plans and do not count separately.

FAQ

General

Runtime Control

Observability

Security & Safety

Technical

Billing

Troubleshooting