"It’s a threat to democracy," says Dev Iyer, Locunity’s CTO, on what happens when local government decisions go uncovered.
Locunity monitors over 200 local government commissions across the United States, city councils, planning boards, school committees, and turns what happens in those meetings into structured intelligence for the people who need it. The pipeline ingests meeting videos, runs transcription, matches findings against what each customer actually cares about, and delivers personalized briefings: 31,000 processing jobs a month, 4.5 terabytes of video and documents processed every week.
For a two-person team operating at that scale, the infrastructure just has to work.
From six-hour meetings to a same-day briefing
Locunity’s pipeline runs continuously. Every time a government body meets, it fetches the video, extracts the audio, runs transcription, and routes the output through a matching engine that personalizes the findings for each customer. Government meetings can run six hours. Video files can hit 10 to 15 gigabytes. The pipeline has to handle that without failing mid-job and starting over.
And the last stage is where the intelligence gets personal. Locunity’s matching engine reconciles what happens in a meeting against what each customer cares about: pending contracts, regulatory exposure, policy fights. "It’s like having a chief of staff that’s analyzing 50 jurisdictions and telling your company what you need to act on today," Dev says. The matching engine turns that reconciliation into a briefing, delivered by email and their native software interface, pushed automatically.
A silent failure, or a job running on stale code after a deployment, shows up not as an error in a dashboard but as wrong intelligence in a Fortune 50 company’s inbox, feeding decisions about government contracts. For Locunity, a background job has to do more than finish: it has to be right, every time.
