Neuryn
Start free

01 / About

We build the thing
we kept rebuilding.

Neuryn started because two of us spent a quarter reconciling key rotation logs across three clouds, by hand, in a spreadsheet, during an audit.

02 / Origin

The audit passed. That was the frustrating part.

Everything we needed existed somewhere. The access logs were in three consoles. The schema history was in version control, sort of. The list of which pipelines read which column lived in the head of someone who had changed teams. We assembled the answer, we shipped it, and the auditor was satisfied.

Then we did it again eleven weeks later. It became obvious that the work was not the audit. The work was that nobody had built the place where this record was supposed to live, so it was reconstructed from scratch every time someone asked. That place is what Neuryn is.

Founded
2023
Rows validated / min
4.2M
Customers
340+
Countries
19
Uptime, trailing 12mo
99.98%
Team
31

03 / Principles

Four opinions we keep having.

  1. 01

    Check at the edge

    A validation that runs in the warehouse is an autopsy. The only place a check is still cheap, and still actionable, is the moment the record arrives.

  2. 02

    Never delete evidence

    Rejecting a record and destroying it are different acts with different consequences. We quarantine. Storage is cheaper than an unanswerable question.

  3. 03

    One clock, one format

    Three providers give you three logs and three notions of time. Reconciling them during an incident is not a task, it is a week. We record once, centrally, in order.

  4. 04

    Boring beats clever

    Most breaches begin with an over-scoped token, not a novel exploit. We spend our effort on the unglamorous 31 percent rather than the exotic tail.

04 / Timeline

Four years, one idea.

2023
Founded after two of us spent a quarter reconciling key rotation logs across three clouds by hand.
2024
First production deployment. The validator was a queue and it topped out at 300,000 rows a minute.
2025
Rewrote validation to run on the ingest node. Fourteen times the throughput on the same hardware.
2026
SOC 2 Type II, self-hosted build, and the first customer running Neuryn across four regions.

05 / Team

The people who write here.

Everyone publishing on this site works on the product. Nothing here is written by someone who has not run the thing they are describing.

06 / Contact

Come and break it.

We are more interested in the pipeline that defeats us than the one that works. Tell us about yours.

Get in touch See the platform