Get Started
You can have Labs64.IO answering real API requests in about five minutes. No account, license key or sign-up is involved: everything on this page is open source and runs on your own machine or cluster.
Not sure where to begin? Take the Quickstart.
Pick your path
| You want to… | Take this path | You need | Time to first result |
|---|---|---|---|
| See it running and call an API | Quickstart: one script installs the platform on any Kubernetes cluster | kubectl, Helm 4, a cluster (a local one is fine) | About 5 minutes |
| Try one service without Kubernetes | Run one module locally: AuditFlow on Docker Compose | Docker, just, JDK 25, Maven | A few minutes |
| Run it for your team | Deploy to your Kubernetes cluster: AWS, Azure, GCP or on-premises, with your own identity provider and data stores | A cluster and the infrastructure you intend to keep | An afternoon for a first environment |
| Change the code | Run the full ecosystem locally: every repository, built from source | Docker, and VS Code or a handful of CLI tools | One long first build, then minutes |
flowchart TD
Q{"What do you want to do?"}
Q -->|"See it work"| A["Quickstart<br/>about 5 minutes"]
Q -->|"Try one service, no Kubernetes"| B["Run one module locally"]
Q -->|"Run it for a team"| C["Deploy to your Kubernetes cluster"]
Q -->|"Change the code"| D["Run the full ecosystem locally"]
A -.->|"ready for more"| C
B -.->|"ready for more"| A
The paths build on each other. The Quickstart and a team deployment install the same Helm chart; what changes is who provides the identity provider, the data stores and the secrets. Nothing you learn on the first path is thrown away on the next.
What you are installing
Labs64.IO is a set of independently deployable services behind one authenticated gateway. You do not have to adopt all of it.
| Piece | What it does for you |
|---|---|
| Auth Gateway | Checks every request’s token and policy at the edge, so services do not each reimplement it |
| AuditFlow | Takes audit events over one REST call and routes them to the stores you choose |
| Payment Gateway | One payment API in front of several payment providers |
| Checkout and Customer Portal | The purchase flow and the customer-facing frontend |
For the vocabulary and the reasoning behind this shape, read What is Labs64.IO? and Core concepts. Neither is required before the Quickstart.
When you get stuck
- Troubleshooting your first run covers the problems people actually hit on day one.
- Compare the paths shows side by side what each path installs and what it is not meant for.
- Found a bug or a gap in these pages? Open an issue in the repository it belongs to, or use the “Edit this page on GitHub” link at the bottom of any page.