Security

Reminix runs code your team wrote, with your API keys. Here is how it keeps both safe. If your security team has a questionnaire, send it to security@reminix.com.

Where your code runs

Each run gets a fresh, isolated machine, and Reminix removes it when the run ends. Nothing carries over from one run to the next. A run sees only its code and its inputs. It can't reach other scripts, your workspace's data or Reminix itself.

A run has no network access unless its version lists the hosts it may call. Even then, it reaches only those hosts, and only over HTTPS. Every request goes into the run's log. Each run has a time limit, and you can cancel a long one. How Reminix works has the details.

Secrets

Reminix encrypts API keys at rest with AES-256-GCM, using a key for each workspace. Once you save a key, the app, the API, the CLI and agents never show its value again.

Each secret lists the hosts it may go to. Reminix adds it to a request only when the request goes to one of them, so the code doesn't hold the key. A script can read a secret only if its owner turns that on. If a run prints a secret it had access to, Reminix shows [secret] in its place, in both the output and the log.

Who can do what

What Reminix stores

Reminix stores your account and workspace details, and each script's code, versions and settings. It also stores every run: its inputs, output, log and files, and who started it from where. Run logs and files last for your plan's period, which is 7, 30 or 90 days. Each run's record stays for as long as the workspace exists.

Where it's stored

Code runs on Cloudflare's network. Reminix keeps script code, run logs and files in object storage (Cloudflare R2). Accounts, settings and run records live in a managed PostgreSQL database (Neon) in a single region. The provider's point-in-time recovery lets us restore it to any moment in the last 7 days. We encrypt all traffic in transit (TLS 1.2 or later, with HSTS), and all data at rest.

Signing in

People sign in with an email and password, and we check each password against known breaches. Anyone can turn on two-factor authentication. We store only hashes of passwords, API keys and personal access tokens. You see a key or token only once, when you create it. Each one carries scopes. Only authorized staff can access customer data, and we log every access.

Webhooks

Each webhook endpoint has its own signing secret, shown once when you add it. We sign every delivery with it. Our SDKs check each signature, so your endpoint can turn away a forged delivery. They also refuse any delivery more than five minutes old, which stops replays. Verifying deliveries.

Audit log

Reminix keeps an append-only audit log that workspace owners and admins can read. It records membership changes, script access and approval settings, approvals and publishes. It also records secrets saved or deleted (never their values), and API keys and access tokens created or revoked.

Sub-processors

Compliance

We haven't completed a third-party audit (such as SOC 2) yet. We can sign a data processing agreement on request. Ask us about our plans.

Reporting a vulnerability

Please report security issues privately to security@reminix.com. The address is also in /.well-known/security.txt. Tell us what you found, where, and how to reproduce it. We reply within two business days, and ask for reasonable time to fix an issue before anyone makes it public.