Auto Secure LoginPlatform
Controlled pilot B2G 57 tests · zero deps

Run a small-town utility on one platform — not five vendors.

ASL Municipal Utilities is all-in-one billing and operations for rural and small water, sewer, and trash utilities. One login covers customers, service locations, meters and readings, rate plans, billing runs, invoices, payments, and delinquency — plus the field side: work orders, routes, fleet and fuel, a time clock, and live crew tracking. A second face serves the public: a town site, resident portal, clerk and dispatcher workspaces, and a council/mayor portal. One login for the whole operation means the clerk's day goes to residents and crews, not to reconciling five vendors' spreadsheets.

1login for the whole town office
integer centsmoney math, no floats
8roles, least-privilege
57tests pass · zero runtime deps

The problem

A small town shouldn't need five subscriptions to send a water bill.

Rural utilities run on a patchwork — one vendor for billing, another for payments, a spreadsheet for meters, paper for work orders, and a separate site for the council. Nothing reconciles, every integration is a seam, and the clerk holds it all together by hand.

Municipal Utilities is one deterministic system for the whole operation, with forced tenant isolation, a tamper-evident audit, and money math that uses integer cents so a bill always adds up.

Every integration fails closed

  • QuickBooks OAuth, Stripe Checkout (HMAC-verified)
  • Twilio SMS opt-in; Drive / PDF / DOCX / CSV export
  • Payroll math is honest — FICA correct, refuses to be filing-grade
  • Every optional integration refuses to fabricate

Capabilities

Front office, field crew, and council — in one place.

🧮

Deterministic billing engine

Tiered pricing, proration, and integer-cent math — no floating-point drift, so bills reconcile exactly.

Meter lifecycle

Readings with anomaly flags across the meter's life, catching a bad read before it becomes a bad bill.

Billing runs

Draft → approve → post, so a whole cycle is reviewed before a single invoice goes out.

🚚

Work orders & routes

Field work orders with route optimization for the crew's day.

📍

Live crew dispatch

A time clock plus on-duty-only live GPS dispatch on a self-hosted Leaflet/OSM map — location only while on the clock.

🏛

Council portal

Meeting notes, a blog, and resident lookup for council members and the mayor.

👤

Resident self-service

Residents view and pay their own bills through a public portal.

💳

Integrations that fail closed

QuickBooks OAuth, Stripe hosted Checkout (HMAC-verified), Twilio SMS opt-in, and Drive/PDF/DOCX/CSV payroll export.

📱

Native apps + PWA

Native Android (Java) and iOS (SwiftUI) via the system browser, plus an offline PWA.

0 runtime depsone Node service, node built-ins only
forced RLSPostgreSQL 16 row-level tenant isolation
hash-chainedappend-only tamper-evident audit
Keycloak PKCE+ Google broker, hardened mobile handoff
Honest about the pilot. This is a controlled pilot (Sugar City, Colorado), not yet live resident billing. Defense-in-depth is real — forced row-level isolation, a tamper-evident audit, integer-cent money math, idempotency keys, opaque session tokens, per-mutation CSRF, fresh-auth gates, and immutable releases with daily verified backups.

One platform for the whole town office.

Billing, meters, payments, crews, and the council — deterministic, isolated, and auditable, without stitching together five vendors.