Run your institution as an intelligence.

Governed AI that rebuilds a credit union around the flow of information. The system holds the context, your people hold the judgment, and every agent action is keyed, logged, and killable.

Built for the examiners
NCUAPart 748
FFIECexam-aligned
BSA / AMLSAR-ready
FinCENCTR / SAR
OFACsanctions
GLBASafeguards
FCRAcredit data
SOC 2audit-ready

Start with the work

A member calls, an alert fires, a loan file needs a decision. The answer exists. It is just scattered across the core, the queues, and three people's heads, and today your staff carry it there by hand.

A credit-union officer at their workstation facing a queue of flagged loan alerts, a loan file open on the desk. The work is an information problem.

Four things, not a roadmap

A company organized as an intelligence does not ship a product roadmap. It produces four things, inside NCUA, GLBA, and BSA: capabilities, a world model, an intelligence layer, and the interfaces on top. When a Runner cannot compose a solution, the missing primitive is the next build.

Four things the Framework produces: Capabilities, a World model, Intelligence, and Interfaces, on the Grid and Identity floor, wrapped in governance.
Read the framework

Human oversight, enforced by the architecture

Not by policy, by the Grid. Every agent action passes through one control plane before it ever reaches a core.

Every action passes the Grid: a Runner's action (post journal entry) flows through the Grid, checked by Key, Policy (Allow, Ask, Block), and Audit, with a kill-switch, before it reaches the core and vendors.
  • Kill-switch
    Stop any agent, sub-100ms, in your hands.
  • Audit
    Append-only, hashed, examiner-ready, five-year.
  • Keys
    Scoped per vendor and per agent, through the Grid.
  • Gates
    Human sign-off where a mistake is expensive.
See governance-first

Not a gateway. A Company OS.

Horizontal tools hand you a control plane and a catalog, then leave the credit union to assemble the rest. Runline ships the whole stack, cores to interfaces, tuned to your world and already running.

Primitives versus the running company: on the left, sparse disconnected primitives (model, gateway, keys, logs); on the right, the full connected Runline Company OS stack from cores and vendors up through the Grid, data and world model, Runners, and interfaces.
See the Company OS

Explore the platform

Start from the top
Start here
From hierarchy to intelligence

The thesis, the four things you produce, and how work should feel when the system holds the context and people hold the judgment.

Read the overview
From hierarchy to intelligence
The credit-union anchor and its neighbors: banks, RIAs and funds, and real estate, as warm screenprint portraits under one governed pattern.

Who we serve

Credit unions are the anchor: NCUA-regulated, member-owned, and already outsourcing intelligence work, so the budget line and the vendor-swap path already exist. The same governed pattern carries to the neighbors.

  • Credit unions
  • Banks
  • RIAs & Funds
  • Real estate
Who we serve, and why

For the team building it

The private SDK, the API, the harness, and the full lexicon. Everything needed to compose Runlines on the same primitives our own Runners run on.

The credit union, made executable.

Same people, same members, one governed stack, and far faster information.