MasterOS문서
문서

Overview

What MasterOS is, its three editions, and the core vocabulary used throughout these docs.

이 페이지의 목차

  1. The three editions
  2. Core vocabulary
  3. Where to go next

MasterOS is an AI-native operating system, sold as a product with three editions from one codebase — not three separate products with three separate codebases. It is a control plane: it gives users safe access to multiple AI models, reusable Skills, org knowledge, and cost/governance controls, from a single account up to a full organization rollout.

The three editions

One codebase, three editions, differing only in configuration and entitlement — never in code path:

EditionDeployment modeAudience
MasterOS PersonalPublic SaaS (shared multi-tenant)Individuals, freelancers, small SMEs
MasterOS TeamDedicated SaaS (isolated multi-tenant, per subdomain)Small teams, SME / mid-market
MasterOS OrganizationPrivate / on-premise (or dedicated SaaS at larger scale)Enterprise, regulated orgs

This site currently documents MasterOS Personal — the edition that is actually shipping today. Team and Organization-specific surfaces (shared Knowledge, Role Packs, Trust Zones, on-prem licensing) are called out as roadmap items where relevant; see Architecture → Components for the full shipped-vs-roadmap breakdown.

Core vocabulary

  • Knowledge — facts, documents, and structured information (in Personal MVP: your uploaded files).
  • Skill — a reusable, named action such as writing, coding, or reviewing — save an instruction once, run it again with new input instead of retyping the same prompt every time.
  • Agent — an autonomous worker that consumes Knowledge/Memory/Skills to execute a task. Not yet available in Personal MVP (agent tool execution is a later phase).
  • Workflow — an ordered sequence of Skills. Also not yet available in Personal MVP.
  • Chat — the day-to-day surface for talking to a model, with per-message cost tracking against your quota.

Where to go next