The StoneOS App Store: apps that inherit your rules

The price on a new tool is the smallest number attached to it. The real bill arrives over the following year — in accounts, in islands of data, and in the things you can no longer see.

What a tool actually costs

Adopting software carries three costs that never appear on the invoice.

Accounts. Every tool means a set of credentials per person: created at onboarding, maintained through role changes, revoked at exit — forever, for as long as you run it. Multiply by every tool and every person, and account administration quietly becomes a standing job. Worse, every account is a door, and doors that nobody remembers are how access outlives employment.

Data islands. The tool accumulates records — customers, transactions, documents — in its own private shape. Those records do not connect to anything else you run. Ask a question that spans two tools and the answer is a manual export, a spreadsheet, and an afternoon.

Blind spots. What happens inside the tool is invisible to the rest of your operation. Someone changed a price, approved a request, deleted a record — inside that tool’s own log, if it keeps one, in a format only that tool understands. When you need to reconstruct what happened across your business, each tool is a chapter written in a different alphabet.

These costs are why prudent companies say no to good software. The tool might be worth its subscription — but not its accounts, its island, and its blind spot.

Apps that arrive under your rules

The StoneOS App Store is where your team’s apps come from: you find an app, approve the permissions it requests, and it runs under your identity, on the record. Installed apps simply appear in Launchpad — the dock, one tap away. This model removes those three costs at the root, because every app inherits three things the moment it runs.

Your identity. People use the app as themselves — the one identity they already have. No new credentials, nothing to provision, nothing to revoke separately at exit. The onboarding cost of an app rounds to zero, and so does its offboarding risk.

Your permissions. An app does not get ambient access to your operation. It requests scoped permissions — the specific things it needs to read or do — and you approve them explicitly before it runs. What the app can touch is a decision you made, written down, not a default you discovered later.

Your event history. What the app does is recorded in your event history, in the same form as everything else in your operation. An approval made inside an app from the App Store sits on the same timeline as a sale in your retail platform. No blind spot, because the app was never outside your line of sight.

An App Store you can trust by construction

The App Store is governed rather than open-ended. Publishers are verified — and the door is open: anyone can build an app with App Engine, the app foundation of Link Loom Cloud with its built-in IDE, and publish it as a verified publisher. Every app declares the permissions it needs, scoped and explicit, and nothing runs until you have approved that request. There is no app that “just needs admin access.” The trust model is not a review score — it is that you can read exactly what an app is allowed to do before it does anything.

Leaving is clean

The test of any software relationship is the exit. Remove an app and its access ends — immediately and completely. But your data stays, and your event history stays. Everything the app did remains on the record, legible, attributable, yours. What ends is what the app could do next.

Compare that to retiring a standalone tool: the export project, the orphaned accounts, the archive nobody can open in three years. Here, leaving costs a click.

The economics change

When accounts, islands, and blind spots go away, the marginal cost of adding software collapses toward its subscription price — the number you can actually see. That changes behavior. Trying an app stops being a commitment and becomes an experiment: install it, scope its permissions, watch what it does in your event history, and keep it or remove it with equal ease.

Companies on fragmented stacks are forced to be conservative about tools, and it costs them. A stack where apps inherit your rules lets you be curious instead.

Explore the App Store, see the platforms apps build on, or talk to sales about what governed apps would change for your operation.