Your AI agents are running on docs from 2019.

The codebase is the only thing that's actually true.

Wikis lie. Diagrams drift. The retiring engineer hates writing documentation. newinsights.ai makes the source code itself the knowledge base — audit-grade documentation, business overviews and architecture diagrams generated and verified from code on every commit.

Code-to-knowledge platformFor regulated DACH financial services
On-prem · BYO keys · DORA-alignedSource code never leaves your perimeter
Legacy code base support25+ supported languages
The Gap

Three uncomfortable facts you already know about deploying AI in legacy app landscapes.

01

You want to ship faster. Every release is still a gamble.

A change to one core system touches forty others — and the map of those dependencies lives in people's heads, not in any system of record. You approve the release. Then you find out what it broke.

02

AI coding agents are now writing your new code. They learn from your stale docs.

Every coding agent grounds itself in old documentation and the minimal context it holds in a session. Bad docs propagate into bad code, faster than ever before.

03

The senior engineer who knows the legacy core retires in eighteen months.

The cost of finding out what they knew, after they leave, is not a documentation cost. It is a transformation programme that stalls.

Wrong vs. verified

Same function. Different documentation. One of these will pass an audit.

wiki / payments-core CONFLUENCE · LAST EDITED 2021
Settlement Engine
unverified · drift unknown

"Handles settlement of payments. Uses the legacy clearing system. Owned by the Payments team. See PROJ-1184 for details."

Three years stale. The legacy clearing system was decommissioned in 2023. PROJ-1184 was archived. The Payments team was reorganised twice. None of this matches the code.
newinsights / payments-core VERIFIED · 18 DEC 25 · COMMIT a3f12c8
Settlement Engine
verified against 14 source lines · 6/6 quality criteria

Reconciles intra-day SEPA Instant payment messages against the ledger and emits T+0 settlement instructions to the Bundesbank gateway. Replaces the legacy clearing path decommissioned in PROJ-2019.

cited: settlement_engine.py:42-89, sepa_validator.py:15-31, ledger.py:204

Based on the peer-reviewed research arXiv:2504.08725

What we do

A code-to-knowledge platform. Not a documentation tool.

The difference: documentation tools take what you write and make it look nice. We take what your code actually does and turn it into the knowledge your organization needs.

01
Living docs, not one-shot
Re-runs on every commit. The documentation a regulator reads next quarter reflects the code that shipped this morning.
02
Verified, not hallucinated
A dedicated Verifier agent rejects outputs that don't meet the bar. Failed drafts are rewritten — automatically — until they pass.
03
Grounded, not guessed
A dependency map is built from the source itself, function by function, call by call, before any LLM is involved. Documentation describes what's true in the code — not what sounds plausible.
04
On-prem & BYO keys
Single Docker image inside your firewall. Use your own Azure / GCP / OpenAI / Bedrock / self-hosted endpoints. We never see the source code.
Who's behind this

Built by the people who have lived this problem.

Ryan Grenier
Ryan Grenier
Founder & CEO

Most recently a Managing Director in Commerzbank's Big Data Group in Frankfurt, Germany. Previously a GM at Amazon AWS, CMO of Rackspace (Nasdaq: RXT), Head of Product at two successfully exited startups and Yahoo!

Shriram Ramamurthy
Shriram (Ram) Ramamurthy
Founder & CTO

Lead platform and engineering development at Telescope Partners, a SF-based VC with $900M AUM. At Amazon and AWS Ram built massive scale systems for ultra-fast grocery delivery and gaming infrastructure.

Stop guessing what your code does.

Closed beta with a small group of regulated banks and insurers in DACH. If documentation gaps are on your risk register, write to us.

No marketing list. One reply from a founder.