Choose the operating model
Discuss customer-hosted, dedicated and shared-tenancy deployment.
WHY IT MATTERS
A security conversation grounded in specifics.
Scope access
Review tenant separation, roles and credential responsibilities.
See the evidence position
Distinguish documented controls from independent assurance.
THE OPERATING MODEL
What happens, and in what order.
Map
Identify data, access and operating responsibilities.
Select
Agree the appropriate deployment model.
Review
Examine controls and the evidence available.
Approve
Complete the institution’s security and procurement process.
MAKE THE EVALUATION CONCRETE
Ask to see it.
Use these demonstrations to test the fit with your institution. Capability descriptions are a starting point, not independent assurance.
- Document data flows and permitted external services.
- Review credential ownership, rotation and egress.
- Establish any mandatory independent-assurance requirements early.
QUESTIONS, ANSWERED
The questions that matter.
Bring the next question to a focused product and architecture conversation.
Is customer-hosted deployment described?
Yes. The inventory describes customer-estate, dedicated-instance and shared-tenancy options, determined during technical discovery.
Is Stretus SOC 2 or ISO 27001 certified?
The current disclosures state that neither is held. No future certification date is promised here.
Does a deployment diagram prove data residency?
No. Data flows, support access, external providers and contractual responsibilities must be reviewed for the specific deployment.
CONNECTED CAPABILITIES
Continue the evaluation.
START WITH YOUR REQUIREMENTS
Bring your operating model.
Let’s map the fit.
Discuss the client journey, enabled scope and institutional controls that matter to your team.