OpenRecover

Same data. Different outcome.

Whose record
is it?

Crews cut the tickets. Monitors took the photos. Residents watched the trucks roll past the curb. The record of all of it lives behind someone else's login, in someone else's format, on someone else's schedule.

Nothing here is for sale. The tools go out free when they go out.

OpenRecover

Release ticket 0001

  • Open ADMS$0.00
  • Companion dispatch, web and mobile$0.00
  • ArcGIS Pro drop-ins$0.00
  • Cloud integration$0.00
Total due $0.00

No license. No seat count. No support contract.

Status: coming soon.

Signature not required. The release date lands in your inbox if you ask for it.

One question for your operation

Where is your debris data sitting right now, and what would it take to hold a complete copy of it before lunch?

Most answers land somewhere between a support request and a hard drive that arrives months after closeout. Photos in one system. Load tickets in another. Truck certifications in a binder that went home with a field supervisor at demobilization.

Nobody set out to build it this way. An event gets declared, something is needed by Monday, and a system gets assembled at speed by people whose actual expertise is debris operations. The version that carries you through the mission becomes the version you live with for seven years, including the years when a reviewer is asking questions about it.

How it usually works

  • Records split across separate systems
  • Access runs through someone else
  • Ownership goes undefined until closeout
  • Simple questions take weeks
  • Knowledge walks off at demobilization

What it could look like

  • One record, held by the jurisdiction
  • Direct access with no request needed
  • Ownership written in from day one
  • Answers inside an afternoon
  • The next event starts from a baseline

What is coming

OpenRecover builds AI and data tools for debris monitoring. The core set releases at no cost, published in the open, maintained by the people who use it in the field. Release dates go out to the list first.

  • Open ADMS

    Free, coming soon

    An automated debris management system anyone in the industry can run, read, and improve. Ticket capture, load calls, truck certifications, site management, and the reporting fields a PAPPG review actually asks for.

    Free for cities, counties, haulers, monitors, and anyone willing to help maintain it.

  • Companion dispatch

    Free, coming soon

    A web app for the back office with Android and iOS apps for the field, all on one shared record. Crews, monitors, and the client see the same assignment, the same photo, the same timestamp, without a phone tree in the middle.

    Open template you can brand, extend, or hand to your own developer.

  • ArcGIS Pro drop-ins

    Free, coming soon

    Project templates, field schemas, symbology, and portal layouts you can drop into ArcGIS Pro and have a working recovery map the same afternoon. No custom build. No consultant hours spent making a dashboard exist.

    Pass or fail geography, pre-clearance imagery, site throughput, and daily progress out of the box.

  • Your existing cloud

    Free, coming soon

    Keeping the system you already have is a valid answer. These tools connect to Azure, AWS, Google Cloud, CloudFront, or the database a monitoring firm already runs for your project.

    Nothing has to be replaced for your own record to become readable.

  • Applied AI

    In build

    Assistance aimed at the parts of debris work that eat hours: photo review at volume, duplicate and outlier ticket detection, load call variance, and drafting the documentation narrative a reviewer will read years from now.

    Built against real field records, tested against real audit questions.

Why give it away

Field expertise is the scarce thing in this industry. Software is not.

Every firm in debris work ended up building software. Not because anyone wanted to be a software company, because an event started and something was needed by Monday. Those tools got built fast, under pressure, by talented operations people working outside their discipline. The result carries the mission and leaves behind a record nobody can read afterward.

Handing the tools over at no cost takes that burden off the table. The firms that are genuinely good at debris operations get to go back to being good at debris operations. Jurisdictions get a record they can hold. Nobody has to defend a system they never wanted to build in the first place.

Free means free. No trial, no tier, no seat count.

Nothing here asks you to rip anything out

Change costs money and political capital in the middle of an event. If your firm, your hauler, and your county are comfortable with the setup you have, the goal is a readable copy of your own data inside it, not a migration.

  • Microsoft Azure
  • Amazon Web Services
  • Google Cloud
  • CloudFront
  • Existing monitoring databases

Who tends to use this first

Cities and counties

You carry the obligation long after the last truck leaves. Holding a complete, readable record is the difference between answering a reviewer in an afternoon and rebuilding a paper trail from memory.

Haulers and subcontractors

Invoices get held for reasons nobody explains in writing. Matching what your drivers actually did to what the prime's system says they did is the fastest path to getting paid on the first submission.

Monitoring firms and field staff

Your people rebuild the same spreadsheets on every event because the last one went home with someone who moved on. Shared, open tooling means a new project starts from a working baseline.

Correcting the record

30 seconds

Proving the correction

60 minutes

The gap is the whole problem

Fixing a wrong entry is trivial. Assembling the photos, the timestamps, the certification, and the site log that prove the fix was justified is where the hours go, on every event, on every project, for as long as the record lives in a place you cannot reach.

Also available on a shirt. Setup on the front, payoff on the back.

Get the release, or bring a problem

Ask to be told when the tools drop and that is the only message you will get. Bring the messy version of anything else: an active declaration, a closeout nobody wants to open, a contract about to go out for bid, or a repository you would like to actually read.

7+ years across 32 projects in 4 states through 8 major declaration events. California, New Mexico, Texas, Mississippi, Alabama, Florida, Georgia, the Carolinas, and Virginia.

No list rental, no drip sequence. Replies come from a person.