Gradual rollouts
Percentage and audience Controls can let teams introduce a feature in deliberate stages.
Products Developer tools
Available for trialFeature flags & remote config
FlagPilot
A little more control over every release.
FlagPilot helps mobile teams decide when an existing feature reaches users. Plan gradual rollouts, adjust configuration, and keep a known fallback when a device loses its connection.
Guided evaluation · Technical discovery · Trial access through our team
iOS / SwiftAndroid / KotlinFlutterREST management API
Core capabilities
Built around the
work that matters.
Explore how FlagPilot works, then talk with us about trial access for your workflow.
Remote configuration
Manage configuration values for behavior already supported by your application.
Offline defaults
SDK plans include cached values and explicit local defaults for devices without a connection.
Change history
A history of configuration changes can make it easier to review and restore earlier settings.
How it works
A clear path from
setup to everyday use.
Define a flag
The SDK can wrap an existing feature in a named flag with an explicit default.
Choose an audience
Configure an rollout stage and the conditions under which the feature should be enabled.
Adjust with context
Review the rollout and change configuration as you learn from your own application monitoring.
Architecture
How FlagPilot
fits together.
A clear division between the product interface, processing layer, and the systems your team already owns.
01Native evaluation
Typed flags evaluate in the app from verified, cached configuration.
02Control service
Projects, environments, segments, rollouts, and change approvals live in your self-hosted console.
03Safe refresh
ETags, signed responses, polling controls, and local defaults protect startup and offline behavior.
Technical profile
Built for integration,
not a closed box.
Trial onboarding confirms the exact environment, product boundary, and success criteria for your implementation.
Platforms & surfaces
iOS / SwiftAndroid / KotlinFlutterREST management API
Connects with
DebugStreamEventPulseCI/CD webhooksSSO / team roles
Flag typesBoolean, string, number, JSON
TargetingEnvironment, version, segment, percentage
Offline behaviorBundled defaults + last verified cache
Change controlHistory, comparison, rollback
DeliverySelf-hosted HTTPS endpoint
Security & control
Deliberate boundaries
from the beginning.
- Separate development, staging, and production environments
- Client-safe values only; server secrets are never distributed as flags
- Signed configuration responses and scoped management tokens
- Change history with role-aware production controls
Who it's for
Made for real workflows.
Mobile product teams
For teams planning measured introductions of new functionality across app versions.
Development agencies
For agencies that need separate settings and controlled release steps for client applications.
Internal app owners
For business applications where different departments need different feature access.
Guided product trial
Evaluate FlagPilot
against real work.
We scope the trial around one meaningful workflow, the environments you use, and evidence your team can assess.
- 01
Select one application and two release scenarios
- 02
Integrate the SDK with explicit defaults
- 03
Run a staged internal rollout and rollback exercise
- 04
Review evaluation telemetry and production policy
What the evaluation includes
Discuss trial access ↗Product access for the agreed scope, technical onboarding, implementation guidance, and a review of the findings.
A few answers
Explore with confidence.
A closer look at the scope and trial experience for FlagPilot.
How can I try FlagPilot?
FlagPilot is available through a guided trial. Tell us about your requirements, platform, and evaluation goals; our team will discuss fit, access, and the right trial scope with you.
Could FlagPilot ship new executable code into my app?
No. The scope is configuration and feature decisions for functionality already included in your app. App updates and platform review requirements still apply.
Can a flag change reach an offline device immediately?
No. The SDK can use local defaults or cached configuration until it reconnects and receives an update.
Explore FlagPilot
Bring us your
real workflow.
Share your platform, requirements, and evaluation goals. We'll discuss the product and arrange a focused trial where it fits.