For city clerks, county counsel, and records officers

Fewer requests. Faster responses.
Transparency that keeps up.

Most requests ask for something that's already public. Brandeis answers those on the spot. The rest arrive sorted, assigned, and on your state's legal deadline — AI does the drafting, your staff make every call.

51
public-records laws built in
100%
of actions logged, people and AI alike
0
outside services needed

Residents get answers in seconds. Staff get requests that arrive 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. What isn't should leave only by a person's decision, on the record. 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.

01Answer

Answer before they file

Residents search everything you've already released, in plain language — and you see the requests that never had to happen.

02Fulfill

Run every request on rails

Requests arrive sorted and assigned, departments reply from a link with no login, and the deadline comes from your state's law.

03Defend

A record that stands up

A permanent log no one can edit, redactions that can't be lifted off the page, and every release approved by a named person.

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.
AI 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 comes from your state's law, and every clock is checked nightly.
“Sent” is the only record of what happened.
Every action is logged permanently, and anyone can check that a released file is genuine.
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 can search your public records and file for them — and it only ever sees what's already public.

Every release can be proven real

Anyone can confirm a released file is the real one, right in their browser.

You watch the request count fall

One report shows what got answered before it became a request — and what to publish next.

For the technical: every portal speaks MCP, so you can point an AI agent straight at it. Developer docs →

Under the hood

A staff of AI agents

One at every stage of a request. Each drafts; your staff decide.

51
public-records laws built in
Every state and D.C.
0
outside services needed
AI, email, OCR, storage — all optional.
1
platform, every agency
Its own portal, seal, rules, data.
100%
of actions logged
People and AI alike. History can't be edited.
Before a request exists

The answer box

Answers residents from what you've already released, linked to the documents.

Sees only public records. Nothing else.

At intake

Triage

Sorts, scopes, and routes each request the moment it lands.

A coordinator accepts, edits, or discards.

As records arrive

Document review

Suggests whether each record is public and flags what the law may let you withhold.

Staff accept, edit, or dismiss every suggestion.

In the redaction studio

Redaction assist

Proposes redactions line by line; approved ones are sealed into the page for good.

Every redaction confirmed by a person, then checked for leaks.

In correspondence

Drafting

Clarifications, extensions, response letters, denials — with your state's appeal language.

Sent only by a staff member, under their name.

Alongside your team

The copilot & deadline watch

Answers questions about any request, and watches every clock nightly.

Every question it answers is logged too.

After the release

What to publish next

Watches what people keep asking for and points at the records worth posting.

A person decides what gets published, record by record.

If a denial is appealed

Appeal packets

Assembles counsel's file from the log — timeline, deadlines, exemptions, proof of release.

Drafted for counsel. It never sends itself.

Every agent action is logged, and with no AI switched on 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 — kept fully separate from every other agency.

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 dates follow.

Its own data

No other agency can reach your records — enforced by the software, not by policy.

What it costs

Your first 1,000 requests are free.

Every office deserves the good version, whatever its size. 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 you'd rather hand off.

What it costs, in full →

Not a procurement

Bring us your worst backlog.

We open your records office with you — and the first 1,000 requests are on us.

Thirty minutes on the real product — your state's rules, your backlog, no slides. The about page has the thinking behind it.