Skip to main content

§ 01 — Modern Relay

Context &
Coordination
Infra

Designed and built for token-maxxing teams and people.

[Use Cases]

Core use cases

Every team and every agent reads from — and writes to — one governed graph. Context stops scattering across wikis, tickets and DMs.

Company Brain
[State of Affairs]

Intelligence is here. Systems are not ready.

01

Every system still assumes a human.

CRMERPTicketsWorkflows
1 Operatorread · judge · approve

One operator behind every screen.

02

The operator changed.

Agents act as operators.

They don't just ask questions. They deliver real work:

  • Reach across systems
  • Update records
  • Trigger workflows
  • Hand off tasks
  • Write and execute code
03

One agent is easy.

How about dozens?

parallel · same systems · partial context · overlapping decisions

04

Without coordination, they collide.

overwrite · stale reads · no audit trail

Who changed what? No one knows. No one knows why.

05

Today, teams reach for tape.

connectorspluginsscriptsglueworkflows

Every new agent adds another wire. The system gets more fragile.

06

Agents need a substrate.

read
branch
write
merge

Treat knowledge like code. It doesn't exist yet — so we're building it.

[Primitives]

Building blocks

A coordination substrate comes down to the assembly and orchestration of primitives.

Branch

Git-style data branches.

Graph

Typed nodes and edges — semantics and ontology.

Surface

Slack, VS Code, CLI, web — one context.

Policy

Access and governance, defined as code.

Ontology

A model of your domain.

MD File

The native format. Human-readable, agent-editable.

ETL Pipeline

Deterministic and reproducible ingestion.

Object Storage

S3, MinIO, RustFS.

Config

Code defines system behaviour.

Events

Event streaming across the graph.

Notebook

Generative, queryable dashboards.

Lakehouse Files

Open Lance files on object storage.

Omnigraph orchestrates these primitives

[Product]

Omnigraph

The lakehouse-native graph engine for context assembly. The operational state and coordination substrate for agents.

A typed knowledge graph that lives directly on object storage: versioned, branchable and queryable. Agents read from it, write to it, and coordinate through it.

RustLanceS3Cedar
01

Git-style

Versioning, branches, commits and merges over a typed graph.

02

Multimodal retrieval

Graph, vector, full-text and filters across text and blobs.

03

Object-storage native

Runs on S3 or RustFS. Elastic storage.

04

Open format

Lance as the open storage layer — read it with anything.

as code

Schema

Typed .pg schemas — planned, applied, enforced.

as code

Context

Linted queries and agentic nudges, versioned and reusable.

as code

Security

Cedar policies enforced server-side on every mutation.

as code · soon

Dashboards

Declarative views and controls over the graph.

[Deployment]

Deployed on infrastructure you own

Modern Relay's stack is optimised for data sovereignty and maximum infrastructure control.

Option 1

On-prem

Fully inside your own data center.

  • Runs on your hardware, your network
  • Air-gap friendly — no outbound calls
  • Object storage on local disk or on-prem S3
  • You hold every key

Option 2

VPC

In your own cloud account.

  • Deploys into your AWS, GCP or Azure VPC
  • Your bucket, your IAM, your peering
  • Private networking — nothing leaves your tenancy
  • Scales with the cloud you already run

Option 3

Hybrid

On-prem and cloud, one graph.

  • Keep sensitive data on-prem, burst to cloud
  • Branch and sync across environments
  • One control plane spanning both
  • Move workloads without re-platforming
[Careers]

Build with us

We hire high-agency people, genuinely passionate about data engineering, knowledge graphs, ontologies and infra for agents. Small team, high bar, real ownership.

[Backed By]

Our investors

POINT NINE
—Amino—Collective—
emerge
Common Magic