Answer before they file
Residents search everything you've already released, in plain language — and you get a report of the requests that never had to happen.
For city clerks, county counsel, and records officersFewer requests. Faster responses.
Fewer requests. Faster responses.
Transparency that keeps up.
Most requests ask for something that's already public. Brandeis answers those on the spot, straight from your archive. The rest arrive organized, assigned, and on your state's legal deadline — AI agents do the drafting; your staff make every call.
51
public-records laws built in — every state + DC
100%
of actions logged — people and AI alike
0
outside services needed to run it
City of Riverton · Public recordsAnswers from the public archive
Do you have building inspection reports for 400 Main Street?
Brandeis
Yes — already public, no request needed:
Inspection report · 400 Main StReleased June 2025 · PDF · with 2 more from 2024
I also need the police incident report from the June 2025 vehicle damage there.
Brandeis
Not published yet — I've drafted a request for you:
“Police incident report, June 2025 vehicle damage at 400 Main St.”Filed as PR-2026-00184 · response due Mar 14, per Cal. Gov. Code § 7922.535
Every answer cites the public archive; a named human decides what goes out.
Residents get answers in seconds — and so do their AI assistants. Staff get requests that arrive already organized.
Sunlight is said to be the best of disinfectants.
Louis D. Brandeis, 1913 — the namesake, and the job description. What's already public should answer itself in seconds. What isn't should leave only by a person's deliberate decision, with a permanent record of who decided. That's the whole product.
The problem
More requests. The same one person. Still by hand.
Three trends, one desk.
Staffing hasn't kept pace
Most offices are one person, wedged between other duties. Volume climbs. Headcount doesn't.
AI is driving the volume up
AI tools now write many of the requests — broader, faster, and around the clock.
Most of what's public was never published
The answer is usually already public — just nowhere a resident can find it. So a question becomes a case number.
How we help
Three jobs. One system. No new headcount.
Most records software does only the middle one.
Run every request on rails
Requests come in sorted and assigned, departments reply from a simple link — no logins — and the deadline comes straight from your state's law.
A record that stands up
A permanent log no one can edit. Redactions that can't be lifted off the page. Every release approved by a named person — and verifiable by anyone.
What actually changes
Not a portal with a chatbot.
The same law, a different day at the desk.
How it's always worked
With Brandeis
Every question becomes a case number and a wait.
Most questions get answered on the spot, from records already public.
Staff read every page for exemptions, by hand.
An AI agent flags what the law may let you withhold, citation attached — staff confirm each one.
Deadlines live in a spreadsheet and slip in a busy week.
Every deadline is computed from your state's law, and an agent checks every clock nightly.
“Sent” is the only record of what happened.
Every action is logged permanently, and every released document carries a digital fingerprint anyone can check.
The agent era
AI files requests now. Brandeis answers them.
More requests every year are written by AI assistants. Work with them instead of drowning in them.
Their AI can ask you directly
A resident's or reporter's AI agent can search your public records and file requests itself — and it only ever sees what's already public.
Every release can be proven real
Each released document carries a digital fingerprint, so anyone can confirm a copy is authentic — right in the browser.
You watch the request count fall
One report shows the questions answered before they became requests — and what to publish next.
For the technical: the live demo speaks MCP at /api/v1/riverton/mcp — point any AI agent at it. Developer docs →
Under the hood
A staff of AI agents
An agent at every stage of a request. Each one drafts; your staff decide.
51
statute profiles — every state + DC
Your state's deadline rules, built in.
0
external services required
AI, email, OCR, storage — all opt-in.
1
deployment, every agency
Own portal, seal, statute, data.
100%
of actions audit-logged
People and AI alike. No way to edit history.
The answer box
Answers residents from everything already released, linked straight to the documents.
Sees only public records. Nothing else.
Triage
Drafts scope, complexity, routing, and duplicate flags the moment a request lands.
A coordinator accepts, edits, or discards.
Document review
Suggests whether each record is public and flags exemption passages, citation included.
Staff accept, edit, or dismiss every suggestion.
Redaction assist
Proposes redactions line by line; approved ones are sealed into the document itself — never a removable overlay.
Every redaction human-confirmed, then checked for leaks.
Drafting
Clarifications, extensions, response letters, denials — with your statute's appeal language.
Sent only by a staff member, under their name.
The copilot & deadline watch
Answers questions about any request; a nightly sweep watches every clock.
Every consultation is itself an audit event.
The disclosure librarian
Watches what people keep asking for — requests, searches, near-misses — and points at what to publish next.
A person decides what gets published, record by record.
The appeal packet builder
Assembles counsel's dossier straight from the audit log — timeline, deadlines, exemptions, verification records.
Drafted for counsel's review. It never sends itself.
Every agent action is logged: which model, which prompt, what came of it. And with no AI configured at all, Brandeis still runs. How the guardrails work →
One platform. Every agency its own house.
Its own portal, seal, deadline rules, staff, and residents — fully separate from every other agency, with your state's law set up as configuration.
Its own address
Own path, seal, accent, and contact block. Residents never see another jurisdiction.
Its own clock
Business days, holidays, extensions — change states and the deadline math follows, automatically.
Its own data
Separation from other agencies enforced on every database query — and proven by automated tests.
What it costs
Your first 1,000 requests are free.
Everyone should have access to best-in-class transparency tools — whatever the size of the agency. After the first thousand, you pay for exactly three things:
Usage
The requests you run through the system. No seats, no modules.
Document storage
The records you keep, publish, and serve.
Hands-off help
Optional — our team takes on whatever desk work your agency would rather hand off.
Not a procurement
Bring us your worst backlog.
Create your records office in about a minute — the first 1,000 requests are on us.
Want a guided look first? The walkthrough is thirty minutes on the real product — your state's rules, no slides. Or see it live.