We use only essential, cookie‑free logs by default. Turn on analytics to help us improve. Read our Privacy Policy.

37lab / product

37lab Core

Agents, memory, workflows — on infrastructure you own.

Core is the platform layer every 37lab system stands on. This page assembles it in front of you, layer by layer — in the same order we build it for real.

↓ Scroll — the platform assembles as you read.

APISSERVICESDATABASEMEMORYHITL GATEFIG. 03 — CORE · ASSEMBLY VIEWSOVEREIGN BY DESIGN

01

Ontology

The map comes first.

Before any agent acts, the platform has to know what exists: your entities, your systems, your processes, the words your company actually uses. Core starts with a semantic layer — a working map of your organization that every agent shares.

Every answer traces back to something on that map. That is what keeps a platform grounded — not bigger models, but a floor of verified meaning under every step.

IN PRODUCTION· Trace-based ontology derivation — in development.
APISSERVICESDATABASEMEMORYHITL GATEFIG. 03 — CORE · ASSEMBLY VIEWSOVEREIGN BY DESIGN

02

Connections

Bridges, not integrations.

Core reaches your world through MCP — the open Model Context Protocol. Your databases, your internal APIs, third-party services and the platform's own long-term memory are all servers on the same bus.

A new capability is a new bridge, not a rebuild. And every bridge is inspectable: you can see exactly what crosses it, in both directions.

  • Databases — Postgres, warehouses, vector stores
  • APIs — internal services and third-party systems
  • Services — mail, calendars, messengers, ticketing
  • Memory — the platform's own recall, as a first-class server
IN PRODUCTION
APISSERVICESDATABASEMEMORYHITL GATEFIG. 03 — CORE · ASSEMBLY VIEWSOVEREIGN BY DESIGN

03

Agents

Inhabitants, not chatbots.

Agents live on the platform. Each one holds a role, carries its own context, and works through the bridges — a researcher, an operator, an investigator, cooperating on shared ground.

They are not wrappers around a prompt. They keep state, they hand work to each other, and they leave an audit trail of everything they touch.

IN PRODUCTION
APISSERVICESDATABASEMEMORYHITL GATEFIG. 03 — CORE · ASSEMBLY VIEWSOVEREIGN BY DESIGN

04

Workflows

Stairs with gates.

Work moves along explicit routes: multi-step workflows with branches, retries and escalation — the staircase the whole system climbs, continuously.

Where a step is irreversible — money out, message sent, records changed — the route passes a human-in-the-loop gate. Nothing crosses without a nod. The loop is perpetual; the gate is yours.

IN PRODUCTION
APISSERVICESDATABASEMEMORYHITL GATEFIG. 03 — CORE · ASSEMBLY VIEWSOVEREIGN BY DESIGN

05

Sovereignty

The dome over everything.

Your keys, your endpoints, your jurisdiction. Core runs where you need it to: EU cloud, your own servers, fully air-gapped if that is what your regulator requires.

Data orbits inside the dome and never leaves. Models are reached through your own keys, so no vendor sits between you and your system.

IN PRODUCTION· Managed cloud tier — on the roadmap.
APISSERVICESDATABASEMEMORYHITL GATEFIG. 03 — CORE · ASSEMBLY VIEWSOVEREIGN BY DESIGN

Assembled.

This is the tower from our front page — you have just watched it being built. Ontology as the ground, bridges as reach, agents as inhabitants, workflows as the endless stair, sovereignty as the sky. One platform. Your house.

Statuses on this page reflect what runs in 37lab's own production stack today — not a roadmap dressed up as a product.

Want this standing on your infrastructure?

We deploy Core as the foundation of every 37lab engagement — scoped to what you actually need, owned by you from day one.

Start a project