Home

AKKO

Own Every Layer

The sovereign data and AI platform you deploy in minutes and control forever. Every layer on your infrastructure. Kubernetes-first. Zero cloud lock-in.


What is AKKO?

AKKO (Analytics Kernel, Keep Ownership) is a self-hosted analytics stack that gives you the full power of a modern lakehouse -- from raw storage to polished dashboards -- without surrendering a single byte to a cloud vendor.

Deploy with Helm on Kubernetes: locally via k3d for development, or on any CNCF-conformant cluster for production. Every component is open-source and Apache-licensed whenever possible -- no BSL surprises, no usage-based billing, no vendor-controlled kill switch.


Everything You Need, Integrated

Six pillars, one platform. Every service is wired with SSO, monitoring, and data governance out of the box.


Up and Running in 3 Steps

1

Clone and create your cluster

git clone https://github.com/AKKO-p/AKKO.git
cd akko/helm/scripts && ./k3d-create.sh
2

Deploy with Helm

./deploy.sh
3

Open the Cockpit

open https://akko.local

Sprint 36 & 37 — delivered

36 commits, zero breaking changes. AKKO is now repositioned as an AI-native sovereign data & AI platform.

  • RBAC hardened — OPA plural-group handling, preferred_username in Trino, destructive DDL admin-only, first live 4-dimension matrix (5 roles x 4 services x 3 dims).
  • AI stack matured — OpenMetadata JWT bot for ADEN, Trino error translator, catalog suggest, session history, 10 BLOCKERS of hardcoding externalized.
  • Cockpit UX — stable service counter, ARIA palette/drawer fixed, architecture page refreshed, 6 health-proxy 502s closed.
  • Docs & demos — MkDocs nav refresh, bilingual DEPLOYMENT, enterprise-federation page (EN+FR), banking-fraud demo end-to-end.
  • Tests — Playwright cockpit-render-validate, pytest integration with env-var passwords, notebook execution harness, post-deploy Woodpecker pipeline.

See the consolidated changelog for the full history, and the Kubernetes Deployment guide for setup details.

Default demo credentials (demo/dev mode only)

AKKO ships five seed users: alice / alice123 (admin), bob / bob123 (engineer), carol / carol123 (analyst), eve / eve123 (user), dave / dave123 (viewer). These memorable six-character passwords are for demos and CI only — override the akko-test-users-passwords Secret before install for any shared environment. Enterprise mode (global.auth.mode=enterprise) disables them entirely. Full reference: DEPLOYMENT.md § Default demo credentials.


Service URLs

All services are accessible via *.akko.local domains through the Traefik ingress controller (configurable via global.domain in Helm values).

Service URL
Cockpit https://akko.local
JupyterHub https://lab.akko.local
Superset https://bi.akko.local
Airflow https://orchestrator.akko.local
Keycloak https://identity.akko.local
Dashboards https://metrics.akko.local
Object storage console https://storage.akko.local
Trino UI https://federation.akko.local
MLflow https://experiments.akko.local
Polaris https://polaris.akko.local

macOS / Safari

Self-signed certificates require manual trust in Keychain Access on first use. See the Installation guide for details.


Why AKKO?

No compute-based billing

Traditional analytics stacks charge per compute unit, per user, or per TB. AKKO is built on open-source components (Apache-2.0 / MIT / BSD); deploy on your own hardware and pay only for the infrastructure. Support, SLA, hardened images and managed SaaS are commercial offerings — see Offers.

Data Sovereignty

Every byte stays under your control. AKKO runs entirely on-premises or in your private cloud with full audit trails for GDPR, HIPAA, and NIS2 compliance.

No Vendor Lock-in

Open standards everywhere: Apache Iceberg, S3, SQL, OAuth2. Migrate any component independently without rewriting your pipelines.

Production-Ready

Every layer integrated — SSO, RBAC, monitoring, alerting, data governance and lineage. From ETL pipelines to executive dashboards, AKKO covers the full data lifecycle.