Every organization's data, apps, and credentials are isolated at the database level -- not just access-controlled in the UI.
Contact usEvery tenant's data lives in its own scoped rows, enforced at the database level, not just the UI.
API keys and connection secrets are encrypted at rest -- never stored in plain text.
Grant access per app, per team, or per person -- and revoke it just as precisely.
What tenant isolation means in practice
Isolation enforced at the database level means a bug in one tenant's app UI can't expose another tenant's data -- the boundary doesn't depend on every screen getting its access checks right. Connection secrets, API keys, and OAuth tokens are encrypted at rest with dedicated per-purpose keys, and all traffic is encrypted in transit.
If something goes wrong
Infrastructure and application errors are monitored continuously, and live status and uptime history are published at status.viibestack.ai. If an incident affects your data or availability, affected account admins are notified directly -- see our incident response page for the full detection-to-resolution process.
Who can see what
Platform staff access to a tenant's data is role-scoped and limited to what's needed to operate the platform or help with a support request -- not blanket access to every account by default. Within your own workspace, access is yours to grant and revoke per app, per team, or per person, down to a single user.
Where this fits your own review process
If your team runs a formal vendor security review, this page and the Trust Center cover the core architecture questions most reviews start with -- isolation, encryption, access control, incident response. For anything more specific to your process, contact us directly rather than guessing from what's published here.
Security questionnaire or specific compliance question? Reach out and we'll get you what you need.