Skip to content

A ten-minute IT briefing

Use this briefing to prepare a Lazurio pilot and decide what the operator must demonstrate before deployment. Lazurio uses Git repositories for company materials and change history. Agents prepare drafts; publication is approved separately. GitHub, the operating system and connected services still control access.

The current baseline is installable Platform v0.1.21, released on 13 November 2026. CLI and Apps share one installed program; the product generates the Lazurio Folder’s agent instructions (README). This does not supply an AI subscription or a universal sandbox. The earlier Lazurio root repository at revision 3c5bda5, which this briefing still cites for some rules, ran from a developer-operated source checkout with Git and Bun and had an experimental CLI v0; that describes that revision, not the current release.

Before approval, identify the account, machine, Organization, tool and available data. Separately verify who may publish the result.

The user's machine is one trust domain holding the Lazurio root, Organization checkouts, the task agent client and local integrations. Data leaves it for GitHub, the selected model provider, approved application providers and optional hosted services.

The diagram is a reference model. Its boundary is the user’s machine: one shared trust domain, not a hosted Environment. Optional hosted services are separate services and belong in the inventory only when a deployment enables them.

ItemCurrent public position
Product formInstallable CLI and Apps, with generated instructions; source checkout is not required for daily use. Releases are versioned; the latest final release is v0.1.21 of 13 November 2026.
Runtime maturityThe Platform README still describes the status as release candidates, and hosted Environments still run the earlier Resident beside it until hosted entry and content synchronization land. Verify the installed release and enabled services; a release is not a promise that every optional service is deployed.
LicenseLazurio Platform is source-available under Elastic License 2.0, with no automatic transition to Apache. A hosted or managed service offered to third parties that exposes a substantial set of the software’s features or functionality needs a separate agreement, even when it is free. This is not a prohibition on every kind of hosting: internal company use, including a rented server or an internal cloud deployment, is allowed subject to the license (scope). The earlier Lazurio root repository is under FSL-1.1-Apache-2.0, with Apache 2.0 applying to each of its published versions after two years.
AssuranceNo certification, universal service level, retention period or deployment topology is claimed. Support and hosting terms belong to the concrete deployment.

See security and control evidence for the license, source links and limits of these claims.

AreaLazurio’s operating modelWhat IT should verify
IdentityThe signed-in user supplies authority; a task agent has no independent rights.The account, repository membership and machine owner are correct.
Company boundaryOne company maps to one Organization and GitHub access boundary. One machine remains one trust domain.Only intended repositories are mounted; use separate machines or equivalent isolation when companies must not share an OS boundary.
Working contextWork begins in checked-out source and explicitly enabled tools.Endpoint protection, local data scope and provider terms meet policy.
PublicationAgent output stays editable until an authorized merge, deployment, send or provider action.Branch rules, reviews and provider permissions enforce the intended gate.
IntegrationsEach connected app has one route: a tool, Executor or, where the Organization allows it, Composio. Official MCP servers and CLIs come first. Tool and Executor sign-ins stay in the Environment and can be revoked separately; Composio connections belong to the Composio account, and Composio holds their tokens and call content.Every provider, OAuth scope, owner, data path and revocation procedure is accepted.
EvidenceGit and provider records can show who changed what, but coverage depends on the tools actually used.Required endpoint, model, app and deployment logs exist and have named retention.

Access depends on the account, machine, repository permissions, AI client and enabled tools. Check these five areas for your deployment:

  1. Git repositories and teams visible to the operating identity.
  2. Local files placed inside the active workspace or readable by the client.
  3. External applications connected through a tool, Executor (MCP servers) or, where the Organization allows it, Composio, and work in a browser under the user’s supervision.
  4. The agent client, model provider and any hosting provider used by modules.
  5. Optional hosted Lazurio services such as Dashboard, a hosted team workspace or a per-owner Resident/Buddy service.

An integration existing in the ecosystem is not evidence that it is enabled. Ask for a live list with provider, scopes, owner and revocation instructions.

Lazurio does not turn policy prose into a universal technical restriction. Controls remain with the system that owns the capability:

ActionEffective control
Read a local fileOS permissions, workspace selection and any client sandbox. A readable file may be sent to the model provider as task context.
Push a branch or open a pull requestGitHub write permission. This is reviewable Draft work, but the source has already reached GitHub.
Merge or deploy an exact revisionBranch rules, required checks, reviews, merge rights and the module’s deployment gate.
Create or send something in an external providerThat provider’s credential, scopes and confirmations. A provider draft may already transmit data; where no provider-enforced restriction exists, explicit authorization remains a process control.

An agent prepares the change. Publication requires both the account’s permission and approval from the person responsible for that decision.

A person defines the outcome, an Agent prepares a proposed change and proof, and the change takes effect only when the account is allowed to perform it and the responsible person approves it.
The agent prepares the result. The authorized user decides whether to publish it.

Before production use, ask for:

  • the Organization, repository and enabled-service inventory;
  • named identities, GitHub team grants and offboarding owners;
  • the endpoint protection and local-data baseline;
  • the selected agent client, model provider and data-processing terms;
  • integration scopes, credential custody and revocation procedures;
  • branch protection and provider-specific publication authority;
  • logs, retention, backup, deletion, incident response and rollback; and
  • a bounded pilot that proves both the normal path and meaningful denials.

Unknowns should become implementation issues, not security claims.

Approve a scoped pilot when the identities, repositories, endpoint boundary, providers, integrations and action-by-action gates are concrete and testable. A source-checkout pilot carries different support and change-control risk from a managed product. Continue with data access and security and deployment and operations before approving production use.