Most systems can't tell you which installations of their app are out there, let alone switch one off. Why that blind spot matters — and what it looks like when every installation is known, controllable and auditable.
When a user installs your app and opens it for the first time, what happens? In most systems, nothing — the app just works. Nobody decided that installation should be trusted. Nobody will notice if it shouldn't be. And if it needs to be stopped one day, there's usually no way to stop just that one.
Most security models think in terms of users and sessions. But the thing actually talking to your API is an installation: a specific copy of your app on a specific device. A user can have several. Some are on phones that were lost last year. Some are on tablets that belonged to an employee who has since left. Some aren't your app at all — just something pretending to be.
When installations are invisible, every response is blunt. You reset a password and hope. You revoke a user and lock them out of every device, including the one they're holding. You ship a fix and wait for the bad version to age out.
With Enravo Core, every installation of every app is known, from its first launch to its last request. You decide how new installations are admitted — instantly for a consumer app, only after an administrator approves it for an internal tool. And you can act on any single installation without touching the rest of the user's devices or the rest of your business.
App lifecycle management sounds like a feature. In practice it touches authentication, device management, threat response and admin workflows all at once — and if those live in different systems, they disagree at exactly the wrong moment. In Enravo Core they are one system, because security features that don't work together don't work at all.
If you can't answer 'which installations of our app can reach our data right now?', you can't control them either. Enravo Core makes that answer — and the ability to act on it — part of the platform. If that blind spot exists in your product today, talk to us.
Recent articles on platform, security, and engineering.
A platform is a claim until something real runs on it. Rakton is the first product family built on Enravo Core — and building it changed Core more than we expected.
Read moreAssembling a stack from best-in-class services is the sensible default. Here is the specific reason we did the unreasonable thing instead — and what it cost.
Read moreA tablet on a shop counter is shared, public, and occasionally offline. Designing for it forced us to rethink what device trust means when the device is not personal.
Read more