These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Security review asks
- Bespoke deployment promised
- A second codebase
- The two drift apart
With SynaptaGrid
- Isolation by default
- Dedicated instance where required
- Dedicated database or cluster
- One product, one setting
The situation
One account requires demonstrable isolation from every other tenant, and the self-serve tier has to keep running on shared infrastructure. Answering each requirement with its own deployment ends in separate codebases that drift apart.
How it is approached
Tenants are isolated by default, with a dedicated instance for the accounts that require it. Isolation runs from a dedicated logical database up to a dedicated cluster. Plans run from trial through to negotiated enterprise terms on the same product.
What changes
Hosting becomes a per-customer setting rather than a fork. The security review is answered without committing engineering to a second deployment to maintain forever.