Roger Dewey has spent much of his career staring at the small gap between two enormous industries. On one side are mobile operators, built to sell connectivity. On the other are companies that want tractors, payment terminals, motorcycles, meters, cameras, and cargo trackers to remain connected without hiring a telecom priesthood. The gap is where ordinary things go expensively wrong: a device clings to a public network beside a cheaper private one, a credential expires in the field, or a technician drives three hours to restart a box that should have restarted itself.
Able Device's answer fits beneath a thumbnail. A SIM is not merely a serial number in plastic. It contains a processor, hardened memory, a clock, and secure input and output. It can run Java Card software and receive updates over the air. Dewey's Raleigh company built SIMbae - short for SIM-based application engine - to turn that overlooked hardware into an independent rules engine. When a defined event occurs, the applet takes a defined action. It can inspect network conditions, switch identities or networks, protect keys, run diagnostics, reset a device, and report what happened.
That distinction sounds small until a fleet leaves the lab. Cloud software can advise a device to move. An operating system can expose a setting. A user can tap a button. SIMbae sits lower in the stack, inside the secure element that identifies the device to the network, and is designed to enforce the rule without depending on any of them. The company's current shorthand is admirably blunt: AI can predict; SIMbae enforces.
The product is a rulebook with unusually good real estate
SIMbae is sold to the people who control connected fleets and connectivity: enterprises, mobile operators, MVNOs, private-network providers, SIM vendors, and manufacturers. The applet runs on a standard SIM, eSIM, or eUICC and uses established telecom standards. Able Device supplies a common engine, prebuilt capabilities, and no-code or low-code templates. Customers configure chains of events and actions instead of beginning every feature with a scarce Java Card developer and a blank screen.
The menu is practical rather than glamorous. A logistics device can prefer a private warehouse network and fall back to public cellular outside. A payment terminal can monitor quality of service and revert when a new profile performs badly. A remote device can collect diagnostics or restart. A connected vehicle can keep cryptographic credentials inside the SIM's tamper-resistant memory. Policies and applets can change over the air, so a deployed fleet does not need a firmware visit for every new rule.
The four-beat SIMbae loop
Observe → decide → act → update
What failed first was control
The useful enemy in Able Device's story is not a rival logo. It is the first operational assumption to break. Coverage can exist while a device stays attached to the wrong network. The network can look healthy while the application feels slow. A product can ship securely and later become impossible to diagnose. Traditional SIMs authenticate; device firmware and cloud systems do most of the thinking. That division leaves blind spots precisely where the device experiences the network.
A BICS executive offered a clean example in an Able Device interview. When a device uses public data outside the expected bundle, a single instance can cost around EUR25. One mistake is an annoyance. Ten thousand are a procurement meeting. SIMbae lets a customer define when a device should use private connectivity, when it may fall back, and when it should return - then applies the logic at the SIM.
The fleet-math trap
Illustrative scaling at EUR25 per eventSecurity produces a similar failure. In a next-generation electric-motorcycle engagement, the customer needed trustworthy maintenance access and protected credentials at scale. The conventional answer was another proprietary security chip, with another line on the bill of materials and another component to deploy. Able Device used the SIM/eSIM secure element already present. That did not make security free, but it removed dedicated hardware and made updates portable across supported SIM vendors.
“They just put a little bit of software on the SIM, and boom, it's taken care of itself.”Roger Dewey, describing the idea to GrepBeat in 2023
The long wait was part of the product
Able Device was founded in 2010 and passed through Durham's Startup Factory accelerator in 2012. SIMbae reached global commercial availability in 2016. The company demonstrated with Janus Remote Communications and Limitless Mobile at GSMA Innovation City in 2017, landed work with Transaction Network Services, and appeared in a GSMA credential-security case study in 2018. Then came a 2019 IoT Evolution Expo security award and a third-generation, vendor-independent architecture in 2020.
This was not a tidy overnight curve. Dewey told GrepBeat in 2023 that it had taken time to get the ball rolling. The market had to acquire the problems his architecture was built for. Enterprises began installing private 4G and 5G networks. eSIMs made identity and lifecycle management strategic. Connected vehicles needed security that could survive a long product life. Fleets crossed more network boundaries. By 2022, Able Device had announced commercial work with LiveWire, Harley-Davidson's electric-motorcycle business, and a partnership with Belgian connectivity provider BICS.
That is what changed the conversation. The SIM stopped looking like an obscure place to run code and started looking like the one component guaranteed to be present at the disputed border between device and network. SIMbae 3.0, announced in 2023, packaged its state machine with scripts and templates. The 2026 release adds context from cellular radio conditions, Wi-Fi, positioning, and proximity, then lets the applet enforce human-authored or AI-generated policy. A 2025 eSIM Innovation Award gave the patient thesis a neat plaque.
Where it sits - and what it charges
Able Device is a B2B software company in the narrow seam between IoT connectivity management, secure-element software, device lifecycle tooling, and edge automation. Its alternatives are custom Java Card projects, SIM-platform suites from large identity vendors, cloud connectivity dashboards, and logic built into device firmware. SIMbae's difference is architectural: one configurable “super applet” consolidates functions and executes inside the secure element across supported vendors.
The business appears to combine software licensing with implementation, customization, integration, white-label arrangements, and support. The site routes buyers to demos and consultations, not a checkout page, and it does not publish list prices. That makes sense for standards-heavy deployments involving operators and secure OTA access, although it also means buyers cannot calculate payback from a public rate card. The economic case must be built from avoided hardware, shorter development cycles, fewer field visits, lower roaming costs, and new services.
The customers named publicly are revealing: BICS, LiveWire/Harley-Davidson, Transaction Network Services, Janus, Limitless Mobile, and ZARIOT. Other case studies describe a global payment processor and a Belgian communications provider without naming them. This is infrastructure sold through credibility and integration, not a self-serve SaaS funnel.
The idea worth stealing
- Inventory every mandatory component in your customer's system. Ask which already has compute, memory, trust, and an update channel.
- Find the repeated specialist work. Turn the common portion into an engine and expose the variation as templates or rules.
- Sell the avoided system, not just the new feature: no added chip, fewer truck rolls, less custom firmware, and less cloud dependence.
- Use standards as distribution. Vendor independence matters more when a device fleet outlives a supplier contract.
The conditions hiding under “no new hardware”
There is no magic SIM dust. The buyer needs control of the SIM or eSIM applet environment, compatible Java Card and SIM Toolkit capabilities, a secure over-the-air path, and cooperation from the relevant operator or connectivity provider. A consumer with a locked carrier SIM cannot simply install SIMbae. An enterprise that treats connectivity as an undifferentiated monthly bill may lack the authority to deploy it.
The fleet owner cannot load applets, manage keys, or coordinate OTA changes with its SIM and connectivity partners.
The job needs rich analytics, large models, or heavy computation better handled by a device CPU or cloud platform.
The fleet is small, rarely moves, and has cheap fixed connectivity, so integration costs outweigh avoided failures.
The deployed secure elements lack required interfaces or behave inconsistently across the chosen vendor estate.
Even when it fits, the product complements rather than replaces cloud analytics, device software, and network management. SIMbae is an executor with some unusual senses, not an all-purpose IoT operating system. That narrower claim is more convincing. Connected fleets do not need another dashboard telling them a device chose badly. They need the device to choose better the next time.
Able Device's story is ultimately a lesson in technical timing. The company did not discover a new chip. It noticed that a mature, globally distributed, standards-based chip had been assigned too little responsibility. Then it spent 16 years building the software and waiting for the rest of telecom to need the same thing. In infrastructure, being early can look exactly like being wrong - right up to the moment every customer acquires your problem.