BasilAOS 1.0: one platform, four connected product planes

From a toolchain to an operating model

BasilAOS 1.0 brings Workbench, Library, Studio, and Admin onto one shared foundation. The release is less about placing four products beside one another and more about removing the seams that prevent enterprise agents from operating as a system.

Before this foundation, an employee workspace, a knowledge repository, a workflow builder, and an administrative console could each work independently while still creating duplicate accounts, conflicting permissions, repeated configuration, and disconnected artifacts.

BasilAOS 1.0 establishes one account system, file and folder ACE permissions, model groups, role-gated functions, and formal super-administrator transfer across the platform.

Four product planes

Workbench: where people work with agents

Workbench is the employee-facing workspace. Teams launch approved agents, upload or retrieve context, review generated artifacts, handle exceptions, and complete multi-step work without moving between separate AI tools.

Library: where company context becomes usable

Library brings files, digital assets, product objects, published table views, knowledge bases, and generated artifacts into one governed environment. What a user cannot access in Library remains unavailable to their agent.

Studio: where execution becomes dependable

Studio provides visual workflows, typed variables, condition routing, function calling, output parsing, code, HTTP requests, connectors, Library operations, Smart Tables, and triggers. Creative steps can remain flexible while approvals, compliance checks, and data jobs run on deterministic rails.

Admin: where the enterprise remains in control

Admin governs users, groups, roles, models, connectors, permissions, versions, call records, logs, and system operations. Governance is not an external checklist; it is a product surface connected to the work itself.

One foundation

The value appears in the loop between the four planes. Library makes the organization legible. Workbench lets agents use that context. Studio defines how they act. Admin keeps the system governed. Approved artifacts and decisions return to Library with provenance, becoming useful context for the next run.

BasilAOS 1.0 is the foundation for an AI-readable, agent-operated company: one operating layer, four ways to work.