Enterprise / Company
Company
Small on purpose, and built so that it matters less than you would think.
You are evaluating whether to let a small vendor near a system that runs your business at two in the morning. That is the right question to ask, and it deserves a straight answer rather than a page of stock photography. The short version: the software is built so it does not depend on our continued existence.
The vendor-risk answer, in specifics
Most vendor-continuity assurances amount to headcount — the implication being that a larger company is a safer one. That reasoning does not survive contact with how software actually fails a customer. A two-hundred-person SaaS vendor that folds takes your data down with it, because your data lives on its infrastructure. What matters is not how many people we employ; it is what you are left holding if we stop answering email.
| If Handeware disappeared tomorrow | What happens |
|---|---|
| Your running workflows | Keep running. The Engine is a container in your account with no control plane to switch off, no licence server to call, and no network egress in its core. |
| Your evidence bundles | Still readable. Every proof and audit bundle is self-contained HTML and JSON that opens in any browser, with no Handeware software involved. |
| Your event logs | Still yours and still parseable. Plain JSON Lines, one event per line, documented — not a proprietary binary format. |
| Your estate data | Never left your boundary in the first place. There is nothing of yours on our side to recover, or to breach. |
| Your ability to keep working | Source escrow is available for anything beyond a pilot. Ask during procurement. |
That is a bounded downside rather than a guarantee, and we would rather state it that way. It is also more than most vendors of any size can honestly offer.
Why the smallness is load-bearing, not incidental
Several of the properties enterprise reviewers care about most are available because this is a small, deliberate codebase — they are not things a larger organization would have chosen:
- Zero third-party runtime dependencies. The software bill of materials is CPython plus our package. Your third-party risk review is a code review, not a supply-chain investigation. No organization with a hundred engineers ships a dependency list that short.
- No network I/O at all in the core.
--network noneis the reference deployment, not a hardening tip. That is only possible when nothing in the product needs to phone anywhere. - Artifacts over services. Every output is a file you keep. There is no dashboard to lose access to and no account to be locked out of.
- Reviewable in an afternoon. The whole thing is readable. That is a security property, and it disappears the moment a product grows a platform team.
What we have actually shipped
Judgement about a small vendor should rest on delivery, so here is the record rather than a mission statement. Handeware LLC builds and ships production software across two lines: the enterprise product line described on this site, and a portfolio of consumer applications built on the same principles — no accounts, no servers, nothing leaving the user's device.
| Product | State |
|---|---|
| Scanner — estate assessment | Shipped, containerized, free |
| Prove — replay-conformance proof | Shipped; mutation-tested falsifiability |
| Engine — event-sourced runtime | Shipped; audit bundle per run |
| Garrison — agent control plane | In development |
The published evidence bundles on this site were produced by those tools, not mocked up for the website. That is the standard we would like to be judged against: not what we say the software does, but what it emits when you run it.
How we work with you
- Assessment before commitment. The scanner is free and permanent, and the pilot is fixed-price and bounded. Nothing about the sequence requires trusting us before you have seen output.
- Through your existing procurement. AWS Marketplace, so purchases land on the AWS bill you already have and draw down committed spend. Direct contracting is available for pilots.
- Through your integrator, if you prefer. Systems integrators run our tooling under their own engagements. If you already have a modernization partner, that is often the cleanest route — point them at us.
- Honest coverage. We publish where our format support is thin rather than letting a demo imply otherwise. See the questions operators actually ask.
Contact
| Reason | Address |
|---|---|
| Product, pilots, procurement | support@handeware.com |
| Vulnerability disclosure | security@handeware.com · security.txt |
Handeware LLC. Software that runs in your boundary.
The fastest way to judge us is to run the thing
It is free, it works offline, and it needs no account. Five minutes gets you a report on your own estate — no conversation required.