Systems of Record

Built into yours.

Policy administration, claims, ERP, CRM, document stores and data platforms: the system runs on the ones you already have.

Talk to Us Read the Method

Works with the systems you already run
Every connection reviewed by your engineers
Nothing migrated, nothing replaced

import os
from connectors import PolicyAdmin
from connectors.review import engineer

system = PolicyAdmin(
    environment=os.getenv("CLIENT_ENVIRONMENT")
)

link = system.records.connect(access="read-only")
link.append(engineer("Integration review"))

result = link.verify()
print(result.audit_trail)

import { policyAdmin } from "@client/connectors";
import { connect } from "@client/review";

const { record } = await connect({
  system: policyAdmin.records("read-only"),
  reviewer: "Integration review",
});

console.log(record);

import Connector from "@client/connectors";

const client = new Connector({
  environment: process.env.CLIENT_ENVIRONMENT,
  baseURL: "https://systems.internal/v1",
});

const response = await client.records.policies.connect({
  access: "read-only",
  reviewers: [{ role: "engineer", name: "Integration review" }],
});

console.log(response.records[0].audit_trail);

curl https://systems.internal/v1/records/connect \
  -H "Authorization: Bearer $CLIENT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "access": "read-only",
    "reviewers": [
      { "role": "engineer", "name": "Integration review" }
    ]
  }'

How a system connects

Connected to the systems you already run

Every connection is scoped with the people who do the work, reviewed by your engineers and logged before the first record moves.

Start at the scoping session.
Review each connection with your own engineers.
Connect read-only to the system of record and start with Guidewire.

Works through the interfaces your engineers already approved, in Python, TypeScript or REST.

Talk to Us How a connection runs

systems.internal

Connections

guidewireconn-••••••••••••••••3kf9Aug 3, 2026Active
salesforceconn-••••••••••••••••q7d2Jul 19, 2026Active

Every connection is reviewed by your engineers and logged.

Systems we build on

Talk to Us How a connection runs

Every connection is scoped, reviewed and logged. Nothing is migrated and nothing is replaced. The system of record we connect most often is below. How each one is connected is written in the blueprint.

System	Connects	Records read daily	Read access	Write access
GuidewireCorePolicy administration, billing and claims for insurers. The system works through the interfaces your engineers already approved, and every action is logged against the record it touched.	Records in, to the system of record	500k	01	02

**CRM and service**Accounts, cases and service requests
System	Read access	Scope	Write access
salesforceAccounts, documents → Records	01	Read and write	02
servicenowRequests, tickets, approvals → Records	01	Read and write, approvals	02
policy-documentsAccounts, documents → Records	01	Read and write	02
document-storesAccounts, documents → Records	01	Read and write	02
email-intakeLetters, forms, attachments → Records	01	Read, then write	02

**Finance and data**ERP, data platforms and warehouses
System	Phase
SAP	01
Snowflake	02
Your data warehouse	03

Included in every engagement

Every connection reviewed by your engineers

Before anything goes live, your engineers review each connection: what it reads, what it may write, and who approves it. Nothing is migrated, nothing is replaced, and every action is logged against the record it touched.

Talk to Us

Everything we build on

Policy administrationGuidewire and the policy platforms insurers already run: quotes, endorsements and renewals.
ClaimsClaims systems and the documents around them, read and filed against the right record.
ERPSAP and the finance systems behind it: ledgers, invoices and reconciliations, matched record by record.
Document storesContracts, policies, letters and site reports, read where they already live. Nothing is copied out.
CRM and serviceSalesforce and ServiceNow: accounts, cases and service requests, updated where your team already works.
Finance and dataSAP, Snowflake and the warehouses your reports come from, with the model each step uses written down.

Enterprise

Controls that get a system through a security review

The Lyrion systems run under your controls: single sign-on, audit logging, residency and named engineers, on the platforms your team already runs.

Talk to Us Enterprise FAQ

Access and audit loggingSingle sign-on, role-based access, and every action logged against the record it touched.
Your EnvironmentAble to run inside your own environment where residency requires it.
Approvals you defineApprovals sit wherever your team wants them, and nothing leaves the building without a person.
ResidencyProcessing kept in the region your regulators require.
Systems of record untouchedNothing is migrated and nothing is replaced. The system works through the interfaces you already run.
Approvals wherever your team wants themThresholds set per process, so routine work flows and exceptions go to a person.
Never used to train a modelYour data is never used to train a model, and retention follows the policy your team sets.
Named engineersThe engineers who connected the system operate it after go-live.

Every action, logged in the Lyrion Audit Trail

Every connection, every approval and every action in one record, readable by your team and ready before the auditor asks.

Talk to Us

Choose how to begin

One process first

Most engagements begin with:

A scoping session with the people who do the work
A written blueprint before anything is built
A system built inside your own platforms
Your engineers review every connection before go-live

Scoping Session

Then the next

The ones that earn it extend from there, department by department.

The same engineers operating what they built
Approvals wherever your team wants them
An audit trail ready before the auditor asks
Encrypted in transit and at rest
Able to run inside your own environment

Talk to Us

Runs on the cloud you already trust

The system runs in your own environment, on Microsoft Azure, Oracle Cloud or Google Cloud, under your controls.

Your Azure tenant

Microsoft Azure

Where it runs

Your Oracle tenancy

Oracle

Where it runs

Your Google Cloud project

Google Cloud

Where it runs

Field notes

All notes

Field noteSep 21, 2026

What it takes to move AI beyond the pilot

The Written Blueprint, on an orange and violet gradient

Sep 18, 2026

What a written blueprint contains, and why it comes first

Five Processes, on a plum and orange gradient

Field noteSep 16, 2026

Five processes usually worth building a system around

Sep 3, 2026

Approvals, audit trails, and who signs for what

Frequently asked questions

How does Lyrion connect to our systems?

It starts in the scoping session, where we name every system the process touches. Your engineers review each connection, and the system reads the system of record before it writes anything.

Does anything get migrated?

No. Nothing is migrated and nothing is replaced. The system reads and writes through the interfaces your systems of record already expose, under the access your team grants.

How does a connection go live?

Lyrion connections run in phases: Guidewire, like every system, starts in phase 01 with read access and moves to phase 02 for write access, only after review.

How each phase runs is written in the blueprint.

Can our own engineers review the connections?

Yes. Every connection to the system of record is reviewed by your engineers before go-live, and the Lyrion engineers who built it walk them through every scope.

Which systems of record do you build on?

Policy administration, claims, ERP, CRM, document stores and data platforms: Guidewire, Salesforce, SAP, ServiceNow and Snowflake among them. If your team runs it and it exposes an interface, the system can work through it. Which ones a process touches is settled at scoping and written into the blueprint. Nothing is migrated, nothing is replaced.

Where is each connection documented?

Every connection is written into the blueprint. This page covers the systems we build on and how each one connects.

Can the system run in our own cloud?

Yes. Systems run in your own environment where residency requires it, on Microsoft, Oracle, Google or Amazon platforms, under the controls your team already runs.

Who approves what the system does?

Your people. The Lyrion systems hold approvals wherever your team wants them, log every action, and come with a BAA where you need one, plus residency and named engineers. To scope your first process, talk to us and we will set up a scoping session.

Which models do the systems use?

Each system runs on the model each step needs, chosen per step and written down, and model governance covers how a model changes: only under change control, and never trained on your data.