Nano vs Open Envelope

An AI-native security and observability platform for cloud, local, hybrid, and air-gapped teams. Sub-second search, detection engineering, OpenTelemetry, pivt AI, and...

The full technical specification for the Envelope team definition format, agent structure, workspace documents, adapters, variables, secrets, and access policies.

About Nano

An AI-native security and observability platform for cloud, local, hybrid, and air-gapped teams. Sub-second search, detection engineering, OpenTelemetry, pivt AI, and deployment control in one place. Run nano in the cloud, locally, hybrid, or air-gapped. nano was built from scratch, not refactored: a dedicated cluster, one query language over your security and OpenTelemetry data, agentic investigation, and deployment options from cloud to air-gapped. So when a service slows down, "is this an outage or a breach?" is one query, not two tools and a guess.

About Open Envelope

The full technical specification for the Envelope team definition format, agent structure, workspace documents, adapters, variables, secrets, and access policies., VS Code, JetBrains, and any SchemaStore-aware editor will validate *.envelope.json files automatically, no configuration needed. The Envelope team definition, the structure that describes agents, roles, hierarchy, escalation paths, required secrets, and adapters, is published as a formal, versioned open source specification. Anyone can read it, validate against it, and build tooling around it.