Skip to content

Lazurio documentation

Explore Lazurio. From your first steps and company modules to security and operations.

Last updated:

In Lazurio, people work with AI agents using shared materials. Procedures, plans and applications stay where the team can find them and review changes.

It builds on GitHub, which can hold tasks, documentation and decisions as well as code. History shows who changed what; permissions control who can read, edit and approve the work. You do not need to move accounting, email or every other existing service into GitHub.

Company work is translated by Lazurio into private GitHub processes.
The business remains more than GitHub. Lazurio brings into it the work that benefits from versioning, access control and review.

The agent works with the materials and tools available for the task. It prepares a draft, checks it and presents it for review. You define the goal; an authorized person decides whether to publish or deploy the result.

People direct the work, Task Agents prepare Drafts, people review them, and authorized publication creates shared Organization truth.
GitHub is the context for the whole loop, not a step in it. People direct and authorize; Task Agents prepare the editable work between those decisions.

What Lazurio is today

Lazurio Platform v0.1.14 is an installable release, published on 27 October 2026. It includes the command-line tool, Apps and diagnostics. It also prepares the instructions agents read in your Lazurio Folder. You do not need a checkout of the Platform source code for everyday work. See deployment and updates.

You choose the AI client and model provider separately. A self-hosted installation does not require Lazurio’s optional account and managed-hosting services. Lazurio does not add a universal security sandbox around AI tools; check the providers and access used by your deployment. The security and control evidence explains these boundaries.

Browse the documentation

If you are new to Lazurio, open the Guide. The other sections cover technical requirements, access and operations.

The current Platform uses Elastic License 2.0. Legacy code, third-party components and optional services have separate license boundaries; see the license explanation.