EDGEOTA HAS MOVED TO RENBO.DEV
The console and API now live on ota.renbo.dev and api.ota.renbo.dev. The old ota.renbo.site domain stays online as a fallback, so no published update, device or account is affected. Move at your own pace.
MIGRATION CHECKLIST
Update your bookmark
The console moved. Sign in as usual — accounts, projects and keys are unchanged.
https://ota.renbo.dev
Point app.json at the new API
Set both fields, then rebuild native projects so the URL is baked into the binary.
"expo": {
"updates": {
"url": "https://api.ota.renbo.dev/api/projects/<projectId>/updates"
},
"extra": {
"edgeOtaServer": "https://api.ota.renbo.dev"
}
}Rebuild + refresh the CLI
A new native build is only required to move new installs. Already-installed apps keep working through the legacy endpoint.
npx expo prebuild --clean npm i -g @renbostudios/edge-ota@latest && edge-ota login
FAQ
Will my app break if I do nothing? +
No. api.ota.renbo.site stays online and keeps serving devices, and the CLI keeps pushing to it. Nothing is being shut off today.
Do I need a new App Store / Play Store build? +
Only to move new installs onto the new API hostname. Devices running your current binary keep receiving OTA updates through the legacy endpoint.
Why renbo.dev? +
renbo.dev is the permanent home for Renbo developer products. Keeping the console and API on one clean domain makes webhooks, docs and device URLs predictable.
What happens to my account and keys? +
Nothing. Users, projects, releases, channel history and ECDSA keys carry over as-is — same database, same signing keys.
Questions? hello@renbostudios.com · EdgeOTA by Renbo Studios