Handeware Enterprise

Enterprise / Start

Five minutes, start to report

Run it before you talk to us.

No account, no signup, no sales call, no network access. The scanner is free and stays free. It reads workflow exports off your disk and writes a report next to them — nothing leaves the machine, which is why you can run it inside a locked-down environment without asking anyone's permission first.

The five minutes

  1. Install

    Python 3.13. Zero third-party dependencies — nothing else is pulled in.

    $ pip install handeware-scanner

  2. See it work on a synthetic bank

    Before you point it at anything of yours. Writes a full report for "Demo Bank" — a card-dispute process, a KYC review, a wire-exception repair, an end-of-day Control-M batch, an AutoSys payment-release chain, plus mailbox and file-share exhaust.

    $ handeware-scan --demo

    Open handeware-demo-report/report.html. That is exactly what a report looks like — or read one here first if you would rather look before installing.

  3. Point it at your own exports

    Formats are auto-detected. Irrelevant files are skipped silently. You do not normalize anything first.

    $ handeware-scan ./exports

    It reads BPMN 2.0 and DMN, IBM BAW .twx archives, Pega exports, Control-M DEFTABLE XML, AutoSys JIL, crontab, and case-system event logs. Point it at a directory and let it sort them out.

  4. Or run it in a container, network switched off

    The reference deployment. The full test suite passes under exactly this.

    $ docker run --rm --network none \ -v "$PWD/exports:/work" handeware/scanner .

  5. Read what it found

    Every process inventoried and scored 5–95 for agent-readiness; every task classified with a one-line rationale you can argue with; human choke points surfaced; and a gap analysis showing how many workflows your modeled estate does not contain at all.

    The report is a single self-contained HTML file with no external assets — it survives being emailed, and it is designed to be forwarded upward without us in the room.

What it will tell you at the end

The report closes by naming the deterministic tasks inside your batch chains — the ones a replay proof can verify — and the exact command that would prove them:

# estate export + a window of your real run history $ handeware-prove ./exports/wire_eod.jil \ --history ./exports/autorep_march.csv \ --out ./wire-eod-proof

That is the paid step, and it is the one that answers the question a migration actually dies on: would the replacement have made the same decisions at 2 a.m.? How the proof works →

Common first questions

  • Does it need production access? No. It reads exported definition files. It has no network I/O to reach a scheduler with even if you wanted it to.
  • Does anything get uploaded? No. There is no telemetry, no analytics, no licence check, and no socket opened. Local files in, local files out.
  • Is the free tier time-limited? No. No expiry, no seat count, no account. An assessment nobody can run is worth nothing.
  • What if it finds nothing? It exits with a clear message rather than an empty report. Send us what you tried to scan and we will tell you whether the format is supported today — the FAQ is candid about where coverage is thin.

When you want the proof, not just the picture

The pilot takes a bounded slice of your estate — up to 500 jobs — and replays a window of your real run history against it. Two weeks, fixed price, and the deliverables are artifacts rather than slides.

See the pilot scope → · support@handeware.com