The sovereign data and AI platform. On your ground. Under your rules.
AKKO
Seven layers, each one replaceable. One identity crosses them all.
- UsesCockpit, SupersetExplore, govern, publish dashboards.
- AIADENA question in plain language becomes SQL, under the rights of the person.
- AINORA, vector indexA data steward reviews what NORA proposes; the index finds the tables.
- Governance
OPA or Ranger, KeycloakRow and column rights, a single identity; every access is logged.
- Catalogue
OpenMetadataGlossary, lineage, a description for every table.
- Semantic layerApache Ossie modelsMeasures and dimensions written once, in the open Apache Ossie format; ADEN uses them to answer right.
- Federation
TrinoOne SQL query across every source.
- Storage
Iceberg on S3, Polaris catalogueOpen tables on SeaweedFS by default or your own S3, with the Apache Polaris REST catalogue.
- FoundationKubernetes or OpenShiftThe control plane keeps the desired state; Prometheus and Grafana watch it.
Deploy wherever you want, on premises or in the cloud
Your Hadoop
Federate your Hadoop without moving your data. AKKO plugs into the cluster in place; its rights and its catalogue stay the reference.
- ClouderaThe distribution in place, kept as it is.
Hive and IcebergThe Hive and Iceberg tables of the cluster, federated by Trino through its metastore.
- HDFSThe storage of the cluster, never copied.
RangerThe access policies, applied to every query.AtlasThe technical catalogue and lineage of the cluster.
- KerberosThe authentication of the cluster, respected end to end.
- ARCHEThe edition of AKKO for a Hadoop in place: federation and AI under the Ranger rights and the Atlas catalogue already defined, agents through the AKKO MCP connector. Reasoned, Controlled, Inherited, Explainable access.
Objects and databases
This island holds object storage and databases. The data stays where it is; only answers travel.
- S3Any S3-compatible object storage (Ceph, MinIO, a host’s service), on premises or hosted.
SeaweedFSThe S3-compatible object storage AKKO installs by default; any other S3 storage can replace it.
IcebergThe open table format, with history and schema evolution.
Trino and its connectorsAt the heart of AKKO, Trino reads more than thirty sources in place: relational databases, warehouses, documents, search, streams, open tables. Pinot, Hudi, Delta Lake, Loki, Vertica and Exasol too.
PostgreSQL, MySQL, MariaDB, Oracle, SQL Server, Snowflake, BigQuery, Redshift, ClickHouse, Druid, MongoDB, Cassandra, Elasticsearch, OpenSearch, Redis, Kafka, Iceberg, Hive, Google Sheets, Prometheus, SingleStore, DuckDB
AI and agents
Models run on your ground or with a host you choose; agents go through AKKO and its rights.
- MistralModels served by API or installed on site.
- OllamaOpen models on a single machine.
vLLMHigh-throughput model serving on GPUs.
- MCPThe gate every agent goes through; each call carries the identity of the person it works for, and each tool is authorised.
- LiteLLMOne gateway to every model, with quotas and traces.
- Other providers, through LiteLLMOpenAI, Anthropic, Google Gemini, Llama, Qwen, DeepSeek, Hugging Face: by explicit choice; by default, models run on your side.
- Claude, GitHub Copilot, CursorAgents that query the data through MCP, within the rights of that person.
- In-house agentYour own agents, on the same protocol.
The Lab
The workspace of data teams: notebooks, code, compute, models and orchestration, on the same rights.
- JupyterLab, Jupyter AIA notebook for each person, signed in with their identity; Jupyternaut answers in the page.
- code-serverVS Code in the browser, with dbt Power User, SQLTools and its Trino driver, and GitLens.
- Coding with an AI assistantJupyternaut and Continue write the code on request, on models that run on your side through LiteLLM, never a cloud by default.
akko-labThe ready environment: libraries, connections and access to Trino, under the rights of the person.
- SparkDistributed compute for heavy processing.
- MLflowExperiment tracking and the model registry.
- AirflowOrchestration of the processing chains.
AKKO
Seven layers, each one replaceable. One identity crosses them all.
- UsesCockpit, SupersetExplore, govern, publish dashboards.
- AIADENA question in plain language becomes SQL, under the rights of the person.
- AINORA, vector indexA data steward reviews what NORA proposes; the index finds the tables.
- Governance
OPA or Ranger, KeycloakRow and column rights, a single identity; every access is logged.
- Catalogue
OpenMetadataGlossary, lineage, a description for every table.
- Semantic layerApache Ossie modelsMeasures and dimensions written once, in the open Apache Ossie format; ADEN uses them to answer right.
- Federation
TrinoOne SQL query across every source.
- Storage
Iceberg on S3, Polaris catalogueOpen tables on SeaweedFS by default or your own S3, with the Apache Polaris REST catalogue.
- FoundationKubernetes or OpenShiftThe control plane keeps the desired state; Prometheus and Grafana watch it.
Deploy wherever you want, on premises or in the cloud
Your Hadoop
Federate your Hadoop without moving your data. AKKO plugs into the cluster in place; its rights and its catalogue stay the reference.
- ClouderaThe distribution in place, kept as it is.
Hive and IcebergThe Hive and Iceberg tables of the cluster, federated by Trino through its metastore.
- HDFSThe storage of the cluster, never copied.
RangerThe access policies, applied to every query.AtlasThe technical catalogue and lineage of the cluster.
- KerberosThe authentication of the cluster, respected end to end.
- ARCHEThe edition of AKKO for a Hadoop in place: federation and AI under the Ranger rights and the Atlas catalogue already defined, agents through the AKKO MCP connector. Reasoned, Controlled, Inherited, Explainable access.
Objects and databases
This island holds object storage and databases. The data stays where it is; only answers travel.
- S3Any S3-compatible object storage (Ceph, MinIO, a host’s service), on premises or hosted.
SeaweedFSThe S3-compatible object storage AKKO installs by default; any other S3 storage can replace it.
IcebergThe open table format, with history and schema evolution.
Trino and its connectorsAt the heart of AKKO, Trino reads more than thirty sources in place: relational databases, warehouses, documents, search, streams, open tables. Pinot, Hudi, Delta Lake, Loki, Vertica and Exasol too.
PostgreSQL, MySQL, MariaDB, Oracle, SQL Server, Snowflake, BigQuery, Redshift, ClickHouse, Druid, MongoDB, Cassandra, Elasticsearch, OpenSearch, Redis, Kafka, Iceberg, Hive, Google Sheets, Prometheus, SingleStore, DuckDB
AI and agents
Models run on your ground or with a host you choose; agents go through AKKO and its rights.
- MistralModels served by API or installed on site.
- OllamaOpen models on a single machine.
vLLMHigh-throughput model serving on GPUs.
- MCPThe gate every agent goes through; each call carries the identity of the person it works for, and each tool is authorised.
- LiteLLMOne gateway to every model, with quotas and traces.
- Other providers, through LiteLLMOpenAI, Anthropic, Google Gemini, Llama, Qwen, DeepSeek, Hugging Face: by explicit choice; by default, models run on your side.
- Claude, GitHub Copilot, CursorAgents that query the data through MCP, within the rights of that person.
- In-house agentYour own agents, on the same protocol.
The Lab
The workspace of data teams: notebooks, code, compute, models and orchestration, on the same rights.
- JupyterLab, Jupyter AIA notebook for each person, signed in with their identity; Jupyternaut answers in the page.
- code-serverVS Code in the browser, with dbt Power User, SQLTools and its Trino driver, and GitLens.
- Coding with an AI assistantJupyternaut and Continue write the code on request, on models that run on your side through LiteLLM, never a cloud by default.
akko-labThe ready environment: libraries, connections and access to Trino, under the rights of the person.
- SparkDistributed compute for heavy processing.
- MLflowExperiment tracking and the model registry.
- AirflowOrchestration of the processing chains.
Paused. Touch to resume.