BeryX · Roadmap
What comes next, with no promised dates.
Three horizons — in progress, next and exploring — with a reference for every item, so your evaluation can cite it as planned. When an item closes a partial line in our RFP answers, the two pages link to each other.
No dates: approving and ordering is the product owner's decision; what already exists is in the changelog.
01
In progress
Being built right now.
- Ref. #265
Expression and conditional rules across columns
Cross-column consistency — for example, the end date after the start date — in a safe rule language, evaluated with read-only SQL.
- Ref. #249
Automated dedicated instances, in the region you choose
Provisioning and updating one single-tenant instance per customer automatically — its own GCP project, secrets, domain and fleet-wide updates — with the region the customer chooses reflected in the subprocessor list.
02
Next
Approved and ordered: it starts when what is ahead of it finishes.
- Ref. #226
Public status page and security incident runbook
A public status page (operational, degraded, incident), the security incident runbook — from containment to communication within the legal deadlines — and a documented tabletop exercise.
- Ref. #254
Continuous audit streaming to your SIEM
The audit log, which today you can query and export as CSV, streamed to Splunk, Microsoft Sentinel or Google Chronicle, as CEF or JSON.
- Ref. #193
The BeryX assistant in Slack
Talk to the assistant inside Slack, through an app installed with consent and a choice per channel. Alerts, the digest and scheduled reports already reach Slack by webhook.
03
Exploring
Scope not settled yet: it may change or leave the roadmap.
- Ref. #242
SCIM 2.0 provisioning of users and groups
From Entra ID and Okta.
- Ref. #194
The BeryX assistant in Microsoft Teams
The same assistant as the Slack app, in a Teams bot. Alerts and scheduled reports already reach Teams by webhook.
- Ref. #258
Response SLA tracking and account health report
Help requests in a support team queue, with the time to first response measured per severity, and a monthly account health report — usage, incidents, failed scans and SLA met — for the customer and the account manager. Enterprise terms are already set in each customer's contract.
- Ref. #255
ServiceNow integration
Incidents and tickets synchronized both ways.
How we keep this page honest: it is generated from a single file, and the site does not build if an item carries a date, if an item marked as delivered is not in the changelog, or if a delivered item stays here for more than 30 days.
Need something that is not here?
Tell us what your evaluation requires: we answer with what exists, what is planned and what we will not do.