Platform and integration · Coming soon
SimpleOS

SimpleOS
The SimpleOS family has working products. Its shared shell is still planned for customers.

For Operations and IT leaders who expect to run more than one Simple Intelligence product and want to know how those products will be reached, entitled, and administered together.

SimpleOS names the product family. SimpleOS Delivery, SimpleOS Reach and SimpleOS Desk are working products with their own applications and access paths. A shared shell is being built so an entitled customer can find those products in one place. The shell is deployed for internal review but is not open to customers. Its availability does not control access to the working products. Simple Ops remains a separate planned operational suite.

Replaces A separate sign-in for every tool A hand-maintained internal portal page A folder of bookmarks nobody keeps current
Web Planned Copilot Planned

When you can get SimpleOS

Coming soon

Not open yet. Tell us where to send word when it is.

What you can do now

Get product updates

None of these creates an account, a trial, or access. Each one records what you asked for so a person can answer it.

Where this stands

Availability
Coming soon

What it costs

Pricing is shared when access is set up.

Routes that are not open

  • Direct trial with Simple Intelligence Not open yet
  • Direct subscription from Simple Intelligence Not open yet
  • Microsoft Marketplace listing pending Not published yet
  • Sponsored subscription for member companies Not open yet

What a shell is, and what it is not.

SimpleOS is the product family. Its planned shared shell is a way in, not a place your work lives. The working products keep their own applications, their own data and their own approval seams. You can use a product without using the shell.

Why it opens products rather than containing them.

The built shell links out to each product rather than embedding or proxying it, and that is a deliberate constraint rather than a stage on the way to something else. A shell that proxies becomes a second copy of every product's permissions, and the copy is what goes wrong. Sending you to the product means the product decides what you may do, using the same rules it applies to anyone arriving directly.

How far this has actually gone.

The shell sign-in and module list work for internal review. An entitlement outage locks access. The shell does not have customer sign-up, billing or tenant provisioning, so the shell remains Coming soon. Delivery, Reach and Desk run independently of that shell.

SimpleOS is not another name for Simple Ops.

The names are a character apart. SimpleOS is a product family with a planned shared shell. Simple Ops is a separate planned operational suite.

Nothing on this list is available today. This is the product we intend to build, written down so you can tell us whether it is the right one, and it will change.

The SimpleOS shell is the surface

The family includes working products today. Its planned shell would show the products your organization has and open them.

Simple Ops is the grouping

A decision about which operational products belong together under one name. It has its own page, and nothing has been built under it.

Neither is on sale

The shell is deployed internally and closed. The suite does not exist as software. There is nothing to buy on either page.

The products run independently

SimpleOS Delivery, SimpleOS Reach and SimpleOS Desk each have their own application, access path and terms. None depends on the shared shell.

If a future version of this page describes SimpleOS as a suite you can buy, it has drifted from what was decided.

Composing products is not merging them.

The word composition does a lot of work in software marketing, so here is exactly what it is planned to mean and what it is planned not to mean.

Your data stays in the product

The shell holds no product records. Time entries, projects, deals, and tickets stay in the product that owns them, under that product's stated storage posture.

Approvals stay in the product

Arriving through the shell does not change what an agent may do or who has to approve it. The seam is the product's, and it is the same seam whether you arrived through a tile or directly.

Entitlement decides what you see

A tile you are not entitled to is locked rather than hidden, so the shell tells you a product exists and that you do not have it, which is a more useful answer than an empty screen.

Failure locks rather than opens

When the entitlement service cannot be reached, every tile locks. The failure is visible and it is on the safe side of the decision, which is the behaviour the built shell already has.

What the shell does today, and what it does not.

There is more built here than a plan and less than a product. Both halves are stated below rather than one of them.

Working today

  • A person signs in with their existing Microsoft work account
  • A module registry lists sixteen entries grouped into tiers, each carrying its own stage rather than a single suite-wide status
  • A tile opens the product's own application. The shell does not embed or proxy a product
  • Entitlement is read per tile and fails closed: when the entitlement service cannot be reached, every tile locks
  • It is deployed and in use internally for review

Not yet

  • It is not open to customers. There is no sign-up, no billing, and no tenant provisioning
  • Even internally the root address does not serve the shell, so it is reached by a specific path
  • Tiles for three of the products that are already available have not been added to the dashboard
  • There is no single tenant and no single bill across products. Each product is still bought, signed into, and billed on its own
  • There is no approved date, and none will appear here until there is one

Verified against the product on 2026-08-24.

Where each of these claims comes from.

A person signs in with the Microsoft work account they already have.
In the build Sign-in is built against Microsoft work-account identity rather than a separate username and password, and it is the only way into the shell. There is no local account to create. Checked 2026-08-24
The shell opens a product rather than embedding or proxying it.
In the build Every module in the registry carries the address of the product's own application, and the shell navigates to it. The repository states in its own words that it is not a monorepo and not a reverse proxy. Checked 2026-08-24
Entitlement is read per tile and fails closed.
In the build The entitlement read is made per module, and the failure path locks rather than grants: when the entitlement service cannot be reached, the dashboard renders every tile locked. Checked 2026-08-24
It is not open to customers.
In the build There is no sign-up path, no billing, and no tenant provisioning anywhere in the shell. The deployment is internal, its own ship record notes the root address does not serve it, and tiles for three already-available products have not been added. Checked 2026-08-24
Storage posture
None of its own. Each product reached through it keeps its own storage posture.
Certification target
Microsoft 365 certification, not held today
Distribution
Azure Marketplace (planned) · AppSource (planned)
Status
Coming soon

The questions this page exists to answer.

Can I use SimpleOS today?

The SimpleOS product family includes working products today: Delivery, Reach and Desk. The shared shell is deployed internally and is not open to customers. Each product has its own access path.

Is SimpleOS another name for Simple Ops?

No. SimpleOS is a product family with a planned shared shell. Simple Ops is a separate planned operational suite. The working SimpleOS products are available on their own terms; neither the shell nor Simple Ops is purchasable.

Does it give me one tenant and one bill across products?

Not today, and no work on that has started. Each product is bought, signed into, and billed on its own. If that changes it will be stated here as something built rather than as something intended.

What happens when I open a product from the shell?

You go to that product's own application. The shell does not embed it in a frame or proxy it, so the product applies its own permissions and its own approval rules to you exactly as it would if you had gone there directly.

What happens to my data?

The shell stores no product records. It knows who you are, which products your organization is entitled to, and where each product lives. Everything else stays in the product that owns it.

What does it do if the entitlement service is down?

Every tile locks. It fails closed rather than open, so an outage cannot hand somebody a product their organization does not have. That behaviour is built, not planned.

Delivered with Simplicity IT

Simplicity IT provides services around the products in the SimpleOS family.

Simple Intelligence Group builds the product. Simplicity IT Inc. is a separate legal entity that provides services under its own agreement.

Start with a working product.

Delivery, Reach and Desk can be accessed on their own today. The shared shell is not open to customers. Tell us which workflow you need and we will explain the access path for that product.

Availability Get product updates