About
Regulatory change, read at the source.
RegSignal is API-first regulatory intelligence. It watches official publishers in 21 jurisdictions, classifies what they publish, matches it to the products you describe and delivers the result where your team already works.
Mission
Make regulatory change something a team can detect, understand and act on, with the official source one click away.
Detect. Understand. Act.
What RegSignal is
- A continuously updated corpus of official regulatory publications
- Classified into one controlled vocabulary and matched against your product profiles
- Answered with citations and pushed into your systems through webhooks, connectors and an MCP server
- Delivered as a REST API, a console, TypeScript and Python SDKs
What it is not
- Legal advice: Ask answers are informational, so check the cited source before you act
- A news digest: the public corpus comes from official publishers, next to the internal documents you add
- A services engagement: coverage, vocabulary and delivery are there the day you get a key
Principles
What we hold ourselves to
Each of these is visible in the product, not only in this page.
Official sources only
The public corpus is built from official publishers, not from news coverage of them.
- Federal registers, agency pages, gazettes, recall databases and WTO notifications
- Each source registered with its publisher, adapter, cadence and verification status
- Every signal links back to the publisher’s own URL
Every answer cites its source
Ask is only as good as the evidence it can point to, so it always points.
- Citations resolve to a document, a URL and the exact passage
- An explicit insufficient-evidence response instead of a guess
- Answers are informational, not legal advice
Accuracy is published, not claimed
We measure the classifier and retriever on frozen datasets and publish the method and the weaknesses with the numbers.
- Ground truth derived from publisher metadata, not hand-tuned
- Each run records the commit, models and dataset hashes it used
- Known weaknesses listed next to the results
Explainable outputs
Nothing in RegSignal is an unexplained number.
- Every classification records model, provider and confidence
- Slugs are validated against the taxonomy, never free-form
- Impact matches carry a rationale and required actions
Tenant isolation by construction
One organization can never read another’s data, and the rule lives in one place.
- Every corpus query passes a single organization scoping function
- Internal documents stay private to the organization that submitted them
- Row Level Security on every database table, with public grants revoked
Say what is not done yet
Status over seals: when something is in progress, the page says so.
- Security controls labelled live, in progress or planned on the trust page
- SOC 2 reported as a programme in progress, with no badge
- Legal documents marked as drafts until counsel has reviewed them
Published accuracy
Evaluation run of 13 September 2026 on datasets built from the live corpus. The sets are small and will be re-measured as the corpus grows.
- document type accuracy
- 94.0%100 documents
- retrieval hit@3
- 96.7%60 questions
- answers cite the expected source
- 14 of 15end-to-end Ask
- calibration error (ECE)
- 0.061lower is better
How it works
From publication to action
One pipeline runs for every organization. Only the last two stages use your data, and only for your organization.
- Ingest
Collect from official publishers
Each source is configuration, not code, and is polled on its own cadence.
- 101 sources in the registry, 96 active, across 21 jurisdictions
- Federal Register API, RSS and Atom feeds, JSON APIs, HTML listings, WTO ePing and EUR-Lex
- Near-duplicates folded into one canonical signal, with a version history
- Classify
Turn text into one vocabulary
Every publication is summarised and classified with a confidence score.
- 7 verticals, 67 product categories, 19 topics and 9 document types
- Key points, effective dates and comment deadlines
- Substances (CAS, EC, E-number, INCI) extracted and resolved
- Match
Score it against your products
Every new signal is compared with each organization’s active product profiles.
- Heuristic pass first on markets, verticals, categories, topics and substances
- AI assessment for the strongest candidates only
- High, medium, low or none, with a rationale and required actions
- Deliver
Put it where the work happens
Matches and signals reach people and systems through the channel each one needs.
- Impact inbox, tasks, approvals and a deadline calendar
- Signed webhooks, Slack, Microsoft Teams and email digests
- Jira and ServiceNow tickets, SDKs, the REST API and an MCP server
Every stage leaves a trace: each source run records its status, each classification its model and confidence, and each webhook delivery its attempts and response.
Status
An early product, described honestly
RegSignal is in an invite-only soft launch. This is what that means today.
Where we are
Invite-only beta on regsignal.dev
- AccessInvite-only beta for design partners. Organizations can be created from allowlisted email domains or by invitation; everyone else can join the waitlist.
- CommitmentsBest-effort support in business hours, incident notice by email and a public status page. No SLA or uptime percentage yet.
- SecuritySOC 2 Type I is in progress, target Q1 2027. No audit report, ISO 27001 or penetration test report exists yet.
- LegalTerms, privacy policy, DPA and the beta program are published as drafts pending legal review.
- CorpusUnder a thousand public documents at the last evaluation. Accuracy will be re-measured, not extrapolated, as it grows.
Console (available in the beta)
Signals, impact inbox, product profiles, Ask, tasks and settings.
API and integrations (available in the beta)
API keys, signed webhooks, Slack and Teams, email digests, SDKs and the MCP server.
Public status page (available in the beta)
Live checks of the API, the database and regulator ingestion.
Self-serve sign-up (not yet)
Not during the beta: access is by invitation.
Paid plans (not yet)
Billing is built but not switched on for the soft launch.
SAML SSO onboarding (not yet)
Supported by the platform, not part of the soft launch.