The market makes you choose. We refuse the choice.
Every product in this space asks you to give something up: the other verticals, everything past the control room, your freedom of positioning hardware, or the operational layer itself. WillowCreek is built on the position that none of those trade-offs is necessary, and that the platform should be able to prove it.
Four kinds of product, four ways to stop short
Look across the market and the same four shapes recur. Each is strong at one layer. Each asks you to accept its ceiling.
The single-vertical comms platform
Deep in one industry, usually healthcare, and stops at its border. Change vertical, or acquire a second business, and you start again with a different product.
The security-integration engine
Excellent at wiring alarms and systems into a staffed control room, and it ends there. The people on the floor, on handsets, in the wards are outside the picture.
The RTLS application suite
A broad application layer bound to one positioning vendor's engine. Consolidating onto it means consolidating onto that vendor's hardware. Lock-in by another door.
The positioning framework
A capable spatial and positioning layer with no operational layer above it: no duress runtime, no escalation, no closed loop between an alarm and a human response.
What refusing the choice actually requires
Each of these is an engineering position with something behind it, not a slide. Where a pillar rests on a mechanism, the mechanism is named.
1. Vendor-agnostic positioning
A real abstraction, not a compatibility list. Every technology attaches through an adapter and normalises to one canonical fix: identity, position, quality, freshness, provenance. Normalisation is proven across two independent vendor dialects in the lab, so consolidation doesn't recreate lock-in.
Inside the location engine →2. One core, every vertical
Terminology, object types, workflows and screens are configuration, not code. Healthcare, aged care and corrections are live verticals today; twelve more industry packs are fully specified as catalogues. No vertical is a fork.
All fifteen industries →3. Life-safety first: enforced, not asserted
Life-safety is never gated by licence, billing or administrative state, and the storage layer enforces it: a policy attempting to gate incident raising is refused by the database itself. A life-safety assurance suite gates every release. It has already refused a real one.
The safety runtime →4. Explainability everywhere
Honest state over plausible state. A source that cannot be read returns unavailable, never a plausible zero. Dashboards state their own limits. Outbound messages carry honest delivery states: accepted and arrived are different claims, and the platform never blurs them.
The operator surfaces →5. Your infrastructure, your data
On-premises on your own infrastructure is the primary offered shape. The uplink to our provider plane is outbound-only, with no inbound firewall rule into your site network. No payment instrument ever enters the platform.
Architecture & deployment →6. Commercial honesty
Adapters are never metered. The client price is identical through every channel route. Licence enforcement is soft and forgiving: leeway and grace, never a hard cut-off. Evaluation precedes billing.
The pricing model →The usual trade-off, and our answer to it
| The usual trade-off | WillowCreek's answer |
|---|---|
| One vertical, deeply served. Leave it and you start again with another product | One core, every vertical. Industry packs are configuration, not code. |
| Consolidation onto one positioning vendor's hardware | A real abstraction: every technology attaches through an adapter and normalises to one canonical fix. |
| Life-safety as a slogan on the datasheet | Life-safety as an enforced property: the database refuses a policy that would gate incident raising, and an assurance suite gates every release. |
| Alarm state that looks plausible whether or not it is true | Honest state: unavailable is never dressed up as zero, and accepted is never dressed up as arrived. |
| A cloud dependency sitting between an alarm and the response | Your infrastructure, outbound-only uplink. Cut the link and the site still raises, routes, escalates and records. |
| Integrations priced per adapter, per year | Adapters never metered. An adapter is work we do with you, not an item picked from a shelf. |
We can show you the working
We measure our own build the way we would want a safety system measured: independently checked, and corrected in whichever direction the evidence points. Our completion figure has been revised down twice, held once when we could have raised it, and revised up once. All four times because somebody actually checked. Ask to see the arithmetic.
The same discipline is visible inside the product: dashboards that state their own limits, a command palette whose footer reads "commands never commit, you confirm in the drawer", and metrics that return unavailable rather than a plausible zero.
Put the six pillars to the test
An hour, your floor plan, and any question you like, including the arithmetic.