An introduction to Demystify OS
Premiere soon
Playback will be added after episode approval. No video is loaded.
Demystify Business OS Guide
Understand the work, choose your controls, and see what comes next.
Demystify OS brings business records, Mysty Workers and approvals into one operating approach. This guide explains where it runs, how work is reviewed and what is still being built. The beta is invite only from 1 November 2026. Public launch and the Community edition are targeted for 1 January 2027.
Updated 4 November 2026. Early access: invite-only beta since 1 November 2026.
Choose one repeatable task and the records it needs. Agree what a useful result looks like before adding automation.
Mysty Workers are defined roles in early access. Review the proposed work, permissions and approval boundary before use.
Use the activity record to understand what happened. Signed proof packs and measured worker promotion remain work ahead.
Apply for the invite-only beta. A person reads every application. The beta began on 1 November 2026.
Public launch and the Community edition are targeted for 1 January 2027. Plans change; dates are targets, not promises.
Designed with ISO 27001 and SOC II in mind. Not certified. Audit readiness is planned for Q1 2027.
Current pricing comes from the shared price source. The beta is invite only. Worker roles are described without claims of measured runs, and planned capabilities carry dates or a clear planning basis.
Demystify Skills Hub brings skills, routines and workflows together. A browsable catalogue is available; workspace sync and streaming are planned for Q1 2027.
Mysty Desk is the work surface; a single brief, approvals and business context are the direction. Worker roles remain early access. Do not read a proposed screen or conversational example as proof that a workflow runs unattended.
Finocket covers books and GST; ASHR.work covers people and payroll. Mysty provides the assistant experience in early access. Assure is targeted for end December 2026. Confirm plan scope, enabled modules and access during onboarding.
A migration needs a dry run, reconciliation and recovery plan. A connection needs agreed permissions and evidence for supported operations. Neither is proven by a catalogue listing. Review the current integrations page before choosing a first workflow.
Cloud subscriptions, metered credits, Private care, scoped implementation and Assure describe different purchasing needs. Industry scope and managed services need confirmation. The Plans section uses the published price source and does not carry forward the old guide's implementation rates or revenue estimates.
Premiere soon
Playback will be added after episode approval. No video is loaded.
Premiere soon
Playback will be added after episode approval. No video is loaded.
Next steps
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.
After submitting, check your inbox for the confirmation link. Your application is reviewed once confirmed.