Layr8 Documentation
Most coordination patterns assume stability: fixed schemas, synchronized releases, shared control. In real systems — especially across teams or organizations — those assumptions rarely hold. Schemas evolve, teams change priorities, new participants join. The integrations break.
Layr8 is a coordination layer that separates coordination from implementation. Instead of tightly coupling systems together, Layr8 lets participants evolve independently while preserving shared guarantees. Identity-based, not URL-based. Encrypted end-to-end. No shared api keys.
Why Layr8
Designed for change. Participants change APIs, schemas, and implementations without breaking each other. Coordination survives change because it relies on identity and protocols, not siloed-identity and shared api keys.
Coordination without coupling. Integrate across organizational boundaries without shared infrastructure, synchronized releases, or centralized control. Each side owns their implementation.
Built for trust. Every interaction is authenticated, encrypted, and auditable. Clear failure modes. No hidden assumptions. Both parties can verify what happened without trusting each other’s logs.
Practical to adopt. Start with a free node and a single integration. Prove value. Expand where it earns its place. Layr8 coexists with your existing systems — it’s additive, not invasive.
Get Started
Ready to build? Go from zero to your first cross-organization message:
- Getting Started — Provision a free node, write an agent, and send your first message
Want to understand first?
- What Is Layer 8? — The conceptual foundation: identity as a network layer
- How Layr8 Works — Agents, grants, policies, and audit chains
- Architecture — How a Layr8 Node fits into your infrastructure
See It In Action
- Database Proxy Demo — Query a partner’s database using your identity. No VPN. No shared credentials.
- CRM Integration Demo — Connect systems across organizations without custom API integrations.
- Example Agents — Echo, Postgres, REST proxy, IoT — working code you can run.
Evaluate
- Boundaries and Assumptions — What Layr8 guarantees, what it doesn’t, and where it fits
- FAQ — How Layr8 compares to API keys, OAuth, and existing tools
- For Partners — What integration looks like from the other side
Go Deeper
- SDK Reference — Go · Node.js · Python — API details for each language
- Reference — DIDs · DIDComm · Verifiable Credentials · Problem Reports