The BlackBerry name remains prominent in enterprise mobile security circles in 2026, but the hardware picture has fundamentally changed.
By 2024, that licensing arrangement had effectively collapsed, leaving enterprises that valued BlackBerry-branded hardware without a clear upgrade path.
Understanding the current state of BlackBerry hardware requires separating the hardware brand from the software and services businesses, which continue to operate independently and serve large enterprise and government customer bases. This analysis covers both dimensions — the hardware picture as it stands in 2026, and what enterprise IT teams that once relied on BlackBerry devices now deploy.
The Current State of BlackBerry Hardware (2026)
As of 2026, no actively sold, newly manufactured smartphone carries genuine BlackBerry hardware brand licensing from an active partner. The devices available in secondary markets — TCL-manufactured BlackBerry Key2, Key2 LE, and Passport SE models — run Android versions that no longer receive security patches and are unsuitable for enterprise deployment from a compliance standpoint. Any organization still running TCL-era BlackBerry devices in a managed fleet is operating hardware outside its support window.
The BlackBerry brand in the mobile hardware context now functions as legacy inventory. IT procurement teams asking about "BlackBerry hardware" in 2026 are typically asking one of two questions: what is available that provides similar capabilities (physical keyboard, high security bar, government certification), or how do they migrate their existing BlackBerry UEM policies to devices from a current OEM.
Both questions have answers — but they do not involve newly purchased BlackBerry-branded smartphones.
What Happened to BlackBerry-Branded Devices?
BlackBerry's exit from hardware manufacturing happened in stages. Research In Motion announced in 2016 that it would stop designing BlackBerry-branded hardware itself, licensing the brand and security software suite to device partners. TCL Communication Technology signed the first major hardware licensing agreement and began producing BlackBerry-branded Android devices starting with the BlackBerry KEYone in 2017.
TCL's partnership covered five years of production, yielding the Key2 (2018), Key2 LE (2018), 5G (2020), and several additional models. In August 2020, TCL announced it would not continue the BlackBerry device brand license beyond 2020. TCL ceased manufacturing and sales of new BlackBerry smartphones in late 2020, with inventory sales continuing into early 2021.
OnwardMobility subsequently announced a licensing agreement to produce new BlackBerry Android devices with physical keyboards, targeting enterprise and government markets. The company raised funding and announced a 5G BlackBerry keyboard phone for 2021. However, OnwardMobility failed to bring any device to market.
In 2022, the company announced it was shutting down without having shipped a product, citing manufacturing and supply chain difficulties. The BlackBerry hardware licensing track effectively ended there.
BlackBerry Limited confirmed in January 2022 that legacy BlackBerry OS, BBOS, and BlackBerry 10 devices — all first-party hardware — lost service functionality (network connectivity, data routing through BlackBerry's infrastructure). This date marked the formal end of operational support for any original BlackBerry-manufactured device.
BlackBerry Software on Third-Party Hardware
The separation of hardware from software is the key to understanding what "BlackBerry" means in enterprise mobility in 2026. BlackBerry Limited pivoted aggressively to software and services, and those businesses are operationally active and financially significant.
BlackBerry UEM (Unified Endpoint Management) — the successor to BlackBerry Enterprise Server — manages iOS, Android, macOS, Windows, and legacy BBOS devices. It runs on OEM hardware from Apple, Samsung, Google, Zebra, and any other Android Enterprise-compatible manufacturer.
UEM 12.19 and 12.20 releases in 2025 and 2026 added new configuration profile keys for iOS 17/18 and Android 14/15, and BlackBerry maintains compatibility tables for each new OS release from major OEMs.
BlackBerry SecuSUITE for Government provides encrypted voice and messaging on standard iOS and Android devices. It does not require BlackBerry-branded hardware and is certified for use on specific Samsung Knox-validated and iOS devices. The NSA Commercial Solutions for Classified (CSfC) program has evaluated SecuSUITE, making it relevant for US government classified communication requirements.
BlackBerry Cylance provides AI-based endpoint protection and is available on standard MDM-managed devices as a managed application. For enterprises whose BlackBerry investment is primarily in the security software stack, the transition away from BlackBerry hardware need not mean abandoning the broader BlackBerry security ecosystem.
Samsung Knox: The Enterprise Hardware Alternative
Samsung Knox has become the most direct successor to BlackBerry-branded devices in regulated enterprise environments. Samsung's Galaxy Enterprise edition devices — the S-series, XCover, and Tab Active lines — carry Knox Validated certification and meet or exceed the security baseline that BlackBerry-branded TCL devices once provided.
Knox's architecture provides hardware-backed security through a dedicated Secure Enclave (Knox Vault on newer devices), which stores cryptographic keys and biometric data isolated from the main application processor. Real-time Kernel Protection (RKP) monitors kernel integrity at runtime, detecting and blocking rootkit-style attacks.
Samsung Knox Platform for Enterprise (KPE) extends MDM configuration depth with thousands of additional policy keys beyond standard Android Enterprise APIs — covering display restrictions, network configuration, application-level controls, and hardware-level lockdown parameters that are relevant in kiosk and task-worker deployments.
Knox-validated devices support all major MDM platforms including BlackBerry UEM, enabling organizations to maintain their UEM investment while transitioning the physical hardware layer.
Samsung's Galaxy for Enterprise program commits to four years of OS updates and five years of security patches for devices in the program — a more transparent support commitment than TCL-era BlackBerry devices ever provided.
For government customers with DoD or NSA requirements, Samsung Knox Cryptographic Module holds FIPS 140-3 validation, and the Galaxy S and XCover lines appear on several government-approved products lists. The Samsung Knox platform has been evaluated under Common Criteria at EAL2+ for specific configurations.
Zebra Technologies and Rugged Enterprise Devices
For enterprise deployments in environments that demand rugged certification — warehousing, field services, utilities, logistics, and industrial applications — Zebra Technologies represents the leading option in 2026. Zebra's TC series (TC52, TC57, TC73, TC78) covers a range of environmental ratings from IP65 to IP67, with drop specifications ranging from 1.2 meters to 2.4 meters across product families.
Zebra devices run Android Enterprise and are Android Enterprise Recommended across their product catalog. Zebra's Mobility DNA software suite adds a management and application layer on top of stock Android Enterprise, providing additional controls relevant for task-worker and kiosk deployments.
Zebra's LifeGuard for Android program commits to extended security patch support, with some enterprise-tier devices receiving patches through Android release n+3 — meaningfully extending the compliant deployment window beyond Google's standard Android support lifecycle.
For organizations migrating from BlackBerry-branded rugged devices, Zebra's MDM compatibility includes native integration with BlackBerry UEM through standard Android Enterprise APIs. Zebra also offers direct Intune integration through Microsoft's Android Enterprise framework. The TC52ax and TC73 are the current mid-range enterprise targets; the TC78 targets harsh-environment deployments with extended temperature ratings.
Honeywell's Dolphin CT series (CT45, CT47) occupies a similar market position, with Android Enterprise Recommended devices and a strong position in healthcare, retail, and utilities. Honeywell's enterprise support commitments through its Operational Intelligence platform include extended patch coverage aligned with enterprise procurement cycles rather than consumer-tier release schedules.
What Enterprise Teams Ask About BlackBerry Hardware in 2026
The most common question from enterprise IT teams concerns physical keyboard availability. BlackBerry's QWERTY keyboard was a differentiating factor for specific user populations — intensive text workers, government analysts, and users with accessibility requirements that made touchscreen-only devices impractical.
The honest answer in 2026 is that no enterprise-certified, currently manufactured smartphone with a full physical QWERTY keyboard exists at scale. The Unihertz Titan series provides a keyboard form factor on Android but does not carry enterprise certification, FIPS validation, or a credible enterprise support track.
For most organizations, the practical path involves adapting workflows — supplementing touchscreen devices with Bluetooth keyboard accessories for desk-bound users, or transitioning keyboard-dependent users to tablet-plus-keyboard configurations running fully managed Android Enterprise or iOS with supervised enrollment.
The second common question concerns security equivalence. IT security teams that relied on BlackBerry's end-to-end encryption and NOC routing for device communications want to understand whether current alternatives provide comparable protection. The answer depends heavily on the specific threat model.
For organizations whose concerns center on MDM policy enforcement, application isolation, and data-at-rest encryption, Samsung Knox-validated devices with BlackBerry UEM or Microsoft Intune provide a demonstrably auditable security posture. For classified communications requirements, BlackBerry SecuSUITE on evaluated hardware provides a validated alternative to the legacy BlackBerry OS encryption model.
Hardware Security Certifications: What to Look For
Enterprise procurement teams evaluating mobile hardware in 2026 should verify the following certification chain before committing to a device platform. First, FIPS 140-3 validation — confirm the device model and firmware version appears on NIST's Cryptographic Module Validation Program (CMVP) list with an active certificate, not a historical certificate for a prior firmware version.
Second, Android Enterprise Recommended status — verify the specific SKU in the Android Enterprise Solutions Directory, including the listed security patch cadence commitment and supported deployment scenarios. Third, for Samsung devices, Knox Validated status for the specific Knox version and configuration being deployed.
For government and regulated-industry procurement, Common Criteria certification and NIAP approval lists provide the definitive reference. NIAP's Approved Products List (APL) covers mobile device fundamentals and BYOD separation profiles for devices approved for US government use. DoD component purchases additionally reference the DISA Approved Products List (APL), which is a downstream curation of NIAP evaluations plus additional DISA-specific review criteria.
IT procurement teams should track certification expiration dates. FIPS 140-3 certificates carry defined validity periods and must be renewed when firmware or cryptographic implementations change. A device may be listed on the CMVP with an expired certificate for the current firmware version — meaning the device in a current production run has not been re-evaluated.
Procurement teams should request the current active certificate number from the OEM's enterprise sales team and verify it against the CMVP database before finalizing purchasing decisions.
Frequently Asked Questions
Can organizations still buy new BlackBerry-branded smartphones in 2026?
No. As of 2026, no manufacturer holds an active BlackBerry hardware brand license for new device production. TCL's license ended in 2020. OnwardMobility's announced device never shipped, and the company closed in 2022. BlackBerry Limited itself exited hardware manufacturing in 2016. New BlackBerry-branded smartphones are not available from any authorized retail or enterprise channel. Devices appearing on secondary markets are legacy inventory from the TCL manufacturing period and do not receive security updates.
What MDM platforms support managing former BlackBerry device users as they migrate to new hardware?
BlackBerry UEM supports managing iOS, Android, macOS, and Windows devices — migration from BlackBerry OS or BlackBerry 10 devices to Android Enterprise or iOS devices within the same UEM console is a documented and supported migration path. Microsoft Intune, VMware Workspace ONE, and SOTI MobiControl also support the full range of current Android and iOS managed enrollment modes. For organizations moving from BlackBerry OS or BlackBerry 10 managed by a legacy BES, the recommended path is to migrate the BES infrastructure to BlackBerry UEM first, then transition the endpoint devices, rather than changing both simultaneously.
Are Samsung Knox-validated devices compatible with BlackBerry UEM?
Yes. Samsung Knox-validated devices running Android Enterprise are fully compatible with BlackBerry UEM through standard Android Enterprise APIs. BlackBerry UEM additionally supports Samsung Knox-specific policy keys through the Samsung Knox Service Plugin (KSP), enabling deeper configuration than standard Android Enterprise APIs allow. Organizations deploying Samsung hardware under BlackBerry UEM management can enforce Knox-specific controls — hardware-level restrictions, Knox container policies, and Per-App VPN configurations — through the UEM console without requiring a separate Samsung Knox management platform.
What is the security difference between Android Enterprise fully managed and Samsung Knox-managed devices?
Android Enterprise fully managed (also called Device Owner mode) places the entire device under MDM control — the organization owns the device profile, application installation, and policy enforcement at the OS level. Samsung Knox adds a hardware-backed security layer on top of this: Knox Vault provides a physically isolated secure enclave for key storage and biometric data; Real-time Kernel Protection monitors kernel integrity at the hardware level. For regulated environments, Knox-managed devices under Android Enterprise fully managed mode represent a meaningfully higher security posture than standard Android Enterprise on non-Knox hardware, because the cryptographic operations and key storage are hardware-isolated rather than software-isolated.
What happened to BlackBerry's encrypted messaging and communications services?
BlackBerry Messenger (BBM) as a consumer product was shut down in 2019. BlackBerry's enterprise communications products — primarily BlackBerry SecuSUITE for Government — continue to operate as a software-only platform running on evaluated iOS and Android hardware. SecuSUITE provides NSA-evaluated encrypted voice and messaging for classified environments and is deployed on standard managed smartphones without requiring BlackBerry-branded hardware. For civilian enterprise encrypted messaging, the product is marketed through different packaging but operates on the same technical foundation.
Which rugged enterprise device makers provide the longest security patch support windows?
Zebra Technologies' LifeGuard for Android program offers the most extended support commitments in the rugged segment, with select TC-series devices receiving security patches for up to five years from device launch, and enterprise support contracts available beyond that. Honeywell's enterprise support program commits to patch availability through enterprise contract terms. Samsung's Galaxy for Enterprise program provides five years of security patches from device launch. Google Pixel devices offer seven years from launch under the Android 14+ commitment, but Pixel devices are not typically deployed in rugged environments. For procurement planning, request the stated EOL date for security patches from the OEM's enterprise sales team in writing — this is a distinct and later date from the OS version update EOL.
How does Zebra Technologies compare to BlackBerry-branded devices for regulated industry deployments?
Zebra devices in the TC-series carry IP65-IP67 ratings and MIL-STD-810H certification for drop, temperature, humidity, and vibration — specifications that BlackBerry-branded consumer-class devices did not meet. For regulated industry deployments in field services, utilities, or industrial environments, Zebra devices are a better physical match than any consumer-tier smartphone. On the security certification side, Zebra TC-series devices carry Android Enterprise Recommended status. FIPS 140-3 validation depends on the Android OS cryptographic module validation, which follows Google's Android release cycle. Zebra devices do not carry Samsung Knox's hardware-backed security enclave, so for organizations whose regulatory requirements include Knox-specific controls, Samsung XCover devices represent a closer comparison point than Zebra for non-extreme-environment rugged use cases.
What enterprise device options exist for users who require a physical keyboard on a smartphone?
No enterprise-certified smartphone with a built-in physical QWERTY keyboard is currently available from a major OEM. The Unihertz Titan Pocket and Slim provide physical keyboards on Android but do not carry enterprise security certifications, FIPS validation, or multi-year security patch commitments from the manufacturer. For enterprise deployments requiring intensive text input, the practical options are: foldable devices (Samsung Galaxy Z Fold series, which runs Knox) paired with a Bluetooth keyboard case; tablet configurations with detachable keyboards under fully managed Android Enterprise or supervised iOS; or standard touchscreen smartphones with Bluetooth keyboard accessories. Organizations with genuine accessibility requirements for physical keyboards should engage their MDM vendor's accessibility accommodation guidance, as exception processes exist for specialized hardware in most enterprise frameworks.
Does BlackBerry UEM still receive active development and enterprise support in 2026?
Yes. BlackBerry UEM is an actively developed product in 2026. BlackBerry Limited publishes release notes for UEM updates on a regular cadence. UEM 12.19 and 12.20 shipped in 2025 and early 2026, respectively, adding support for iOS 18 MDM configuration profile keys, Android 15 enterprise enrollment changes, and updated compatibility for Samsung Knox Platform for Enterprise. BlackBerry maintains documented compatibility matrices for UEM against current iOS, Android, macOS, and Windows releases. Enterprise support contracts for UEM are available through BlackBerry's direct sales organization and authorized channel partners, with support tiers ranging from standard business hours to 24/7 critical-incident response.
Are BlackBerry OS and BlackBerry 10 devices still usable in enterprise environments in 2026?
No. BlackBerry Limited terminated network services for BlackBerry OS, BBOS, and BlackBerry 10 devices in January 2022. This means legacy first-party BlackBerry-manufactured devices can no longer connect to BlackBerry's infrastructure for device routing, messaging, or management communications. From a security standpoint, these devices also no longer receive security patches. Operating BlackBerry OS or BlackBerry 10 devices in a managed enterprise environment is indefensible from a compliance perspective — they represent unpatched endpoints with no remaining security update path. Any organization still carrying these devices in an active fleet should have completed migration before the January 2022 service termination date.
Conclusion
The BlackBerry hardware chapter in enterprise mobile is closed. The brand, once synonymous with secure enterprise communications, produced its last genuinely current licensed devices through TCL in 2020. No new BlackBerry-branded smartphones exist for enterprise procurement in 2026, and no active licensing partner is known to be developing them.
What remains of the BlackBerry enterprise security ecosystem — UEM, SecuSUITE, Cylance, and related software products — is operationally active and continues to receive development investment. Organizations that built their mobile security posture on BlackBerry's software and management infrastructure can maintain that investment by transitioning the hardware layer to current Samsung Knox-validated, Google Pixel, Zebra, or Honeywell devices.
For enterprise IT procurement teams, the actionable path forward is hardware-agnostic: define the security certification requirements, determine the environmental operating specifications, verify the MDM compatibility matrix against the chosen platform, and select hardware that meets those criteria — whether from Samsung, Zebra, Honeywell, or Apple.
The BlackBerry software layer can coexist with or be replaced by any of these hardware choices. For further context on the MDM management layer, see the enterprise mobility management coverage and the BlackBerry UEM guide.