What's changed

A platform-wide reliability and correctness pass. Most of this month's work was verifying that features behaved the way the product said they did — and fixing the places where they did not.

New

• Single sign-on (SAML 2.0) on Enterprise, against any identity provider — Google Workspace, Okta, Entra ID. A domain must be verified by your organization before it can be routed to a provider, so nobody can point your company's sign-ins at a provider they control. Enforcement is checked server-side on every request rather than in the browser, and enforcing it requires nominating a break-glass address that keeps password sign-in: if your identity provider fails, the people who can turn enforcement off must still be able to get in.
• SCIM 2.0 user provisioning — add and remove people from your directory without touching the dashboard. Removing someone revokes access but keeps their audit trail intact. A directory sync cannot change a Rylvo role, by design: a sync that could set roles could create administrators unattended.
• Two-factor authentication (TOTP) is live. Note two limits we would rather state than have you discover: there are no recovery codes, and exactly one authenticator can be enrolled per account — losing your device means asking an operator to remove the factor.
• Public status page at /status — per-surface state, 24-hour uptime and p95 latency, refreshed every five minutes. It names recent failures rather than hiding them.
• Public security overview at /security — architecture, data residency, encryption, retention and access control, with the gaps stated plainly.
• Agency workspaces now show what each client workspace spent this billing period.
• Uploads are validated by their contents, not the filename or declared type: an executable renamed to .txt is rejected.
• Per-loader timing in traces, so the slowest part of building a bot's context is attributable rather than a single number.

Fixed

• The knowledge-base vector store was reached over plaintext HTTP across the public internet, so its credential crossed an unencrypted connection on every request. Authentication always held, so no customer data was ever readable by a stranger — the exposure was the credential in transit. It now speaks TLS and the plaintext port is refused outright rather than merely unused.
• The sign-in page crashed for every visitor for roughly ninety minutes on 13 September after a change of ours. It was our defect, caught by us, and the automated check that would have prevented it is now part of the pre-release gate.
• Data export returned only part of an organization's data. It now covers every namespace, and reports any collection it could not read instead of omitting it silently.
• Audit-log export stopped at 500 rows without saying so. It now pages to the end of the selected range, and tells you when a range is too large.
• Organization deletion left some records behind when a background trigger recreated them mid-delete. The cascade now re-sweeps until nothing remains.
• Broadcast targeting could use a stale audience segment. Segments older than 15 minutes are now resolved live.
• Support requests reached storage but notified nobody. Both the contact form and in-product support now alert us immediately.
• Mission Control approvals in some workspaces could never expire.
• Automatically detected edge cases were written where the dashboard could not display them.
• The prompt optimizer could promote a new prompt version after evaluating it against synthetic samples. It now requires real traffic before promoting automatically.
• Knowledge-base retrieval now says when it returns nothing, instead of appearing to succeed.
• Several plan-gate and empty-state messages that described the wrong thing, and accessibility labels missing from icon-only controls.

Changed

• Pricing no longer lists SSO/SAML and multi-region as available. Both are roadmap items; the pricing page and security overview now say so.
• Deleting an organization from the admin console now requires a recent sign-in, matching the other irreversible actions.
• Our subprocessor list now includes Upstash, which processes IP addresses for rate limiting.

This changelog starts with September 2026. Earlier changes were not published; the release history before this point lives in the repository.