ObjectStack ProtocolWelcome to ObjectStack
The Metadata-Driven Protocol for the Post-SaaS Era.
ObjectStack is not just a framework; it is a Protocol for building enterprise software. It decouples the Business Intent (defined in JSON/YAML) from the Technical Execution (handled by the Kernel).
This documentation is the authoritative reference for the ObjectStack Protocol.
How to navigate
Getting Started
Build your first Object in 5 minutes. Learn the basics of the SDK.
Concepts
Understand the philosophy of 'Intent over Implementation' and the 'Local-First' architecture.
Specifications
The Architecture Blueprints. Deep dive into ObjectQL (Data), ObjectUI (View), and ObjectOS (Control).
Protocol Reference
The Dictionary. Comprehensive reference for every Schema, Field Type, and Configuration option.
The "Trinity" Architecture
ObjectStack is built on three pillars that work in unison:
| Pillar | Protocol | Responsibility |
|---|---|---|
| Data Layer | ObjectQL | Defines the shape of data (Object) and how to access it (AST). Agnostic to SQL/NoSQL. |
| Control Layer | ObjectOS | The Kernel. Handles Identity, Security, Sync, and Automation. |
| View Layer | ObjectUI | The Projection. Defines the User Interface as abstract JSON layouts, enabling Server-Driven UI. |
For whom is this?
- Platform Architects: Who want to build internal developer platforms (IDP) that scale.
- Protocol Implementers: Who want to write a new Driver for ObjectQL (e.g., for FoundationDB) or a new Renderer for ObjectUI (e.g., for Flutter).
- AI Agent Developers: Who need a deterministic, structured generic language for AI to generate software.