Handeware Enterprise

For banks, insurers, and regulated operations

The evidence layer for modernizing regulated operations.

Your batch schedulers and BPM suites run the business, nobody fully understands them anymore, and the board wants agents. We make the toolchain that gets you from there to here with proof at every step: scan the estate, replay your own run history through the replacement before cutover, run it event-sourced, govern the agents. The engineer gets proof, the executive gets cover, the auditor gets the trail — the same artifact, three readers.

Scan your estate — free See a real proof bundle

No account, no signup, no network access. One command, runs offline on your own machine: pip install handeware-scanner

Deploys
In your VPC
Network I/O
None
Dependencies
CPython only
Start with
the free scanner

Read the evidence before you read the pitch

These are real artifacts produced by the shipping tools against a synthetic wire-processing estate — a 17-job AutoSys chain with an AND-join, three human gates, and twelve days of run history. Nothing here is a mock-up.

Scan — estate report

Every process inventoried, every task classified, agent-readiness scored 5–95, human choke points surfaced. Runs offline against BPMN, DMN, IBM BAW, Pega, Control-M, AutoSys JIL and cron exports.

View the scan report →
Proof — 12 days, PASS

The estate's real run history replayed through the Handeware Engine, day by day: same jobs, same dependency order, same failure containment, same human gates. PROOF PASS.

View the passing proof →
Proof — corrupted history, DIVERGED

One seeded lie — a job that "ran" downstream of a failure — and the verdict flips, naming the job. PROOF DIVERGED. A proof that cannot fail is worthless; ours can, and its ability to fail is itself under test.

View the diverging proof →

The product line

Scannerhandeware-scan
Agent-readiness assessment of the legacy estate. Point it at your workflow exports; get a self-contained report and a machine-readable estate file. Stdlib-only Python, zero egress, runs air-gapped — an engineer can run it in a bank sandbox today without asking anyone's permission.
Free. Forever. That is the point.
Provehandeware-prove
The replay-conformance proof. Estate export plus a run-history CSV in; per-day PASS or DIVERGED evidence bundle out — missing runs, phantom runs, status mismatches, containment breaks, and history that violates the modeled dependencies. Proof the replacement is safe before anything is cut over.
The paid product — priced per proof.
Enginehandeware-run
Durable hybrid workflow runtime: event-sourced, replayable, deterministic core with human approval gates, DMN decisions, and a typed agent slot that ships unbound. Every run emits an audit evidence bundle. Deploys as a container in your VPC — we host nothing.
Annual private offers via AWS Marketplace.
Roobeethe evidence substrate
The system of record underneath. An append-only, tamper-evident, causally ordered log of what agents did and under whose authority — verifiable offline, years later, by software that is not ours. Certificate Transparency, not blockchain. The format and verifier are open; the operations are what we sell.
Per governed agent · in development
Garrison
The agent control plane for a regulated business unit: identity, policy packs, budgets, runtime enforcement, and the same event-sourced evidence for every agent action. In development — built on the Engine's audit DNA.
Early access — talk to us.
One evidence model, end to end

A scan, a proof, a run, and an agent action all produce the same shape of artifact: self-contained, event-sourced, reproducible. Your audit trail is not a feature we added — it is the product.

How it deploys

  • In your boundary, not ours. Everything runs in your VPC, your sandbox, or your laptop. There is no Handeware cloud, no account to create, no data leaving your estate.
  • Zero egress by construction. The core makes no network calls of any kind. docker run --network none is the reference deployment and the full test suite passes under it.
  • A software bill of materials you can read at lunch. Zero third-party runtime dependencies — the SBOM is CPython plus our package. Your third-party-risk review is a code review, not a supply-chain investigation.
  • Hardened where it counts. Hostile-input parsing, identifiers-never-paths filesystem discipline, redacted evidence, append-only proof bundles. Details on the trust page.

Buying through AWS Marketplace

Handeware transacts through AWS Marketplace so procurement rides rails your organization already trusts: purchases land on your existing AWS bill, eligible purchases draw down your committed-spend agreement (EDP/PPA), and multi-year terms paper as private offers your finance team has seen before. Because our products deploy into your AWS account, they sit naturally on the right side of the commit-drawdown rules.

Container listings are in preparation in AWS Marketplace. Pilots and private offers are available now, directly.

The pilot: Batch Estate Assessment + Replay Proof

A bounded slice of your estate — up to 500 jobs — scanned, converted, and proven against a window of your real run history. Two weeks, fixed price. Deliverables: the estate report, the proof bundle, and a migration plan your risk team can read.

See the full pilot scope → · support@handeware.com

Go deeper

Position

Why provability, not capability, is the bottleneck on enterprise autonomy — and the three things that would prove us wrong.

The thesis →
Migration

Leaving Control-M, AutoSys, BAW or Pega: what to export, what a proof can tell you, and the sequence that survives a risk review.

Migration path →
Straight answers

Including what a replay proof cannot do, why the scanner is free, and what happens to your estate if we disappear.

Questions operators ask →
Engineering

How the machinery works, in public: replaying twelve days of a batch estate, and why we mutation-test the proof itself.

Engineering notes →