Skip to main content
Early accessBeta, invite only since 1 Nov 2026. A person reads every application.Apply for an invite
Demystify OS

Demystify Business OS Guide

Know the terms and check the basis

Understand the work, choose your controls, and see what comes next.

Early access

This guide explains Demystify OS using the current public product, pricing and security pages. Its glossary separates worker roles, approval tiers, deployment choices and evidence. Earlier guide estimates are not current prices or results. Ask for dated evidence for the capability and deployment you need; the guide was reviewed on 4 November 2026.

Updated 4 November 2026. Early access: invite-only beta since 1 November 2026.

Sources and glossary: the approach, step by step

  1. Read the status

    Early access describes the beta. Building now describes work underway. Provisioned on request needs an agreed deployment scope.

  2. Check the basis

    A role definition, design or forecast is different from a measured run. Ask for a source and date.

  3. Confirm the fit

    Review the current pricing, security and deployment scope before relying on a statement for your business.

Read the diagram as a list
  • Read the status: Early access describes the beta. Building now describes work underway. Provisioned on request needs an agreed deployment scope.
  • Check the basis: A role definition, design or forecast is different from a measured run. Ask for a source and date.
  • Confirm the fit: Review the current pricing, security and deployment scope before relying on a statement for your business.
  1. Read the status

    Early access describes the beta. Building now describes work underway. Provisioned on request needs an agreed deployment scope.
  2. Check the basis

    A role definition, design or forecast is different from a measured run. Ask for a source and date.
  3. Confirm the fit

    Review the current pricing, security and deployment scope before relying on a statement for your business.
How do I join?

Apply for the invite-only beta. A person reads every application. The beta began on 1 November 2026.

When is Community planned?

Public launch and the Community edition are targeted for 1 January 2027. Plans change; dates are targets, not promises.

Is Demystify OS certified?

Designed with ISO 27001 and SOC II in mind. Not certified. Audit readiness is planned for Q1 2027.

Public sources and market context

Use the linked product, pricing, security, integrations and privacy pages for public terms. Internal planning documents are not customer evidence. Older market-size estimates, comparisons, revenue forecasts and unsupported connector totals are omitted rather than represented as current facts.

Demystify OS and Business OS

Demystify OS is the product; Business OS describes the category. Cloud, Private and Community describe deployment choices. Community is targeted for 1 January 2027.

Mysty, Mysty Desk and Mysty Workers

Mysty is the assistant. Mysty Desk is the work surface. Mysty Workers are defined AI roles in early access, with intended responsibilities and review boundaries. Fictional worker personas are not human staff or proof of autonomous operation.

Mysty Pod, department and principal

Mysty Pod describes the Private deployment. A department groups worker responsibilities. A principal is a person or identity with an agreed role and permissions; it does not automatically have authority to approve everything.

Mysty credits and deployment terms

Credits meter AI usage. BYOC means bring your own cloud. Private scope, model charges and care responsibilities must be agreed. Published prices come from the current pricing page, not the earlier guide.

RLS, RBAC and approval tiers

RLS means row-level security. RBAC means role-based access control. R0 to R3 describe action risk and approval needs; L0 to L3 describe proposed worker autonomy. They are different concepts and must be reviewed for the deployment.

Evidence ledger and proof packs

An activity ledger records actions and decisions. Signed proof packs are a planned Assure output, not a independent attestation. A useful claim identifies its basis, source and date.

Assure, migration and the Skills Hub

Assure is the compliance direction. Migration needs a dry run, reconciliation and recovery plan. Demystify Skills Hub groups skills, routines and workflows; a browsable catalogue does not prove workspace sync or installation.

Identity, beta and customer zero

Identity controls establish who may act. Beta access is invite only, with a person reviewing applications. Customer zero refers to our own use, which must not be presented as independent customer proof.

VAPT and DPDP

VAPT means vulnerability assessment and penetration testing. DPDP refers to India's personal data protection framework. A design aligned to it does not establish independent attestation or replace a deployment-specific review.

Demystify OS: Inception to Reality

An introduction to Demystify OS

Premiere soon

Playback will be added after episode approval. No video is loaded.

Business work with human approval

Premiere soon

Playback will be added after episode approval. No video is loaded.

Search the guide and site

Next steps

Start with the task you want help with

Early access

Invite-only beta since 1 November 2026

Apply for the beta. A person reads every application and discusses the fit before an invitation. Share a short task description, without credentials or customer records.

Apply for the beta

Apply for the Demystify OS beta

After submitting, check your inbox for the confirmation link. Your application is reviewed once confirmed.

All fields are required unless marked optional.

15 characters. It helps us verify your business; you can add it later.

Tools you use today