01 · Create an account
Future LAOS Account registration for the relevant product audience.
LAOS Developer Network
Build, connect and operate on the LAOS platform.
A public technical entry point for the modular LAOS platform. Documentation, APIs and access are introduced in stages, with platform boundaries and readiness stated directly.
Developer systemLAOS / 01
LAOS
Developer Network
01Interface
02Reliability
03Integration
No matching public content yet.
Developer journey
A path that starts with clear boundaries.
Public account creation and production access are not available yet. The intended journey is documented so that future access does not arrive as an opaque invitation.
02 · Register a project
Declare ownership, environment and approved modules.
03 · Choose modules
Select capabilities with their limits and data boundaries visible.
04 · Test in a sandbox
Validate an integration before an approved production deployment.
SDKs & APIs
Interfaces should be legible before they are convenient.
The public SDK catalogue will cover Python, TypeScript and Dart/Flutter alongside REST and event contracts. The fragment below is illustrative only; it is not an available package or endpoint.
Python
Data, engineering and orchestration workflows.
TypeScript
Web, edge and service integrations.
Dart / Flutter
Mobile and cross-platform product integrations.
REST & events
Explicit contracts for interoperable system boundaries.
System architecture
Architecture with a visible boundary.
Shared capabilities can support many systems while user projects retain their own data, context and control.
- 01Core
- 02Event bus
- 03Identity & registry
- 04Compute & agents
- 05Storage & observability
API pattern
Illustrative integration shape
No endpoint, package name, token or credential is implied by this example.
TypeScript
// Conceptual request shape — public endpoints are not announced yet
const client = createLaosClient({ project: 'your-project' });
await client.agents.review({ mode: 'supervised' });Resources
Technical material with an honest scope.
Quickstarts, tutorials, integration patterns, examples and component reference will appear here only as they become usable and maintained.
Documentation
Concepts, guides and contracts for public capabilities.
API reference
Versioned endpoints and schemas when a public API exists.
Downloads
Verified artefacts and checksums when releases are available.
Changelog
A factual record of availability, fixes and compatibility.
Ecosystem status
Public status must never expose private infrastructure.
A public status service will report the availability of explicitly public services only. It will not expose internal addresses, topology, ports, credentials or home-lab details.
Public service status
No public production services are announced at this time.
Security reporting
A responsible disclosure path will be published before public access opens.
Technical access
Request access when an appropriate reviewed programme is available.
Public record
Progress has a record.
Security
Public security guidance will state a reporting route and expected response policy.
Versions
Public compatibility, roadmap and support policy will be versioned here.
Access
Sign in and Control Center remain marked as coming later until public authentication exists.
LAOS Developer Network
Work with the system, not around it.
Explore the other LAOS portals for corporate context, research and technical direction.