← All features
Release routing
Route OTA updates by project, environment, and app version
One OTA platform should not mix staging builds with production devices. NitroPush scopes every release to a project and environment, then matches a device using its deployment key, platform, and app version.
Separate test, stage, and production releases
Per-environment deployment keys
Platform and runtime-version targeting
How it works
01
Create a project
Give each mobile product its own release boundary and configuration.
02
Use isolated environments
Deploy to test, stage, or production without sharing environment credentials.
03
Deliver the matching release
NitroPush returns only the release compatible with the requesting app and environment.
Related resources