Platform

One engine, built for the closing table.

Generation, figure verification, compliance, and the audit trail run on a single set of governing rules, whether a person or an agent drives the deal. Every figure reconciles to your terms, statutory clauses are the operative text of the US authority they cite, and each document arrives with the record of the checks behind it, organized for review.

Read the API reference

From deal terms to a signature-ready binder

  1. 01

    Enter the deal terms

    Enter the deal — program, parties, amounts, and dates. Your firm's standing details fill in from your organization profile, so you add only what is specific to this transaction.

  2. 02

    Figures are derived and clauses are sourced

    Each figure is computed from your terms and the governing program rules, and each clause is the operative text of the statute or regulation that controls it. You confirm every figure before a word of the binder is drafted.

  3. 03

    The checks run, then the file is yours

    The full set is checked against the program rules built into the engine, and an append-only audit log records actions on the deal while each generated document retains the record of the program checks behind it, for your auditors and counsel to examine.

Pre-programmed determinism

The math and the templates are built and verified before your deal runs

A blank assembly tool leaves your firm to template every clause by hand. A tool that drafts the language itself composes each figure and clause on the fly, where fabrication enters. OpenShut hardcodes the federal math and the operative templates ahead of time and verifies them once, so every deal draws on the same checked source and the same terms produce the same binder on every run.

The numbers reconcile to the deal

Loan amounts, rates, fees, coverage ratios, amortization, allocations, and withholding each trace to your inputs and the program rules that produced them. The arithmetic is performed in code, so a credit officer can reconcile any figure back to the term it was drawn from.

Statutory clauses are the operative text of controlling law

Statutory provisions are reproduced word for word from the authority they cite; the remaining clauses come from frozen, source-verified libraries. Every clause carries its citation, so counsel can open the source and confirm the language is the one that controls.

Every figure is computed and checked before it binds

Every figure is computed in code and checked against the program's legal limits before it enters a document. A value outside the range is flagged for you to clear — never silently changed.

The controlling authority

Every clause names the authority that governs it

Each provision traces to a specific US statute or regulation. Below is the body of primary law the engine reads from, organized by area, so your counsel can verify any clause against the controlling source. Live coverage spans SBA 7(a), 504, Express, and CAPLines lending, B2B contracts, the YC SAFE family, Series Seed Equity and Notes, and the Section 83(b) election, with the remaining areas in active build.

Federal lending

  • TILA / Reg Z (12 CFR 1026)
  • RESPA / Reg X (12 CFR 1024)
  • ECOA / Reg B (12 CFR 1002)
  • Dodd-Frank ATR/QM (12 CFR 1026.43)
  • TRID integrated disclosures
  • HMDA / Reg C (12 CFR 1003)
  • Flood Disaster Protection Act (42 USC 4012a)
  • UCC Article 9
  • State usury laws (50 states + DC)

SBA programs

  • 13 CFR 120 (SBA loan programs)
  • SBA SOP 50 10
  • 13 CFR 121 (size standards)
  • Guaranty fee tiers
  • CDC/504 debenture requirements
  • Use-of-proceeds rules
  • Affiliation rules
  • Credit-elsewhere test

Startup financing / securities

  • Securities Act §4(a)(2) (15 USC 77d)
  • Regulation D Rule 506(b) / 506(c) (17 CFR 230.506)
  • Form D (17 CFR 230.503)
  • Accredited investor Rule 501 (17 CFR 230.501)
  • Bad-actor Rule 506(d) (17 CFR 230.506(d))

B2B contracts & data privacy

  • CCPA / CPRA (Cal. Civ. Code 1798.100)

AML & sanctions

  • BSA (31 USC 5311-5332)
  • FinCEN CDD rule (31 CFR 1010.230)
  • USA PATRIOT Act
  • FinCEN BOI rule (31 CFR 1010.380)
  • State money-transmitter laws

Sits inside the stack you already run

CRM

Salesforce, DealCloud, HubSpot, Dynamics 365

A new mandate in your CRM can originate a binder, with party and entity data carried across so nothing is keyed in twice.

Fund administration

Juniper Square, Allvue, eFront, Investran

Investor records and capital accounts reconcile directly from your administrator, so reporting and capital calls draw on the system of record.

Document management

NetDocuments, iManage, SharePoint, Drive

Completed documents are filed into your DMS under the right matter, folder structure, and metadata, ready for the file.

Automation

Zapier, Make, Workato, REST API

Originate a binder from any event in your stack, or route completed documents downstream, with the same governing rules behind every call.

Held to the standard a lender applies to its own files

Encrypted end to end, isolated per organization, and recorded in a tamper-evident audit trail behind every action — with no language model anywhere in the path that reads your data or drafts your documents. We are preparing for SOC 2 Type II; our controls are built to that standard and no report has been issued yet. The full detail is laid out on the security page for your team to review.

See the security detail

Run the engine on a deal of your own.

Generate one document at no cost and examine the figures, the cited clauses, and the program-check record for yourself before you commit a mandate to it. Counsel review is recommended.

See pricing