Demo videos

Each video is one real recorded run, nothing staged · EKOS v1.5.5 (13 November 2026)

EKOS compiles code, SQL schemas, ETL jobs, documents and live database catalogs into an append-only, evidence-backed knowledge ledger that people and AI agents can query. The videos below show it working on real open-source systems, including the iDempiere ERP, Pagila and Plausible Analytics. After them comes a guide to what is new in EKOS 1.4–1.5.5: what each feature is for, when to use it, and the commands to run.

Videos

A video loads from YouTube (youtube-nocookie.com) only when you press play. Until then this page contacts nothing at YouTube.

EKOS: An Enterprise Knowledge Compiler for Evidence-Backed AI

What EKOS is and why it exists. The CLI pipeline (doctor → init → build → recover → resolve → compile → commit), the web console and its knowledge graph, then VS Code with GitHub Copilot grounded through EKOS over MCP, on a live ClickHouse schema, with and without EKOS context. The project is Plausible Analytics.

11 Sep 2026 · Watch on YouTube

Ask your data: SQL and dashboards written and checked by EKOS

A business question in Apache Superset returns one checked, read-only SQL query, its rows, or a whole dashboard. The knowledge comes from EKOS's compiled iDempiere ledger: 156,487 objects and 281,840 relationships. This cut adds animations for each step, so you can follow without reading SQL. “Delete all invoices of Joe Block” is refused by EKOS.

9 Nov 2026 · animated version · Watch on YouTube

Ask your data: SQL and dashboards written and checked by EKOS

The same questions with the step log in full: each EKOS call as it happens, each of the 7 joins traced to its ledger id and evidence. Then the Azure architecture, how a question flows inside, and the BIRD results: 76.2% execution accuracy on Mini-Dev against 53.3% with raw table definitions.

9 Nov 2026 · technical version · Watch on YouTube

EKOS on iDempiere: one real run, end to end

iDempiere on Oracle (903 tables, 20 years of migration scripts) taken from analysis to gold marts in the console. The run compiles with 0 model calls, generates 239 documentation pages and has a person review and sign off a 33-table slice. Marts are described in plain words, bronze and silver run through Dagster (895 checks), and gold marts are reconciled. What went wrong is recorded too.

27 Oct 2026 · Watch on YouTube

EKOS Lakehouse: the full end-to-end demo

Pagila goes to monitored Iceberg tables. The load plan gives a reason per table, every load is reconciled (counts, aggregates, bucketed checksums, and a planted difference that must be caught), and source changes arrive as a reviewed Git branch. A gold mart is built from a written description, and terms that name no column come back as questions.

21 Oct 2026 · Watch on YouTube

EKOS on Azure: install, open, remove (a real run)

The cloud console installed into an Azure subscription two ways: a one-file installer that signs in with your own account and shows a cost estimate, and Terraform directly. Both consoles are opened over HTTPS, then both deployments are removed until no resource group is left. Every timing is real, including the 27–29 minutes Azure takes to delete a Container Apps environment.

3 Nov 2026 · Watch on YouTube

Use cases: which video and feature for which job

“What does this legacy system actually do?”

Compile the code, migration scripts and live catalog, then ask. Start with the overview; then use the interaction map, transformation chain and source passport.

Self-service BI that does not guess

Business users ask in plain words and get checked, read-only SQL. Watch Ask your data; use SQL check and generate, plus annotations for your synonyms and rules.

Migrating an ERP to a lakehouse

Review and sign off the source model, then generate reconciled bronze, silver and gold. Watch the iDempiere and Iceberg videos; see what the data says.

Grounding AI coding agents

Claude Code, Copilot or any MCP client reads compiled, evidence-backed facts instead of grepping. See the overview video and Connecting Claude Code.

Capturing what people know

Answers from Slack, Teams or Telegram become testimony with an author and a date, and open questions go to the right person. See people as a source.

Running it for a team

Native installers for a laptop; Azure (installer or Terraform) for a shared console with sign-in. See installers and the Azure video.

Getting started in five minutes

  1. Install. Download the installer for your system from the latest release (.msi, .pkg, .deb or .rpm). You can also use the one-line script:
    curl -fsSL https://raw.githubusercontent.com/alexeyban/EKOS/main/install.sh | sh     # Linux, macOS
    powershell -ExecutionPolicy Bypass -c "irm https://raw.githubusercontent.com/alexeyban/EKOS/main/install.ps1 | iex"   # Windows
  2. Run EKOS Setup. The wizard opens in your browser and asks for the EKOS home, local or team console, a first project and its source directories, and which agents to register (Claude Code, Claude Desktop, VS Code). It lists every step before it does anything.
  3. Compile a project. In the console, press Init & compile on the project's top bar. From a terminal:
    cd your-repo
    ekos init --detect          # an ekos.toml that matches what is in this repository
    ekos build && ekos recover && ekos resolve && ekos compile && ekos commit
  4. Ask. Use the console's search, graph and chat, or point your agent at ekos mcp serve. More in the Quickstart.

Recent features: how to use them

Everything below shipped between v1.4.0 (8 November 2026) and v1.5.5 (13 November 2026). The full list is in the changelog.

Native installers for every system v1.5.5

A Windows .msi (per user, no administrator), a macOS .pkg (Apple silicon), and Linux .deb and .rpm (x86_64 and ARM, glibc 2.34+). Each puts the program and the web console in place and adds EKOS Setup and EKOS Console to the menu. The Release workflow installs, sets up and uninstalls each one on a fresh machine before attaching it to a release. Since v1.5.0, ekos.exe needs no Visual C++ runtime. A Microsoft Store package is also built.

How to

sudo apt install ./ekos-<version>-x86_64-unknown-linux-gnu.deb   # or: sudo dnf install ./….rpm
ekos setup                       # as yourself, never as root
ekos console open --start        # starts the console first if it is not running
ekos uninstall                   # undo what setup did; the OS uninstaller removes the program

The installers are unsigned. On Windows, SmartScreen needs More info → Run anyway. On macOS, right-click the .pkg and choose Open. Your projects in ~/.ekos survive an uninstall. More in Installation.

Writing and checking SQL against compiled knowledge v1.3–v1.4.5

ekos sql check lints a query against the ledger's real tables, columns and keys and against the dialect's rules. It catches unknown names (and suggests the nearest real ones), joins that multiply rows, integer division, a wrong row-limit form, and made-up constants under a column's name. ekos sql generate is EKOS's own text-to-SQL agent, the one measured on BIRD. Every draft is checked before it is final, and a question that would change data is refused with no SQL. This is the engine behind the Ask your data videos.

Use it when

How to

ekos sql check q.sql                         # against the ledger and dialect rules
ekos sql check q.sql --database erp          # plus read-only probes on the live database
ekos sql generate "invoiced total per business partner" --database erp --allow-metered

Over MCP, ekos_sql_check is always available. ekos_sql_generate calls a model, so you switch it on in ekos.toml. It has a daily cap and can be limited to a list of tables:

[sql-generate]
mcp = true
allow-metered = true     # needed for any provider other than a local Ollama model

The interaction map: who reads and writes each table v1.5.0 complete in v1.5.5

For every table, EKOS lists the actors that read or write it: routines, Java components, Kettle jobs and database roles. It shows what the code declares and what the database was seen doing. Observed access comes from PostgreSQL pg_stat_statements, Oracle V$SQL and ClickHouse system.query_log, aggregated per role, table and operation. No statement text is kept.

Use it when

How to

ekos interaction matrix --table c_invoice    # every reader and writer of one table
ekos interaction observe --database erp      # add what database roles were seen doing
ekos interaction findings                    # unexplained writers, writes never observed, many writers

Findings become open questions for a person. In the console, see the Interaction page and Writers and readers on every estate table page. Over MCP, use ekos_interaction.

The transformation chain v1.5.0

A view or stored routine is drawn as a chain of steps. Each step has one sentence that says what it does, plus its source text, its columns and its evidence. This is how you read a 400-line procedure without reading 400 lines.

How to

ekos transformation graph --object <id>

Console: the Transformations tab, where you can add notes on a step. MCP: ekos_transformation_graph. For Pentaho jobs, see Pentaho to dbt.

What the data says about the code v1.5.0–v1.5.5

EKOS profiles a live database to check what the code claims, and it handles only counts. The only values it ever touches are the literals the code already names. It records which coded values are used and how often (per month, with first and last seen), which are dead and which appear only in the data. It also finds implications such as status = 7 ⇒ cancelled_at IS NOT NULL, each table's grain, and references the data shows. Those references are proposed with a MinHash signature and confirmed by an exact inclusion check.

Use it when

How to

ekos profile run                                   # for [[databases]] with profile = "p1" or "p2"
ekos profile show account
ekos relationships discover --cross-database       # proposals, verified by inclusion
ekos review relationships "invoice.parts_id → partstax.parts_id" --confirm --as ana

In v1.5.5, discovery proposes no second parent. On iDempiere that cut 265 candidates to 13 and kept both true ones.

More live databases: SQL Server and Informix v1.5.0

EKOS reads the catalogs of PostgreSQL, Oracle, ClickHouse, SQL Server and Informix read-only. It reads tables, keys, checks, comments, views, procedures, functions and triggers, and compiles them to the same objects as code. Every session is read-only, and a permission check refuses a role that could write.

How to

ekos database add erp    --kind sqlserver --connect mssql.local:1433/erp --user ekos_ro --password-env ERP_PW --owner dbo
ekos database add stores --kind informix  --connect ifx.local:9088/stores@ol_ifx --user ekos_ro --password-env STORES_PW --owner informix
ekos database test erp

You can also add a database from the console's Sources form. More in Indexing a database.

The source passport: estate documentation for analysts v1.5.0

Each table page of the generated estate documentation answers an analyst's questions: what a row is, its keys and references, its codes, how it changes, what the code assumes, what people said, and its open questions. Every fact carries its status and evidence, and a section appears only when it has content.

How to

ekos docs generate --layout estate --output docs/estate

People as a source: inbox, questions and chat channels v1.5.0

Some knowledge exists only in people's heads. The console has an Inbox for material sent by people without the reviewer role, and a Questions tab that routes each open question to the person who can answer it. The Chat tab has a Tell mode: the model proposes a card in which every line quotes the person's own words, and only the author's Save records it. Telegram, Slack and Microsoft Teams connect to the same core.

Use it when

What people said appears on entity panels and in the source passport as “According to author (channel, date)”, and is never mixed up with what the code proves.

Annotations: your comments, instructions and synonyms v1.4.0

Attach a comment, an instruction or a synonym to any table, column, mart or the whole project. Text-to-SQL and search use them, so “revenue” can mean the column your business means. A note goes stale on its own when its target changes. Only a person can write one; the MCP tool ekos_annotations is read-only.

How to

ekos annotate add C_BPARTNER synonym "customer" --as ana
ekos annotate add project instruction "Fiscal year starts in April" --rule '{"rule":"fiscal_year_start","month":4}'
ekos annotate list --target C_INVOICE

Apache Ossie interchange v1.4.0

Export the compiled schema as an Apache Ossie semantic model for BI tools. Edit the model and import it back, and your edits become review decisions. Ossie files found in a source are read as knowledge. Their synonyms, joins and metrics then feed text-to-SQL, the dbt semantic layer and search. In the Ask your data demo, Superset reads its schema from EKOS this way.

ekos export ossie
ekos import ossie model.yml      # edits become review decisions; human-only

More in Apache Ossie.

Running EKOS on Azure for a team v1.4.0–v1.4.6

The Terraform module deploys the console to Azure Container Apps with Key Vault, Azure Files and backups. allowed_cidrs restricts ingress. Sign-in can be handled by the platform (GitHub, Google and others through platform_auth = "aca"). A read_only console serves a public showcase, and optional moderation adds abuse checks and daily limits. The Azure video shows both install paths.

More in Deployment.

Coming next