Self-host
Our cloud, or your servers.
Self-hosting by license, on request. Everything below is what the software does today.
- How you get it
- By license, on request. The container images are private: we send access to them with the license. The install guide is public.
- Runs
- One image: the API and the workers, on one server or split across several (all, api or worker).
- Needs
- Postgres 15 or newer and Redis 6.2 or newer, built in or your own. S3-compatible storage and a mail sender are optional.
- Calls home
- Nothing. No telemetry and no update check. The license is checked offline. When it ends and its grace days run out, the installation pauses until a new one is loaded. Nothing is deleted.
- Licenses
- Both on request. Free: 1 organization, 1 workspace and 3 people, with no end date. Enterprise: the limits we agree, with SSO, SCIM and Embed.
- Sign-in
- With mail, an email link or code. Without mail, email and password. TOTP two-factor either way. A deployment will not start with sign-in switched off.
- Encryption
- Credentials and keys are sealed per organization. Run history is not.
- Deploys
- Workers finish their runs before they stop. In our own test, 202 of 202 webhook calls were answered through a rolling deploy.
- Not yet
- Passkeys.