PRODUCTS · AKILI · LICIA
LEYSCO AKILI · LICIA — EARLY ACCESS · PRE-PRODUCTION

The assistant is the architecture.

Leysco Licia calls the same typed services the screen calls — every action entitlement-checked, correctness-gated, and written to a tamper-evident audit chain. Early access.

Request early accessHow Leysco Akili is built
2026-06-01first boot
repo-governance
RECEIPT · FIRST BOOTThe platform API booted as a running system for the first time on 2026-06-01 (health endpoint returning 200) — a dated, repo-recorded milestone, not a launch claim. — Leysco Akili repo milestone record, verified 2026-07 · repo-governance
21modules designed
repo-governance
RECEIPT · 21 MODULES DESIGNED21 modules designed on the platform's own native core — not a re-skin of anything else — in early access, ahead of general release. Module count per the platform specification and repository governance docs. — Leysco Akili platform specification + repo governance docs, verified 2026-07 · repo-governance
30sprints closed
repo-governance
RECEIPT · 30 SPRINTS CLOSEDThirty development sprints closed and recorded in the repository's governance docs (Sprints 1–30). Early access means you can watch the cadence, not just the promises. — Leysco Akili repo governance docs, verified 2026-07 · repo-governance
Pre-production · watch the cadence, not the promises
ON LEYSCO AKILIEarly accessEarly access. Pre-production — no customers yet. Built and governed in the open: dated milestones, sprint cadence, honest chips.
The category

AI-native ERP assistant / governed agent platform

The names you'll be comparing

SAP Joule · Microsoft Copilot (D365) · Salesforce Agentforce

The difference

They bolt an assistant onto a finished suite. Here the assistant and the screen call the same governed services, under one permission model for humans and AI — stated as architecture, chipped Early access.

code-inventory
RECEIPT · SAME TYPED SERVICESLeysco Licia calls the same typed services the screen calls — the assistant is a first-class caller of the platform's service layer, not a bolt-on chat box. — Leysco Akili service architecture (Leysco Licia embedded copilot, code path), verified 2026-07 · code-inventory

agent → tools/listSCOPED BY ROLE
semantic.query
propose_journal_entry → DRAFT
resolve_master_data
ingest_document
… typed tools
ONE GOVERNED SURFACE — FOR LICIA AND ANY EXTERNAL AGENT

Every AI action is a governed tool call.

The gateway

An MCP tool server exposes the platform as typed, permissioned tools — to Licia and to any external agent. The propose-to-draft pattern: propose_journal_entry returns a DRAFT. The agent proposes; the platform decides.

code-inventory
RECEIPT · GOVERNED TOOL SERVERAn MCP tool server exposes the ERP as governed, typed tools to any external AI. The propose-to-draft pattern: propose_journal_entry → DRAFT — the agent proposes; the platform decides. — Leysco Akili MCP tool server (code path: propose_journal_entry→DRAFT), verified 2026-07 · code-inventory

DOPS · GATEDETERMINISTIC
mandatory fieldschecked
balance assertedchecked
ask-then-actenforced
read-back verifyrequired
IF THE NUMBERS DON'T VERIFY, NOTHING POSTS

Zero silent mistakes, by design.

Correctness

Between any model and any posting sits DOPS — a deterministic gate: mandatory-field checks, ask-then-act, read-back verification. If the numbers don't verify, nothing posts.

code-inventory
RECEIPT · CORRECTNESS GATEDOPS — a deterministic correctness gate between the AI and any posting: mandatory-field checks, ask-then-act, read-back verification. Zero silent mistakes by design. — Leysco Akili DOPS gate (code path), verified 2026-07 · code-inventory

action 0#a91f… action 1#3ce7… action 2#7b02… action 3#d144… action 4#e8aa… EACH ACTION HASHES THE PREVIOUS — TAMPER-EVIDENT · APPEND-ONLY

Audited like a ledger, because it writes to one.

Trust plane

PII routing, injection defense, output-integrity checks, cost ceilings — and a hash-chain audit of every AI action. The same discipline the ledger gets, applied to the model.

code-inventory
RECEIPT · TRUST LAYERA mandatory trust plane around every model call: PII detection and routing, injection defense, output-integrity checks, cost ceilings, and a tamper-evident hash-chain audit of every AI action. — Leysco Akili AI Trust & Governance layer (code path), verified 2026-07 · code-inventory

MODEL ROUTINGPROVIDER-AGNOSTIC
ProviderRoutingTier
Claudetiered by taskcloud
Ollamaself-host default$0 local
MODEL CHOICE IS A CONFIGURATION ROW, NOT A PROCUREMENT CYCLE

Your ledger never has to leave the building.

Model freedom

Claude tiers routed by task — or local Ollama as a $0 self-host default. Provider-agnostic by architecture, so model choice is a configuration row, not a procurement cycle.

code-inventory
RECEIPT · MODEL FREEDOMModel freedom with a self-host default: Anthropic Claude tiers by task plus local Ollama — a $0 local tier. Your ledger never has to leave your building to be intelligent. — Leysco Akili multi-model routing (IChatClient providers: Claude + Ollama), verified 2026-07 · code-inventory

The platform under Licia.

In this line
Document ingestion (email/WhatsApp/PDF → governed draft)Early accessReceipt in, postable draft out.
Master Data ResolverEarly accessMoney-safe fuzzy entity resolution.
Semantic Layer — governed metricsEarly accessOne measure, three renderings.
MCP Tool Server & agent gatewayEarly accessThe governed surface itself.
Immutable multi-book ledgerEarly accessINSERT-only, enforced in persistence.
Schema engine (~375 schemas → database)Early accessConfigure-not-code substrate.
Authorization — one chain, humans + AIEarly accessRBAC/RLS/FLS/SoD incl. 12 ai.* permissions.
3-tier multi-tenancyEarly accessTenant-bound isolation and secrets.
Licia standalone — bring your own ERPEarly accessSame assistant against SAP B1, ByD, BC, NetSuite.
AI eval harness & injection-defense toolingDesignedCompletion-proof for AI features.

Watch an agent get governed.

Signature · Early access · recorded from development environment · synthetic data

A deterministic replay of a real session shape: the agent lists its tools, asks a governed question, proposes a journal entry — and the platform answers with a gate, not an execution.

code-inventory
RECEIPT · GOVERNED TOOL SERVERAn MCP tool server exposes the ERP as governed, typed tools to any external AI. The propose-to-draft pattern: propose_journal_entry → DRAFT — the agent proposes; the platform decides. — Leysco Akili MCP tool server (code path: propose_journal_entry→DRAFT), verified 2026-07 · code-inventory

mcp session · replay · 2026-06 dev env
  1. agent→ tools/list
  2. akili← typed tools · scoped by role: semantic.query, propose_journal_entry, …
  3. agent→ semantic.query { measure: "expenses.total", period: "2026-05", by: "cost_center" }
  4. akili← 12 rows · governed model · RLS applied for this principal
  5. agent→ propose_journal_entry { debit: "6200-FUEL", credit: "1000-PETTYCASH", amount: 18500 }
  6. DOPSGATEmandatory fields OK · balance asserted · read-back required → returned as DRAFT je-2026-000418, not posted
  7. akili← audit: action hash-chained · cost metered · awaiting human approval
THE AGENT PROPOSES. THE PLATFORM DECIDES. · EARLY ACCESS — PRE-PRODUCTION
1.66M+invoices
sql-count
RECEIPT · 1.66M+ INVOICES1,666,107 invoices posted in a single hosted customer system — SAMWEST hosted production DB (SWD_LIVE), countable live in the SAP ledger. — SAMWEST hosted production DB, verified 2026-07 · sql-count

The team behind this platform runs 1.66M+ posted invoices in production today — on Leysco100, its sibling house. Licia inherits the team and the domain depth; it claims none of those numbers as its own.

Two houses, independently built. Choose by fit — neither is a stepping stone to the other.

Built for operations that…
  • want to shape an agent-operated ERP from the inside, as a design partner
  • need AI that can act — under entitlements, gates and audit — not just chat
  • have a data-residency posture that prefers a self-host model tier
  • are comfortable with Early access software and honest chips
The old way → this way

A chat box beside the ERP, guessing at screens → a governed caller inside it

Choose by fit. Need it running this quarter, on Kenyan rails, with referenceable proof — Leysco100. Building the agent-operated enterprise and want to shape it from the inside — Leysco Akili early access.Both come with the same team, and neither is a stepping stone to the other.

Part of the house.

Related

MCP Gateway

The governed tool surface.

Early access

Semantic Layer

Governed metrics under every answer.

Early access

The Leysco Akili house

The platform Licia is woven into.

Early access

Designed by the team whose sibling house runs East African distribution floors — informed by that experience, not derived from that code.

Shape the assistant from the inside.

Early access. Honest chips. Nairobi · EAT.
Request early access
Talk to us · WhatsApp +254 780 457 591