Everything you build on Ubex is encrypted in transit and at rest, checked at every endpoint and logged on every run. Here is exactly what is in place today, and what is still in progress.
Every request travels over TLS, and your data stays encrypted at rest once it arrives.
Endpoints can require an API key on every call. Keys you revoke stop getting in.
Allow only the IPs or CIDR ranges you choose. Calls from anywhere else are refused.
Set how many calls a minute an endpoint accepts. Calls above it are refused.
Choose which websites may call the endpoint from a browser. Every other site is turned away.
The workflow runs, and Activity records it with its status, timing, input and output.
Keys and passwords live in the Vault. Workflows use them by name, so their values never land in a log, an output or on a screen.
A sample run. Secret values never appear in logs or outputs, only their names.
Every secret is encrypted the moment you save it.
Nodes read secrets.STRIPE_KEY. Nobody pastes the value into a workflow.
The API returns secret names and hints, never their values.
People join your organization by invitation. Owners and admins share the day-to-day, and a few things only the owner can do.
Status, timing, input and output for every run, with each step in the execution log. Kept 7 to 30 days depending on your plan, longer on request.
How Activity works →We are working towards GDPR compliance and SOC 2 Type II. We will mark each one done when it is done, not before.
The EU's rules for personal data: what is collected, how it is kept and how it is deleted.
An independent audit of how our security controls work over time.
Send us your questionnaire or ask us anything. We answer with what Ubex does today, not what it might do one day.
Found a vulnerability? Tell us privately through the contact form.