Private beta · by invitation

Ando Engine. From knowledge to context.

Ando Lab develops Ando Engine: connect enterprise knowledge, retrieve relevant evidence and select context for AI applications. Explore UKS, TRAMA and our internal evaluation results.

Request an invitation See how it works

UKS connects. TRAMA navigates. Sources stay visible.

Inside Engine

Same question. Two paths. Two answers.

With many complex sources, the work done before a question changes how much the model must search, read and reconstruct.

Illustrative scenario

Could component AX-44 put Atlas at risk?

Live search across tools

Question → ERP / CAD / PDF ↻ → Search again

Navigation on the map

Question → UKS network → TRAMA → Evidence

Multiple MCPs

Explore everything at query time.

The agent calls tools one after another. Each result reveals only part of the systems; links between ERP, CAD and documents must be rebuilt in the prompt.

MCP · ERPMCP · CADMCP · PDF

Call tools
Accumulate outputs
Attempt joins in prompt

Context window · raw outputs and tokens

ERP JSONCRM recordCAD rev ACAD rev CPDF p.7PDF p.28SQL rowsE-mailnotes…

More live search · risk of a wrong answer

“No risk to Atlas.” If PO-4821 is not linked to revision AX-44, the decisive evidence is missed.

Ando
Engine

Prepare the network. Then answer.

During ingestion UKS profiles, reconciles, deduplicates and versions entities. TRAMA traverses the prepared network and selects relevant evidence.

ProfileReconcileVersionTrace

UKS prepares the network
TRAMA selects
The model cites sources

Context window · selected evidence only

PO-4821 · ERP

AX-44 rev C · CAD

Atlas milestone · PDF

Less runtime work · answer with sources

“Yes. PO-4821 arrives 14 days after the Atlas milestone.” The ERP order and AX-44 revision are linked and verifiable.

Illustrative scenario, not a benchmark. MCP is a protocol and can include servers with ingestion; the left path represents live tool access alone. Paired tests are needed to compare latency, tokens, cost and accuracy.

One engine, all your knowledge

Structured and unstructured. Together, at the same quality.

Engine queries data, documents and complex enterprise systems in the same reasoning path and returns answers verified against real sources.

Structured dataERP · CRM · Databases

Unstructured dataDocuments · Email · CAD

Complex systemsVerified answers

Measured, not promised.

+18.8%

HERB Hit@5: internal paired test

0.512 → 0.608 · n=125 · Hit@1 regresses

0.782

FinQA internal MRR@5

n=500 · not a matched literature comparison

0.338

BRIGHT/pony internal MRR@10

0.239 → 0.338 · exploratory · n=20

HERB measures the gain from graph fusion when evidence is distributed across textual sources. Live ERP/database + document joins are validated internally, but no equivalent public benchmark exists yet.Internal measurements: methodology and limitations

From source to answer, without losing the thread.

One engine ingests data, understands it, builds Clean Knowledge and finds a verifiable answer. UKS keeps knowledge coherent and current.

Enterprise knowledge

Information stays across the organisation’s systems and repositories.

DatabasesERP and CRMDocumentsEmailCAD and PLMSpreadsheets

Security and governance

Every access follows the authorised identity, role and data perimeter.

PII detectionUser data segregationRBACEncryption

TRAMA

Ando’s proprietary engine manages the entire knowledge cycle, from source to answer.

03 · UKS

Unified Knowledge Schema

Profiles sources, resolves entities and builds a coherent map of enterprise knowledge.

ProfilingEntity resolutionMappingDeduplication and repair

Retrieve · Reason · Act

Retrieve

Selects only the context needed for the request from the available sources.

Reason

Traverses relationships, compares evidence and builds a verifiable answer.

Act

A team of action agents calls authorised tools, APIs and workflows.

Agentic APIConsoleMCP · Coming soon

Guided preview

From first connection to first answer.

An illustrative journey through a source, files and the UKS/TRAMA network preparing traceable evidence. Connections are enabled after early access is granted.

Choose a source

Connect what you already use.

40 connection pathsPrivate beta catalog · invitation required

Databases, CRM, files and technical systems enter the same knowledge space. No migration: authorise, verify read-only access and sync.

Data and custom10

PostgreSQLPrivate beta

MySQLPrivate beta

Microsoft SQL ServerPrivate beta

OraclePrivate beta

SQLitePrivate beta

SpreadsheetsPrivate beta

Push APIComing soon

REST ManifestComing soon

On-prem DB BridgeComing soon

AutoCAD / DXFComing soon

Business5

SalesforceComing soon

HubSpotComing soon

TrelloComing soon

Fatture in CloudComing soon

SAP Business OneComing soon

Files and knowledge6

Manual document uploadPrivate beta

Google DrivePrivate beta

OneDrivePrivate beta

SharePointPrivate beta

NotionPrivate beta

NASComing soon

Communications11

GmailPrivate beta

Outlook MailPrivate beta

Aruba MailPrivate beta

Microsoft TeamsPrivate beta

Google ChatPrivate beta

SlackPrivate beta

WhatsAppPrivate beta

Google CalendarComing soon

Outlook CalendarComing soon

Aruba PECComing soon

InfoCert LegalmailComing soon

Finance and compliance8

Open Banking · A-CubeComing soon

SDI e-invoicingComing soon

Cassetto FiscaleComing soon

VAT verificationComing soon

Legal storageComing soon

Peppol GatewayComing soon

Invoice extractionComing soon

Aruba SDIComing soon

Can’t find your system? Connect it anyway.Custom connectors let you integrate proprietary software, internal APIs and legacy systems: define authentication, data and synchronisation to bring any source into Engine.

Authorise · verify · syncConnection verified · read only

PostgreSQLsupply_chainConnection verified · read only

Add filesspecification_AX44.pdfUploaded and verified

KnowledgeTRAMA

Updating Unified Knowledge Schema

Answer preview · access coming soon

Could component AX-44 delay Atlas?

Yes. PO-4821 expects delivery 14 days after the Atlas milestone.

PO-4821 · row 8specification_AX44.pdf

What you can build with Engine.

Console · API

Request an invitation

How you use Engine

One engine. More ways to use it.

Console and APIs bring the same knowledge into invitation-only beta workflows. MCP access will follow in a later phase.

Console

Ask questions, follow evidence and manage sources in a guided interface.

API

Bring answers and sources into your products with an AppKey and scoped permissions.

MCP

Coming soon

Engine as a tool in compatible AI clients, backed by prepared knowledge.

An API example

The request and response below illustrate API integration; they are neither a Console screen nor a live call.

POST/platform/v1/agentic/answer

curl https://api.ando-ai.com/platform/v1/agentic/answer \
  -H "Authorization: Bearer $ANDO_APP_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "Could component AX-44 put Atlas at risk?",
    "sources": ["structured"],
    "max_steps": 6
  }'

AppKey · sources:read · max 6 steps

Verified output

Verified answer

Yes. Delivery of PO-4821 is scheduled 14 days after the Atlas milestone.

Evidence

01purchase_orders.po_4821 · row 8
02Atlas_BOM.xlsx · AX-44 rev C · row 284
03Atlas · October milestone

ContextSelected

SourcesTraceable

AccessComing soon

Private beta access

Tell us what you want to connect.

We review every request personally. You will receive an email confirmation right away; we will contact you about Console and API access.