Encryption in transit and at rest
Files are encrypted from the moment they're uploaded through every transformation step - the same standard whether you're on the free tier or a paid plan.
Supabind is in private beta, and we'd rather tell you plainly what's already in place versus what we're still building than hand you a generic security checklist. Here's both.
At a glance
Encryption
In transit & at rest
Access model
Private beta, invite-based
Audit history
On the roadmap
Files are encrypted from the moment they're uploaded through every transformation step - the same standard whether you're on the free tier or a paid plan.
Your files, connections, and workflows live inside your own account and are never mixed with another customer's data.
These are genuinely on the roadmap, not vaporware - just not live yet while Supabind is in private beta.
A full history of who touched what, and when, inside a workspace - planned as teams start sharing workspaces rather than working solo.
Choosing where your data is stored and processed is on the roadmap as Supabind expands beyond its current single-region setup.
Viewer/editor/admin-level controls for teams, built for the point where workspaces are shared across more than one person.
All data is encrypted both in transit and at rest, helping protect your files and information throughout the upload, transformation, and storage process.
Yes. Each workspace is isolated, ensuring your files, workflows, and connections remain separate from other customer accounts.
Individual workspaces are currently account-based. Granular role-based permissions, including viewer, editor, and administrator roles, are planned for future team collaboration.
Detailed audit logging is planned for a future release. It will provide visibility into user activity and changes made within shared workspaces.
Configurable data residency is on the product roadmap. This will allow organizations to choose where their data is stored and processed as regional deployment options become available.