The operating system for municipal waste
Waste is not only a collection problem. It is a coordination, evidence, money, and accountability problem. MetroCir is the digital infrastructure that connects them.
MetroCir is the platform. Each city concession runs on its own operator host. Dispatch that survives unmapped streets. A weighbridge ledger sealed by design. Remittance ordered in code.
Product preview. Simulated sample city — not a live concession.
Wards, crews and sequences — not a geocoder guessing unnamed streets.
GPS, in-cab proof and sealed weight tickets on one chain of record.
Council first, then vendors, then lenders. The order is a platform rule.
A councillor, a dispatcher and a DFI read the same period statement.
The city operating system
Collection. Evidence. Finance. Governance. Connected.
Four desks. One record. The city does not assemble the month from three vendors and a spreadsheet.
Wards, crews and the in-cab app on one sequence — dispatcher still in charge.
Weight tickets, scheduled-versus-served and civic close-outs share one ledger.
Monthly batch invoices and a settlement order that is not a contract annex.
SLA, remittance and audit pack from the same rows — not three spreadsheets.
Operating loop
Watch a tonne move through the system.
Plan, dispatch, collect, verify, weigh, settle, remit, audit. Click a node. The inspect panel is the product — not a diagram.
Plan
Wards and crew-drawn service points become the unit of work. Geometry is stored as PostGIS points — not street addresses that do not exist.
- 01Depot
- 02North 1
- 03North 4next
- 04Market kerb
- 05Landfill
From ward to weighbridge
The operational journey.
A truck is dispatched. GPS reports. The ward is served. Proof is captured. The scale writes the tonne.
From weighbridge to revenue
The financial journey.
Sealed weight becomes the first claim for the council, then vendor payout, then loan service. Operator retention is last — on purpose.
Illustrative shares. Invoicing is monthly batch — never per job. TZS carries zero decimals.
One record of truth
Dispatch, weight and settlement share the same rows.
Corrections are new entries. Nothing is silently edited. A DFI and a dispatcher can quote the same ticket.
Rows are never updated or deleted. Corrections are new entries referencing the original.
Sample city ledger preview. Illustrative tickets — not a signed month.
Built for African cities
Built because African cities operate differently.
Incomplete maps. Dropped connectivity. Cash crews. Concession fees owed to the council. Multiple operators. Fragmented evidence. Each city still gets its own host.
Wards and crew-drawn points. Not a geocoder.
In-cab cache. Sync when the network returns.
Monthly batch invoices. Field reconciliation.
Sandbox rails. Production cutover is not claimed.
First claim in code — not an ERP export.
One host, one tariff book, one ledger.
Dispatch, weight and money on one record.
Neighbouring cities cannot mix records.
Why incumbents miss this environment
Enterprise waste software was designed for cities with addresses, weighbridges and card payments.
AMCS and Routeware are the closest full-stack peers — and they assume a street network, a card rail, and a remittance that lives in finance.
The council's share is settled ahead of vendor payout and loan service on every run. The order is enforced by the platform, and every step leaves an entry someone can audit.
Collections are designed for how African city concessions actually pay: monthly batch invoices, field cash reconciliation, and mobile money rails in sandbox before we claim them in production.
Each city concession operates on its own host with its own data boundary, currency and tariff book. A neighbouring city cannot see, or accidentally reprice, your wards.
We do not claim production mobile money, wastewater as a product, issued carbon credits, or fully automatic AMCS-class VRP.
Who it is for
Three doors. One platform.
The municipality verifies. The operator runs the fleet. The DFI reads the same sealed tonnes.
Served versus scheduled, remittance that arrives first, and a record a councillor can quote.
- ▚Ward SLA the grantor can defend
- ▚Council share settled in code
- ▚Civic complaints closed on the same record
Assisted dispatch, in-cab proof, and payout that matches the sealed weight — not a submitted claim.
- ▚Assisted sequencing on incomplete maps
- ▚Driver app that survives dropped 4G
- ▚Payout per tonne from the same ledger
Auditable tonnes, an enforced settlement order, and a written list of what is still sandboxed.
- ▚Append-only weighbridge ledger
- ▚Council-first waterfall in code
- ▚Host isolation and PDPA residency
First city proof
Pilot · illustrativeDar es Salaam — the reference concession host.
MetroCir is not a Dar brand. Dar is the first live city host: its own operator console, tariff book and data boundary. Figures below are demo aggregates that show report shape — not a signed month.
Operator console preview with Dar geography. Simulated run board — labelled demo.
The reference concession: dispatch, sealed tonnes, monthly batch billing, and Swahili-first resident messaging.
City host provisioned and deliberately dormant until the first concession is signed off.
See it run
Seventy-five seconds of Smart Dispatch.
Bring your city. We will show you the console, the settlement order, and what is not yet claimed.
A briefing runs 45 minutes: concession model, evidence trail, host isolation, and an honest Now / Next / Later.