The project, the maintainer, the bet.

The bet

Every funded vendor in close + reconciliation + AP shipped agentic AI in 2025–2026. Every one of them keeps the policy chokepoint closed-source. The audit committee can't read the gate; the CISO can't reason about the threat model; the AI architect can't write tests against the controls layer.

closegate's bet is that the chokepoint should be open — not because open-source is virtuous, but because the policy gate, the audit log, and the HITL routing logic are the parts with the least product differentiation and the most regulatory scrutiny. They're the worst possible thing to keep as a vendor moat.

Everything else — the recon engine, the AP 3-way matcher, the eval harness, the workspace UI — is also open. But the chokepoint is the one that matters for whether your AI agent can land in production without your audit committee blocking it.

The project

• Apache-2.0 licensed. Use, modify, distribute, sublicense — including in commercial deployments — subject to standard Apache-2.0 terms.
• 986 passing tests. Reconciliation reference workflow end-to-end functional. AP 3-way matcher end-to-end. SOC 2 Type 2 monitoring loop wired.
• 11 jurisdictions shipping as executable policy.yaml libraries: US (SOX + GAAP), UK (FRS 102 / IFRS / BACS), EU (IFRS / TARGET2 / VAT OSS / GDPR), Japan (J-GAAP), India (Ind-AS / NSE), Australia (AASB / ASX), Canada (ASPE/IFRS / TSX), plus holdco, SOX-public-company, fintech, and SaaS vertical templates.
• 19 MCP tools tier-routed by NIST AI RMF reversibility classification (T0/T1/T2/T3).
• 7 vendor adapters: Stripe, Plaid, Mercury, QuickBooks, NetSuite, Codat, Merge.dev. New adapters typically take ~150 LOC.
• 4-dimension eval harness (matching accuracy, policy enforcement, adversarial robustness, latency) with nightly CI integration via closegate-engine soc2-monitor.

The maintainer

closegate is built and maintained by Dipankar Sarkar, founder of Neul Labs. Background: applied AI research, distributed systems, fintech infrastructure. Solo-maintained today; a formal maintainer organization forms at v1.0 once design partners validate the shape.

Direct contact: closegate@neullabs.com. LinkedIn DM works too — expect a 1-business-day response window, with outliers when an active design-partner engagement is in the deep work phase.

The org

Neul Labs is a small applied-research outfit working on AI infrastructure for regulated industries. closegate is the headline open-source project; commercial engagements are fixed-fee implementation services where Neul Labs ports closegate to a specific jurisdictional + integration shape. The framework remains Apache-2.0 throughout; clients own the deployment.

The roadmap

The public roadmap covers M0 (foundation) through M7 (SOC 2 Type 2, jurisdictions, extensible adapters, ROI surfacing) and points toward v1.0. Full milestone breakdown: ROADMAP.md in the repo.

Pre-1.0, we follow the FastAPI / Pydantic versioning convention: 0.x.y minor releases may contain breaking changes; y patches are additive only. Pin tight (closegate-policy==0.1.0, not >=0.1) until 1.0. Breaking changes always ship a deprecation warning in the prior release plus a migration note in the changelog.

How to participate

• Read the roadmap. Surface gaps that block your team's adoption.
• Open a Discussion. "How do I" + use-case framing. Most-likely place for a maintainer reply.
• Submit a PR. Small fixes (typos, docs, missing tests) merge on a daily cadence when the maintainer is online. Anything that changes policy.yaml schema or the public API needs an RFC first.
• Apply to be a design partner. Two slots per quarter. /contact.

FINOS + the wider OSS ecosystem

closegate is listed in the FINOS Project Hub as a community project. The relationship — including which adjacent FINOS projects inform closegate's design (CDM, Legend, Common Cloud Controls) and why we haven't pursued hosted-project incubation yet — is documented in the repo at documentation/about/finos.md.

Press, attribution, citation

Writing about closegate? Use the project description from the README; grab the logo from /logo.svg (light mode) — the mark is the portal-with-checkmark on the favicon. Apache-2.0 attribution is appreciated; an inbound link to closegate.neullabs.com is the standard form.