Compare
A region is not sovereignty. Running it yourself is.
Vendor-hosted platforms are simpler to operate and often ship excellent research content. They cannot answer the question of who can compel access to your data, and their sensors are theirs. Wahukeza runs on-prem, as a tenant we operate, or both, and we compare honestly, including the operational cost of hosting it yourself.
Side by side
Where the two models differ.
Written generically on purpose: the trade-offs hold across vendors. Named comparisons on request.
| Vendor-hosted SaaS | Wahukeza | |
|---|---|---|
| Where your data lives | The vendor’s cloud, in a region you choose. Subject to the vendor’s jurisdiction and any compelled-access regime it answers to. | Your choice. On-prem: your hardware, your database, your jurisdiction, no call-home. Hosted: a tenant with its own database on Wahukeza-operated instances, Trony Network as processor under the DPA. Or both. |
| Who sees your sensor telemetry | The vendor, by design: it is how their intelligence is produced. | You (and on a hosted tenant, us only as your processor). The exchange shares only what you choose, signed and scoped; the redistributable flag governs what leaves. |
| AI | The vendor’s models, on the vendor’s infrastructure. | Chosen at install: a local model, Anthropic with your own key, or off. Retrieval on Postgres. |
| Multi-tenancy | Usually available for providers, as a feature of the shared service. | Database per tenant under your own control plane. |
| Operations | None: the vendor runs it. The strongest argument for SaaS. | On-prem, you run it: Compose or Helm, a Postgres and a Redis, signed images, a migration runner. We do not pretend it is zero. Hosted, we do. |
| Continuity | Tied to the vendor’s roadmap and ownership; acquisitions in this category have redirected whole products. | A platform you host and a sensor you own keep working regardless of us; an expired licence degrades to the Community edition, never offline. Data exports in STIX 2.1, CSV and JSON. |
| Commercial | Typically by quote, often per seat. | Four packages, modules individually, unlimited analysts; quote after a scoping workshop. |
| Intelligence content | Often the main product: finished analysis on actors and campaigns from a large research team. | Not our product. We make the intelligence you own and generate operable; bring content feeds as connectors. |
Straight answers
Choose SaaS when…
You have no one to run it
A Postgres, a Redis and upgrades are real work. If nobody can own that, do not self-host: take a tenant on Wahukeza-operated instances, ask a partner to run it, or buy SaaS.
You are buying content, not a platform
Finished analysis on named actors is a different product. Buy it, and bring it in as a connector.
Jurisdiction is not a question for you
If no client, regulator or board will ask where the data is and who can reach it, the sovereignty argument does not apply.
Straight answers
Choose Wahukeza when…
Someone will ask where the data is
And “a region” will not satisfy them. Your hardware, your database, your answer.
The sensors should be yours
Telemetry from your own personas, endpoints and firewalls, and a ledger of what was new.
You need to outlive the vendor
Self-hosted keeps running through any acquisition, including ours.
You want to keep the exit
Start hosted, move on-prem, or run both. Export in STIX 2.1, CSV and JSON whenever you like.
Time the install yourself.
The strongest case for SaaS is operations. We answer it by installing on a clean host with you and stopping the clock at the first sensor event.