Skip to content

We built ARTHR because generic AI wouldn’t cut it.

RegAlytics exists because the people trying to build on regulatory data hit the same wall: scraping is brittle, generic LLM extraction hallucinates, and nobody wants to staff the regulatory research team a GRC platform needs. So a small group of regulatory experts and engineers built ARTHR from the ground up, a system purpose-built for regulatory intelligence, then kept it running for every GRC platform, bank and consulting group that now depends on it.

Join us

Infrastructure, not a compliance tool.

The industry has plenty of compliance tools. What it does not have is a data layer that all of them can build on. We chose the infrastructure posture deliberately. Our customers sit on top of us, not next to us. They win their end-customer, keep the relationship, and own the product. We keep the regulators, the classifications, and the feed.

That framing shapes everything from the API design to how we run the on-call rotation. Getting it right means our customers ship faster; getting it wrong means a whole industry keeps paying for regulatory research they should not have to.

The four beliefs the product is built on

Regulatory data is infrastructure. It should be consumed like a database, not copy-pasted from a PDF. Every product decision follows from that.

Buy vs build has a right answer. For GRC vendors, running a regulatory data team is a distraction. Our job is to be the boring, dependable feed they can build on.

AI alone is not enough. Generic LLMs hallucinate regulators, miscount jurisdictions, and confidently lie about effective dates. ARTHR is purpose-built, auditable and specialised.

The practitioner still matters. Compliance SMEs were our first users. Dev-first does not mean compliance-second. The practitioner lane stays first-class.

The ARTHR cast

ARTHR is the system. It is named for the project that produced it, and the internals are named after the rest of the legend. Each component does one job and hands the result to the next.

GAWAIN

The crawler fleet. 11,480 regulators monitored around the clock with regional redundancy. The knight that never sleeps.

PERCIVAL

The extraction and classification engine. Turns regulator PDFs and bulletins into normalised JSON tagged against a shared taxonomy.

LADI

Linked analytics. Connects alerts to regulators and regulations so questions like “everything cyber in the US since Q1” have a one-query answer.

SWORD

The delivery layer. MCP server, REST v3, webhooks, flat files. The customer-facing surface of the data layer.

Who builds it

A senior team drawn equally from regulatory compliance and platform engineering. Former compliance officers, former data platform leads, and people who have sat on both sides of a regulator’s questions during a bank audit. The leadership team is listed on LinkedIn and in press coverage, and full bios will be added here as the page matures. If you want to meet us before a demo, get in touch.

Come work with us, or come build on us.

Either direction is welcome. Open roles are on the careers page. If you are a GRC vendor, bank or product team evaluating a data layer, send a note and we will set up a 30-minute call with the right specialist.

Name(Required)