ObjectOS
A self-hosted business platform your team can operate
ObjectOS is for business users, operators, and IT teams who need internal tools, approval workflows, governed AI actions, audit logs, and data ownership without sending the business system to a third-party cloud. AI assistants act through the same controlled business actions as people.
The Business Platform AI Can Actually Use
ObjectOS turns metadata-defined apps into tools business teams can run, govern, and audit.
Put CRM records, contracts, tickets, approvals, and internal tools on ObjectOS. Your people and AI assistants act through the same identity, permission, and audit model, so business operations stay governed even when agents help execute the work.
What Business Teams Get from ObjectOS
Self-hosted apps, generated admin surfaces, Account, permissions, audit, approvals, and AI assistance without losing data control.
Business Access Control
Users sign in through the identity system you already trust. Roles, row rules, and field redaction protect records whether work happens in the Console, an API, or an AI-assisted action.
Approvals and Internal Tools
Tickets, contracts, expenses, onboarding, inventory, and custom workflows become governed business apps with generated APIs and Console surfaces.
Data Stays in Your Environment
Business records, identities, sessions, audit logs, files, and prompts stay in your database and storage. Offline and air-gapped deployments remain first-class options.
Extend Without Replatforming
Add drivers, identity providers, audit exporters, webhooks, storage, jobs, and AI capabilities as plugins while keeping the same business runtime.
Architecture as Metadata
Flows and plugins are declarative artifacts loaded by the kernel — analyzable by humans and AI agents alike.
# expense-approval.flow.yml
name: ExpenseApproval
initialState: submitted
states:
submitted:
on:
approve:
target: approved
conditions:
- role: manager
- amount: < 5000
escalate:
target: pending_director
conditions:
- amount: >= 5000
pending_director:
on:
approve:
target: approved
conditions:
- role: director
reject:
target: rejected
approved:
actions:
- notify: submitter
- update_ledger
- archive
rejected:
actions:
- notify: submitter
- log_audit
# Same flow becomes:
# • a REST endpoint
# • a typed SDK call
# • an MCP tool 'expense.approve' for AI agents// crm-plugin.manifest.ts
export const CRMPlugin = {
name: 'enterprise-crm',
version: '2.1.0',
objects: [
{ import: '@objectql/schemas/customer' },
{ import: '@objectql/schemas/opportunity' },
{ import: '@objectql/schemas/contract' },
],
flows: [
{ import: './flows/lead-qualification.yml' },
{ import: './flows/contract-approval.yml' },
],
permissions: {
'sales-rep': ['read:customers', 'create:opportunities'],
'sales-manager': ['*:customers', '*:opportunities'],
'finance': ['read:contracts', 'approve:contracts'],
},
// Surfaces exposed to AI agents (MCP tools)
agentTools: [
'customer.list', 'customer.get',
'opportunity.create', 'opportunity.advanceStage',
'contract.approve',
],
};Local-First Sync, Built In
Offline-capable business apps are a kernel property, not a third-party library.
The Challenge of Distributed State
Field technicians, sales reps, and operators in disconnected environments work against local data that diverges from the server. Merging by hand is error-prone — who wins, what gets lost, how do you audit it?
ObjectOS as Replication Authority
The kernel acts as the authoritative replication controller between the server and local stores (SQLite/RxDB). CRDT and last-write-wins strategies are declared as policy metadata; the kernel handles execution and conflict resolution. Every merge is attributable and auditable.
Three Layers, One Metadata Spine
Most customers deploy ObjectOS first; Framework and ObjectUI explain where the artifact and UI surfaces come from.
Framework / ObjectQL
Defines objects, fields, queries, drivers, flows, views, actions, and agents as structured metadata artifacts.
ObjectUI
Renders the Console, app shell, object views, forms, dashboards, and plugin views from metadata.
ObjectOS
Runs the artifact in your environment, enforces identity and permissions, and exposes APIs plus MCP tools.
ObjectOS is the runtime you operate; Framework metadata and ObjectUI renderers plug into it.
From Local-First Tools to Mission-Critical Platforms
One microkernel that scales from a single-user workstation to multi-tenant agent-operated platforms.
Field & Offline Operations
Local-first apps for technicians, inspectors, and sales teams. The kernel handles offline writes, sync, and conflict resolution. Audit and attribution are preserved end to end, even when an AI assistant performs the action.
Enterprise Application Suite
Run ERP / CRM / HRM modules as plugins on a single kernel. Unified identity, unified audit, unified MCP surface so internal copilots can safely act across modules with role-bound permissions.
Agent-Operated Multi-Tenant SaaS
Ship SaaS where every tenant gets the same auditable surface — REST, SDK, and MCP — backed by per-tenant policies in metadata. Scale from 10 to 10,000 tenants without parallel security or AI-tool implementations.
Define Your Business Once.
Let Humans And Agents Operate It Safely.
Stop scattering business logic across SQL, JavaScript, and UI state. Make objects, permissions, workflows, APIs, UI metadata, and agent tools one structured Zod source of truth — analyzable, versioned, and auditable end to end. Launch July 2026.