Skip to main content

Case study · Government

Province-wide oversight of public universities, with an on-premise LLM.

A governor's office had no single view of public higher education, so questions that needed an answer in minutes took days of phone calls. We built the command platform, and kept every byte, including the AI assistant, on government infrastructure.

Client
Provincial governor's office(anon.)
Industry
Government
Duration
Phased
Team
Senior pod, FORGE + CORTEX

The challenge

What stood in the way.

University operations, student and faculty grievances, participation in institutional decisions and emergency response each sat in a different place. There was no live view across institutions, no lifecycle for a grievance, and no way to run a verified vote or push a crisis alert to the right people by severity.

Our approach

How we framed it.

The constraint that shaped the design was sovereignty: government data could not leave government infrastructure. The assistant therefore runs on an Ollama-hosted model inside the estate, with an offline fallback, and the whole platform deploys as Docker Compose behind an Nginx reverse proxy so the office's own team can run it.

The solution

What we built.

  • Live KPIs across universities, students and teachers
  • End-to-end grievance lifecycle with prioritisation, SLA tracking and escalation
  • Verified anonymous voting on budgets, policy and elections
  • Severity-routed crisis alerts
  • 24/7 assistant on a locally hosted model, bilingual English and Urdu
  • React 18 / TypeScript / Vite front end; Node.js and Express API on PostgreSQL with Drizzle ORM and Redis

Results

What changed.

One command centre for the province's public universities, bilingual, with grievances tracked against SLAs and an AI assistant that answers without sending a single record outside government infrastructure.

Stack

Tools used in production.

  • React 18
  • TypeScript
  • Vite
  • Tailwind
  • shadcn/ui
  • Recharts
  • Node.js
  • Express
  • PostgreSQL
  • Drizzle ORM
  • Redis
  • Ollama
  • Docker Compose
  • Nginx

Practices

Practices on the engagement.

Talk to us

Have a similar problem? Bring it to a senior engineer.

A senior engineer plus the relevant department lead joins the first call. No discovery gauntlet, no junior reps.