Labs64.IO Documentation
Build a secure commerce platform one focused capability at a time. Labs64.IO combines independently deployable services with shared identity, policy, routing, observability, and operational conventions.
Whether you are evaluating one service, integrating a product team, or operating the ecosystem on Kubernetes, this guide is the shortest path from first request to a production-ready foundation.
In a hurry? The Quickstart installs the platform on any Kubernetes cluster with one script and has you calling an API in about five minutes.
| I want to… | Start here |
|---|---|
| Understand the platform and its vocabulary | What is Labs64.IO? · Core concepts |
| Run it: on a laptop, on my cluster, or from source | Get started |
| Explore a product capability | Services & Modules |
| Run the platform reliably | Operate & Manage |
| Find a contract or setting | Reference |
The ecosystem at a glance
Every request enters through the Auth Gateway. Modules communicate with each other exclusively through REST calls across the gateway; audit events are delivered to AuditFlow over its HTTP API. No module connects directly to another module’s database.
flowchart TB
Client(["Client / Browser"]) --> AG["Auth Gateway<br/>edge: authn + authz"]
AG --> CP[Customer Portal]
AG --> CO[Checkout]
AG --> PG[Payment Gateway]
AG --> AF[AuditFlow]
CO -->|"REST: initiate payment"| PG
PG -->|"Audit events (HTTP)"| AF
AF -->|"Route per tenant"| SINKS[("Your sinks:<br/>OpenSearch, S3, Splunk")]
A practical path to value
- Choose a path. Install the platform in minutes with the Quickstart, run one service locally, prepare a Kubernetes environment for your team, or build everything from source.
- Use a capability. Each service page explains its role, integration boundary, configuration, operations, and next step.
- Operate with confidence. Apply the shared deployment, security, observability, and tenancy patterns before production.
How to read availability
Service pages marked Planned describe the intended integration and operating model. They help you design ahead, but are not a callable product contract yet. Pages without that badge document the services you can evaluate today.
Documentation map
| Section | For | What you will find |
|---|---|---|
| Overview | Everyone | Platform purpose, concepts, and architecture |
| Get Started | First adopters and contributors | A five-minute quickstart, then local, cluster and from-source paths |
| Services & Modules | Builders | Product areas, service roles, and integration paths |
| Operate & Manage | Platform teams | Helm, routing, persistence, scaling, security, and runbooks |
| Reference | Integrators | APIs, events, configuration, images, charts, and glossary |