Built to contain mistakes.
Plain-language answers about how Tririse separates data, controls access and supervises automation.
Six commitments in the design.
Tenant isolation
Each organization owns its data. Automated tests probe cross-organization access across the product, including the portal and storage.
Roles & provisioning
A system administrator provisions organizations and the first admin. Staff are added by administrators. There is no public sign-up, and access requests never create a login.
Credentials & integrations
Connections use OAuth. Stored provider credentials are protected and never shown back in full.
AI under supervision
Prompts, outputs and decisions are retained. AI features fail closed when a provider is unavailable, and humans approve what is used.
Sending safeguards
Live campaign sending is off by default. Suppression and unsubscribe are respected, and sender domains are verified.
Hardening & audit
Request limits, bounded inputs, security audits and an audit trail are part of the build, with results documented.
Nothing crosses between organizations.
Every record is scoped to an organization, and the portal is authorized separately from the staff workspace, so a client sees only what you share.
What we haven't claimed.
Tririse is a private preview. We don't advertise certifications, uptime figures or customer counts we can't back up. Billing is not connected, and live sending requires an explicit owner decision.
Have a security question?
Request access and tell us what you need to know. We'll answer plainly.