This release is one thing in eight parts: the governance layer around your rules. Security, access control, audit, and release management all shipped together, because in practice they only work together. If your team has to pass a compliance review before it can put a decision engine in production, this is the release that gets you there. Here is the whole set, with a link to the full story on the three that have one.

Single Sign-On

Connect your own identity provider over OpenID Connect or SAML 2.0 and your members sign in with corporate credentials instead of a personal Google, Microsoft, or LinkedIn account. Before SSO can be enforced you verify domain ownership with a DNS TXT record; once the domain is verified, you can require SSO for it and social sign-in is refused for those addresses. SAML accepts multiple signing certificates at once, so certificate rotation costs you no downtime. Enterprise plan, configured by an org admin.

Custom Roles & Access Review

The built-in Read, Write, Run, Debug, and Admin roles now have company underneath them: define your own additive roles, up to 25 per organization. One of the new permissions is View PII values, which decides whether a person sees real subject data in a trace or a redacted placeholder - so an operator can see exactly which rules fired without ever seeing the customer behind them. And when the auditor asks who could touch what, the point-in-time Access Review answers it: every person, every environment, including access granted implicitly by org-admin status, exportable as CSV or JSON. Enterprise plan.

Deployment Pipelines & Releases

Snapshot an entire project into a numbered, immutable release, then promote it stage by stage across your environments through a pipeline an admin defines. Any stage can require approval, drawn from three approver sources: org admins, flagged project members, or named email addresses. Four-eyes enforcement means the person who requested a promotion cannot approve it. A dashboard shows drift across every project and stage at a glance, with approve and reject one click away. On Team plans and above, an org-wide release policy sets the floors - require approval, require tests, require an approval stage, require four eyes - and individual projects can only make those rules stricter, never looser.

Audit Log

Every change to rules, releases, access, and credentials in your organization, newest first, filterable by action, actor, resource, and date. Refused attempts are recorded too, which is usually the half an auditor cares about most. Enterprise organizations can export the log to CSV or JSON, or stream events in near-real-time to their own SIEM - Splunk, for instance - over HTTPS with a configurable auth header.

Access & Security Policy

Organization-wide controls, available from the Pro plan up: require multi-factor authentication, cap idle timeout and maximum session length, and cap how long an API key or MCP token may live before it has to expire. Enterprise adds an IP allowlist that restricts who can reach your control plane at all, with a safeguard built in so an admin can never write a rule that locks themselves out.

Organization API Keys

Machine credentials issued by an org admin for services and pipelines, separate from the project-scoped API Access keys you already use. Each key gets granular permissions - Read, Write, Run, Debug, Admin, View PII - and is scoped either to a single environment or to the whole organization. Expiration is optional but bounded by the organization’s credential-lifetime policy. The full key is displayed exactly once, at creation.

Disaster Recovery

Enterprise organizations get a nightly backup at 03:00 UTC of the entire organization: projects, conditions, action sets, rule sets, and tests, written to a storage container you own. You can also take a backup and download it on demand at any time. Restoring from a backup file includes a guard against silently overwriting a project that already exists.

Compliance Archive

A paid Enterprise add-on that writes a daily, write-once copy of your audit trail and release evidence to immutable storage you own, retained for seven years by default. It is deliberately not a backup. It is evidence you never restore from, held under your own storage immutability policy, so that months later you can show an auditor that a given period happened exactly as recorded.

How the pieces fit

None of these stand alone: the audit log records what SSO, roles, policy, and pipelines gate, and the compliance archive is what proves any of it later. Turn on the ones you need now, and the record of everything else is already being kept.

Visit RuleEngine.ai to try it.

The AI Rule Engine Team