closegate
Install Talk to us

Contact

Talk to the maintainer.

Two design-partner slots open this quarter. The conversation is worth it whether closegate ends up being the right fit or not.

closegate is solo-maintained today. If you're scoping AI agents against close, reconciliation, or AP, the fastest way to compare notes is to send the maintainer three lines about your workflow, your binding audit constraint, and where the agent sits in your stack — then book a 30-minute call.

Send a message

Design-partner intake, integration questions, SOX-scoping, or anything procurement-shaped — this goes straight to the maintainer. Typical response within one business day; FCFS on the design-partner slots.

Other ways to reach us

  • Email: contact@neullabs.com. Best for design-partner intake, integration questions, and anything procurement-shaped. Typical response within 1 business day.
  • LinkedIn DM: Dipankar Sarkar. Best for ad-hoc questions, comments on the long-form articles, or "I saw your post" follow-ups.
  • GitHub: https://github.com/neul-labs/closegate. Discussions for "how do I" + use-case framing, Issues for reproducible bugs. Security disclosures go through the channel in SECURITY.md — never GitHub Issues.

What you get

  • Direct line to the maintainer. No support tier. No SLA bot.
  • Co-design influence on the v1.0 surface — your jurisdictional shape gets first-class support in the next minor release.
  • Reference implementation your auditor, CISO, and architect can all read from the same git commit.
  • Zero seat licensing — forever. Pay for self-hosted compute only.
  • Case study collaboration (anonymized fine) once the pilot graduates to production.

What we ask in return

  • One real workflow (close, recon, or AP)
  • Your real policy.yaml shape (we adapt to it, not the other way around)
  • Monthly 30-minute call to walk through what broke
  • Permission to publish a case study with your numbers attached (anonymized fine)

What we won't do

  • Sell you closegate if your shape fits a commercial vendor better. We'll tell you straight; the comparison page is honest about where each option wins.
  • Promise an SLA we can't keep pre-1.0. We're solo-maintained; a 5-business-day response window is the goal, outliers happen.
  • Sign an NDA before the first conversation. The framework is open-source; we have nothing to protect at the discovery stage.