​
What exists

Org accounts

Workspaces with four roles, invite flow, and per-workspace strategies and watchlists.

Audit logs

Date-filterable action log per workspace, plus a compliance export.

API key management

Tiered keys, hashed at rest, shown once.

Multi-tenant deployment

White-label mode with isolation enforced at the data layer.

Pricing

Four tiers plus a one-time founding option.

Support tiers

What is actually promised, and by whom.

​
What does not exist

Stating this at the top rather than letting a buyer discover it in week three of an evaluation:

​
The deployment model shapes everything

There is no vendor-operated instance. You run it inside your own perimeter, which moves the trust question from “do I trust this vendor’s controls” to “do I trust this code, running on my infrastructure.”

Advantages for procurement

No vendor data pool to assess. No sub-processor chain. Data residency is wherever you deploy. Your existing certified controls apply.

What it costs you

You own hardening, patching, backups, availability, and access control. There is no vendor to page at 3am.
For many institutional buyers the first column is why this is evaluable at all despite the second column and the missing certifications.

​
Vendor-permanency

The honest DDQ answer: this is an early-stage project. “Will you exist in 12 months?” does not have a strong answer, and the self-hosted, open-source model is the mitigation — if the project stops, your deployment keeps running and the code remains readable and forkable. That is a real answer to vendor risk, and it is not the same as the answer a mature vendor gives.
Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.