Small OS
Sign in
Beta documentation

Documentation

A short orientation to Small OS — what it is, the core concepts, and how the pieces fit together. This is an early draft and will grow over time.

Introduction

Small OS (sm-os) is an AI-native operating system for small and medium-sized businesses. It starts with property operations and grows from a small set of stable primitives rather than a sprawl of disconnected tools.

The goal is calm, dependable software: clear operational surfaces, durable automation, and integrations that degrade gracefully instead of failing loudly.

Core concepts

Organizations

Every record is scoped to an organization, with role-based access control enforced on the server.

Work orders

The core unit of operational work — created, assigned, scheduled, and tracked through to completion.

Field work

Technicians update status, capture evidence, and complete checklists from a focused mobile workflow.

Automations

AI-drafted, human-approved workflows that run on durable execution rather than fragile scripts.

Edge Nodes

Customer-local runners that execute functions close to local systems and data.

How it fits together

The web app renders operational screens and API handlers. Authenticated actions run through shared command handlers that persist state, record domain events, and enforce access control in one place.

Background workers, integrations, automations, and Edge Nodes consume those same shared contracts — so business rules live in one place rather than being re-implemented per surface.

Getting started

  1. Sign in to reach the authenticated operations surfaces.
  2. Open an organization to see its work orders and audit trail.
  3. Create a work order, assign it, and follow it through to a field update.