Skip to main content

Sunset FAQ

Why Remote is sunsetting Bravas?​

To better serve our customers, Remote is refocusing on its core international employment products, including payroll, Professional Employer Organization (PEO), Employer of Record (EOR), and Contractor of Record (COR). (See the official announcement here).

As part of this shift, we’re sunsetting Bravas.

Why is this happening so soon after the acquisition?​

After careful consideration, Remote has decided to refocus its product investment on its core offerings. This was a difficult decision. We are giving customers 2 months of continued access and will remain available for support throughout that period. The last day to access Bravas is July 24.

What are the contractual terms for this shutdown?​

This change complies with Section 6 of the Bravas’ Terms and Conditions, which provides for termination by either party with two-months notice. All customers were officially notified via email on May 18, 2026.

What’s the impact for me as a Bravas’ customer?​

All customers must remove Bravas from production no later than July 24, 2026. All tenants will be unavailable from that that time:

  • Both identity and device management services will be stopped on that date.
  • All services still connected to your Bravas IdP will be inaccessible.
  • Any Apple endpoints still enrolled through automated enrollment will be impossible to migrate.

Do you recommend any alternative?​

To avoid disruption, we recommend transitioning to an alternative solution that fits your needs.

For MDM

Our primary recommendation is to engage an IT consultant/partner to support your transition. Additionally:

  • If your company primarily uses Apple devices and manages fewer than 30 devices, you can consider Mosyle Business (free for up to 30 devices).
  • If you use both Apple and Microsoft devices, you can explore Iru or NinjaOne.
  • If you prefer a France-based provider, you can consider Appaloosa.

For IdP

  • We recommend working with an IT consultant to support your transition. Google and Microsoft both offer IDP solutions that can replace the functionality previously provided by Bravas.

How to migrate out of Bravas device management (MDM)?​

To migrate away from a device management solution, you’ll either need a new MDM to move to or you’ll need to stop using MDM.

Migrating Windows endpoints​

For Windows endpoints, you will need to manually unenroll each device:

  1. You can do this from the Bravas console: in the IT Fleet view (Operate tab), select your Windows devices and, using the lifecycle option, indicate that the devices are leaving the enterprise and choose not to wipe them.
    1. This will unenroll the devices without affecting data.
  2. You can also do this from the Windows device itself: open the Windows menu, launch the Settings app, then go to Accounts > Work or school access and request unenrollment from the device management server.

Once unenrolled, follow the manual enrollment process for your next MDM.

Migrating iOS and macOS endpoints enrolled with Apple Business Manager​

For all iOS and macOS devices enrolled with Apple Business Manager (having a circled A in the inventory) you must unenroll the device from the MDM if you want to stop using any MDM, or use the Apple Business Manager based migration process to move to another MDM.

Full unenrollment​

If you do not want to use another MDM, unenroll the device from the Bravas console:

  • In the IT Fleet view (Operate tab), select your iOS and macOS devices and use the lifecycle option.
  • Inform Bravas that the devices are leaving the enterprise and choose not to wipe them.
  • inform Bravas that the devices are leaving the enterprise and chose to not wipe them.

IMPORTANT: It’s essential to unenroll from Bravas if you don’t plan to use another MDM soon. Otherwise, you won’t be able to unenroll manually from the device without losing all data.

Migration to another MDM​

For all endpoints running iOS and macOS 26, you can orchestrate a migration at scale using the built-in Apple process documented here: https://support.apple.com/guide/deployment/dep4acb2aa44/web

Migrating iOS and macOS endpoints enrolled in self-service​

For all iOS and macOS devices enrolled in self-service (with a circled S in the inventory), you can unenroll the device either from the MDM or directly from the device:

  1. In the Bravas console, go to the IT Fleet view (Operate tab), select your iOS and macOS devices, and in the lifecycle options indicate that the devices are leaving the enterprise and choose not to wipe them.
  2. Alternatively, on the device, open the Settings app, go to General > Device Management, and choose to leave the device management service.
  3. Once unenrolled, follow the manual enrollment process for your next MDM.

How to migrate out of Bravas’ identity management (IdP)?​

Migrating out of Bravas’ IdP is a critical process to follow.

Not migrating in time will prevent you to access your production infrastructure after July 24, 2026.

You can audit the list of connect app by going to the Bravas’ admin console, in the Configure tab, and in the Catalog section.

From here using advanced filter, display apps with identity sync or password less authentication enabled.

For each of the you will need to follow this abstract list of operations:

  • on the service provider side, read the documentation to disconnect your organization from an IDP
  • ensure that you have a clear documented process to move to another IDP or to re-issue password based access for all your users
  • disable the SSO for some users if your service provider support partial federation and confirm your process works
  • disable SSO for everyone and confirm everything is good
  • then in Bravas you can delete the app from the catalog
  • and finally cleanup all configuration leftover on your service provider

IMPORTANT: Be absolutely sure not to delete Bravas accounts before removing all apps from your catalog; otherwise, you may delete accounts on your service provider and lose related data.

What is the impact on my compliance level?​

If you are ISO27001 or SOC II compliant, this is a major change because Bravas was part of your compliance framework. You need to review your internal processes and documentation, replace Bravas with an alternative, and complete a new audit.