Sign In Request a demo
How you buy

The same product. Sold as an engagement.

The loop is on Product. This page is how a team purchases it — against your repos, in your cloud, with evidence an auditor checks without logging into us. An unguarded agent at 3am is not a process. The engagement is.

Request a scoping call The product
Who this is for

Architecture and platform teams who will be asked

Built for architecture and platform teams. A missed cross-repo violation is a hard conversation, not a refactor. Commercial structure is framed against your footprint in the scoping call — not a catalog of SKUs.

The loop, on your estate
Author, Seed, Gate, Record — the same engine in the agent session and on the pull request. You are not buying a second product. You are buying that loop against a defined repo set. Read the product.
Across the repositories that matter
Architecture relationships span repos. A service cannot call what is not declared, regardless of which pull request opens. Federation is how the estate is sold, not a module you pick.
Evidence that stands without us
Every governed merge is signed. An auditor installs a public verifier and checks it offline — no ArchRails account, no API call. Attestation is the record the gate already produces. How the evidence works.
Where policy requires
Run it as a managed service, or have it deployed into your own AWS account so architecture files, graphs, and audit artifacts stay under your keys. Scoped with your platform team during onboarding. GCP and Azure on request.
Beyond a single business unit

One rollout. One audit boundary.

Enterprise is the deployment shape for institutions running ArchRails across two BUs or the whole organization. Named solutions engineer, SLA, source-code escrow, and custom integrations — scoped to the engagement, not sold as extra products.

The signed chain is complete to the promoted commit today. Closing the last hop to the deployed artifact is on the roadmap. If that hop is on your critical path, say so in the call.

The engagement

Four steps. Then you are live.

We run the loop against your real architecture and your actual change volume. Not a slide-ware pilot.

01

Scoping call

Thirty minutes with the founding team. Repos, posture, where the agents already write.

02

Defined repo set

Your CALM, or the draft you will review. The estate in scope is named before anything is stood up.

03

In your environment

Managed, dedicated tenant, or into your AWS account. Decided with your platform team.

04

Kickoff

Committed engagements start within two weeks. SLA, term, and security posture are in the kickoff, not after.

Evidence
Per governed merge
Verifier
Offline, no account
FINOS CALM v1
Open standard
Deployment
Managed or BYOC (AWS)
Source code
Never stored
OSFF London 2026
Speaking June 25 →
Who you are talking to

The founding team takes the call

ArchRails is built by Marc Daniel Registre — prior tenure at Royal Caribbean, McDonald's, LinkedIn, Chase, and American Express. POC conversations go directly to the people who wrote the engine. Patent pending, filed March 2026.

The call

Bring the estate. We frame the engagement.

You walk through where agents already write, where architecture review still lives in people's heads, and what an auditor will ask for. We frame shape, deployment, and commercial structure against that footprint.

Direct response from the engineering team. Typically within two business days.

  • 30-minute scoping call with the founding team
  • Engagement shape framed inside that call
  • Kickoff within two weeks for committed engagements
  • SLA, contract term, and security posture scoped in the kickoff

Request a scoping call

Direct to the founding team. Requests are reviewed within two business days.

Request received. We'll be in touch within one business day.
Something went wrong. Please try again or email pilot@archrails.io.

Use your work email so we can route the request correctly.