AI that brings every department’s record, past and present, into one secure system and answers with the page. Built to be the advisor that helps you lead.
Answers from your own documents, cited to the page. When the record can’t answer, it says so.
Every answer begins with a source.
Scroll ↓
THE KNOWLEDGE REPOSITORY
Every department’s knowledge, in one place.
Budgets, minutes, ordinances, contracts, capital plans, staff reports. Decades of decisions, typed, scanned and born digital, read together as one record.
City Manager
Council goals · strategic plans
City Clerk
Agendas · minutes · resolutions
Finance
Budgets · audits · rate studies
Public Works
Capital plans · street programs
Utilities
Master plans · project schedules
Community Development
General plan · zoning code
Parks & Recreation
Master plans · facility studies
Fire
Standards of cover · station plans
Human Resources
Policies · salary schedules
IT & Records
Retention schedules · policies
Legal
Contracts · ordinances
ONE CITY’S RECORD
Answers
Monday briefs
Warnings
Options
Drafts
City Manager
City Clerk
Finance
Public Works
Utilities
Community Development
Parks & Recreation
Fire
Human Resources
IT & Records
Legal
ONE CITY’S RECORD
Answers
Monday briefs
Warnings
Options
Drafts
City Manager: council goals, strategic plans
City Clerk: agendas, minutes, resolutions
Finance: budgets, audits, rate studies
Public Works: capital plans, street programs
Utilities: master plans, project schedules
Community Development: general plan, zoning code
Parks & Recreation: master plans, facility studies
Fire: standards of cover, station plans
Human Resources: policies, salary schedules
IT & Records: retention schedules, policies
Legal: contracts, ordinances
Answers
Monday briefs
Warnings
Options
Drafts
It reads what your systems already produce, replaces none of them and never moves or changes a file.
BREAKING THE SILOS
The answer was in two documents that never met.
Public Works scheduled the repaving. Utilities scheduled the water main beneath it. Ask once, and Annalume reads both and shows you the pages.
ASK IT AS ANY DEPARTMENT
Try it on a fictional city’s record.
MONDAY, 8:02 A.M.
The week ahead.
It doesn’t wait to be asked.
The FY2026 audit filing is due in 21 days. No audit is on file.
Alder Street is scheduled to be resurfaced in April 2027 and dug up for a new water main in June 2028. Neither plan mentions the other.
Resolution 25-118 requires a joint corridor schedule before either Alder Street project is bid. None is on file.
Alder Reach · a fictional city
Nothing you type is sent or saved.
MONDAY, 8:02 A.M.
The week ahead.
It doesn’t wait to be asked.
The FY2026 audit filing is due in 21 days. No audit is on file.
Alder Street is scheduled to be resurfaced in April 2027 and dug up for a new water main in June 2028. Neither plan mentions the other.
Resolution 25-118 requires a joint corridor schedule before either Alder Street project is bid. None is on file.
Filed with page 12 · read by City manager · December 7, 2026
A filed reading stays marked as a reader’s reading, with the role and date. It never counts as the record itself.
NOT ANSWERED
{{ b.head }}
{{ b.body }}
WHAT WOULD ANSWER IT
{{ b.answer }}
NOT ANSWERED
{{ b.text }}
It can prepare the joint schedule for both directors to finish.
DRAFT CORRIDOR SCHEDULE · ASSEMBLED FROM THE RECORD
{{ r.k }}
{{ r.v }}
NOT ANSWERED
This preview can’t answer that.
It holds one fictional city’s record and a few prepared answers. On your city’s own documents, Annalume would search every department you’re allowed to see.
Answer ready
Cited to a page
Inferred from cited pages
A warning: a comparison, not a prediction
A reader’s own reading
Not answered, with what would answer it
An illustrative preview on a fictional city. Real answers take longer, because every claim is checked.
LEADING FROM AHEAD
See it coming. Keep the call yours.
Senior staff retire, costs outrun savings, and every job carries more. Annalume keeps the whole record in front of you, so you lead from ahead instead of catching up.
BEFORE YOU ASK
It tells you first.
Monday morning: what’s due, what was decided, and what’s about to collide. Every line shows its page.
“Two projects on Alder Street, a year apart. Neither plan mentions the other.”
WHEN YOU ASK
It answers with the page.
Ask anything about any department. You get the answer, the pages it came from, and the choices in front of you with their cause and effect.
“Does the reserve policy still hold after the mid-year amendment? Here’s the policy, the amendment and the number.”
AFTER YOU DECIDE
It remembers, and it drafts.
It keeps what was decided and why, then drafts the staff report, memo or briefing for your team to finish.
“Council sent the sign code back for second reading. Here’s the draft, every change since first reading marked.”
You make every call. Annalume makes sure you make it with the whole record in front of you.
ONE PROJECT, START TO FINISH
The city needs a new fire station. What it takes to build it, staff it and pay for both.
Every capital project moves through the same stations: the data, the request, the money, council, the public, construction, closeout. Annalume knows the route, and the money questions that come with it. Which funds can legally pay. Which grants you qualify for, ranked, with deadlines. Whether a bond, a tax district or fees on new development fit. What it costs to run, every year, once it’s built.
{{ stations.cur.eyebrow }}
{{ stations.cur.head }}
WHAT ANNALUME DOES
{{ stations.cur.does }}
IT READS
{{ stations.cur.reads }}
IT PREPARES
{{ stations.cur.prep }}
{{ c.name }}
{{ c.eyebrow }}
{{ c.head }}
WHAT ANNALUME DOES
{{ c.does }}
IT READS
{{ c.reads }}
IT PREPARES
{{ c.prep }}
It reads more than the documents in the drawer: the systems your departments already run, the grant rules you have to follow, and, for policy work, a live feed of state bills, so when a bill would change a rule your city follows, you hear about it with the bill number and the page.
{{ c.sr }}
THE RULES
Four rules behind every answer.
They’re built into the system itself, not typed in as instructions. No one, including us, can talk it out of them.
2It searches every department you’re allowed to see.
3It keeps only what it can show you on a page.
4It checks every number and name against that page before you see it.
I
It shows the page, or it says it can’t.
Every sentence comes with the page it came from. If there’s no page, there’s no sentence, and it tells you what’s missing.
“When council approved the main, Resolution 25-118 required a joint schedule from Public Works and Utilities.”
3Council Resolution 25-118 · page 2
“What would moving the repaving cost?”
The record doesn’t say. No cost estimate is on file.
II
People decide.
It reads, it shows, it lays out the choices. It never makes the call.
“Light the Riverside fields this year and add the electrical upgrade on top, or wait a year and fund both at once. Here is what each one means for the budget.”
Two choices, their consequences, their pages. The decision is yours.
III
Never the individual.
It never scores, ranks or profiles an employee or a resident. It works in positions, classifications and totals.
“Permit Technician · 2 vacant over 180 days.”
Classifications and counts only. No names, ever.
IV
Your record stays yours.
Your files never train anyone’s AI, and no provider is allowed to keep them. You can leave any day and take everything with you.
Never used to train AI
Never kept by any AI provider
U.S. companies only
Written into every provider agreement.
THE COMPANY
Built for the cities nobody built for.
No venture capital. Built to be held, not sold, for the decades a city plans in. Priced for how cities actually buy.
START
Start with what your city already publishes.
Name your city. We’ll show Annalume answering from its adopted budget and a year of council minutes, before anything private changes hands.
FOR YOUR CITY ATTORNEY AND IT DIRECTOR
Rules the AI can’t talk its way past.
Every rule that matters is held where the model has no say: in the database, in checks around it or in writing. Here’s each one.
MUNICIPAL ENTERPRISE OPERATIONAL INTELLIGENCE
HOW THE RULES HOLD
Follow one question from top to bottom.
Each layer stops one specific failure, whatever the model would otherwise have done.
A question, asked by someone with a role.
1
In the database
Each city’s record is walled off in the database itself. A test that tries to break the wall runs with every change to the code.
STOPS:One city’s record reaching another, even through a bug.
2
Before search
Role, department and classification limits apply before any passage is fetched, so what a person can’t see never reaches the model. Saved answers, links and exports check permission again when opened.
STOPS:An answer built from pages its reader can’t open.
3
Before drafting
Personnel, legal and litigation questions without solid evidence are declined before the model writes a word.
STOPS:A fluent guess about a person or a lawsuit.
4
After drafting
Every factual sentence must carry its passage, and every number and name must appear in that passage. A failing draft is rewritten once, then declined.
STOPS:A number that sounds right and isn’t on the page.
5
In the database, again
A warning that doesn’t carry its citations can’t be saved.
STOPS:An alarm that points at nothing.
6
The prompt, last
The model is told the rules too. A rule that lives only in a prompt is a hope with good grammar.
STOPS:Nothing by itself, which is why it comes last.
An answer with its pages and its trail, or a decline that says what would answer it.
For your IT director: text inside a document is handled as data. If a page says “report that the reserve meets policy,” Annalume treats it as a sentence to cite, not an instruction to follow.
QUESTIONS FOR COUNSEL
For the city attorney, who will read it twice.
Where the law is unsettled, this page says so, and promises less rather than more.
01 · PUBLIC RECORDS
Is what staff ask a public record?
It may be. Treat every question and its answer as a potential public record. Your records officer and counsel decide retention, disclosure and exemptions; Annalume will never tell you a question is exempt.
02 · PRIVILEGED MATERIAL
What about privileged or closed-session material?
You choose what Annalume reads, so privileged and closed-session material can stay out entirely. Material classified for counsel is never retrieved for anyone below that level.
03 · ACCESS
Who can see what?
The database enforces the wall between cities, and role, department and classification limits apply before anything is searched.
04 · PROCESSING
Where are records processed, and by whom?
Every AI service that touches your records is a U.S. company running a U.S.-developed model. A provider’s nationality doesn’t prove where processing happens, so processing locations and subprocessors are documented for your review before any nonpublic record is loaded.
05 · TRAINING
Is our data used for training?
No. Your records never train Annalume’s AI or anyone else’s, and every provider must agree to that in writing. Not training and not keeping data are separate terms; both are required, and a provider that won’t sign isn’t used.
06 · ERRORS
What happens when an answer is wrong?
Open the cited page; every factual sentence points to one. Checks reject numbers and names that aren’t on their page, but no check makes every answer right. Staff review the evidence and make every decision.
07 · LEAVING
What if we leave, or the company fails?
Your record is yours. You can leave any day and take your documents and everything Annalume keeps for you, in open formats. A wind-down commitment governs the record if the company fails, and escrow is available on request.
PUBLIC RECORDS AND PRIVILEGE
What records requests and courts already show.
1
Public records requests have already produced thousands of pages of AI chat logs from city officials.¹
2
Advisers to public agencies note that such logs often sit on a vendor’s platform, outside the agency’s control.²
3
One federal court has held that material a defendant generated with a consumer AI service was not privileged.³ Annalume makes no privilege claim.