Your data,kept safe andkept apart
Digize runs on Cloudflare, keeps each workspace's data in a database of its own, and never lets a site's code near another business's data.
Kept apart by design
The way Digize is built does most of the work, before any setting is touched.
A database per workspace
Each workspace's data lives in a database of its own. A query in one workspace can't reach another.
Site code kept apart
A site's code runs in an isolate of its own, and reaches your data only through Digize, which checks the site is yours.
Builds in fresh sandboxes
Every build runs in a new, isolated container that's thrown away when the build is done.
HTTPS everywhere
Every site and domain gets a certificate, issued and renewed for you, and the app and its API answer only over HTTPS.
Cards stay with Stripe
Stripe takes your customers' payments, so card numbers never pass through Digize.
Verified webhooks
Events from Stripe and Twilio are checked against their signatures before Digize acts on them.
Who can do what
Everyone in a workspace is an owner, an admin or a member, and each role carries its own permissions.
API keys go further: each has only the access you give it, module by module, to read or to write.
- Keys are stored hashed and shown only once
- Each key can expire after 30, 90 or 365 days
- Every key and IP address has a rate limit
Signing in, safely
Sign in with a password or a one-time code sent to your email, and every new address is verified before it's used.
Bot checks and limits on repeated attempts keep automated sign-ins out.
Found a security issue?
Tell us at security@digize.com, with the steps to reproduce it if you can.
Build on a safe foundation.
Start free, invite your team with the right roles, and keep every key to the job it does.