Sign in to SimpleOS

Simple Intelligence Group

One command surface for the products your operation already uses.

SimpleOS includes approved product modules in one portfolio view. It does not merge product databases, bypass each product's controls, or claim access the entitlement service cannot verify.

Product walkthrough

How the shell works

  1. 01

    Start with the workspace

    A signed-in person selects the workspace they are authorized to use. The shell uses that context only to request portfolio access for the active tenant.

  2. 02

    See confirmed module access

    The dashboard shows the portfolio and marks access only when the shared entitlement service confirms an active grant for that tenant.

  3. 03

    Work in the included module

    Selecting an available module opens the product on its own origin. The shell composes access without sharing session secrets or replacing the product database.

  4. 04

    Keep human controls where work happens

    Approvals, customer writes, and evidence records stay with the owning product. The shell does not bypass them.

Accessible text

Walkthrough transcript

1. Start with the workspace. SimpleOS begins with a workspace. Your active tenant determines the access request. It does not grant access by itself.

2. See confirmed module access. The dashboard is a portfolio map. An unavailable or malformed entitlement response leaves a module locked. Each module checks access again before customer work opens.

3. Work in the included module. SimpleOS includes product modules in one surface. Projects stay in Simple Projects, time stays in Simple Time, and customer data is not copied into the shell.

4. Keep human controls where work happens. The shell includes the right product in the operator experience. It cannot approve a customer action, perform a customer write, or manufacture an audit record.