Roadmap · Product status
No guesswork. No roadmap dressed up as a feature.
Explore the controls behind SENTR, follow each capability into its workflow and see how to access it. Live features and future plans stay clearly separated.
Features
Select a feature to see how it works. Live means the capability is operational in the product. Status describes readiness and access — not a guarantee of results. Compare SENTR.Tower and SENTR.Citadel for configuration and reporting access.
| Feature | Status | What it means for you |
|---|---|---|
| Features Rules engine | Live | Start with global and industry rules. Author custom conditions, test against history and use Monitor to evaluate a rule without changing live scores. |
| Features Scoring engine | Live | Evaluate mapped events using rule contributions and a separate customer-specific anomaly score. Inspect the signals behind each result. |
| Features Scoring profiles | Live | Lenient/aggressive thresholds inside rules, scoped per event type. Distinct from decision policies that set review/block score cutoffs. |
| Features Decision and action policies | Live | Scoped review/block thresholds and downstream actions (case creation, notify, webhook). Appetite differs by market and event. |
| Features Lists management | Live | Allowlists, blocklists and custom lists with customer-set influence score — a match does not force a maximum score. |
| Features Reason codes | Live | Customer-defined tags for decisions and investigations, with scope and attribution. |
| Feature | Status | What it means for you |
|---|---|---|
| Live | Connect files, REST APIs, webhooks, databases or streams and map your fields to SENTR. Automated mapping for named providers is still in development. | |
| Features History backfill | Live | Import and replay historical activity so velocity, reuse and first-seen rules can interpret the next event in context. |
| Live | Connect web activity with persistent device fingerprints, interaction signals and browser-automation indicators. Native mobile SDKs are planned separately. |
| Feature | Status | What it means for you |
|---|---|---|
| Features Customer-specific anomaly detection | Live | Operational customer-specific unsupervised model. Trains overnight on clean history; validated feedback helps improve the next cycle. Rules and AI are separate score axes. |
| Live | Sector and global model tiers are available alongside customer-specific anomaly detection. Broader-data participation is governed per deployment; it is not an automatic consequence of using SENTR. | |
| Live | Score attribution is stored at decision time. Generative AI turns relevant findings into plain-language explanations; the language model does not make the risk decision. | |
| Features SENTR 360 journey reconstruction | Live | Full journey reconstruction is available with the JavaScript SDK. Device fingerprints and web signals remain available separately for API-only integrations. |
| Features Additional AI scoring | Live | AI scoring is available alongside the customer-specific anomaly foundation. Applicable configuration and score interactions are agreed for the deployment. |
| Live | The AI rule builder is available alongside custom-rule authoring, tests, backtesting and Monitor. Confirm the supported workflow and approval permissions during setup. | |
| Live | The ML pipeline and automatic feature engineering support model learning and the development of input features. Configuration, validation and deployment controls are agreed during technical discovery. |
| Feature | Status | What it means for you |
|---|---|---|
| Features Entity profiles | Live | Users, devices, sessions, IPs and payment methods with linked activity and risk posture. |
| Features Connection Ring | Live | Interactive linked-analysis graph on events — direct vs inferred relationships. |
| Features Queues, cases and human override | Live | Automatic, manual or external escalation into cases. Override requires a written reason with full attribution. |
| Feature | Status | What it means for you |
|---|---|---|
| Features Dashboards and reports | Live | Overview / investigations / rule analytics dashboards; 30+ standard reports; custom builder across six data sources; CSV/XLSX/PDF export. |
| Features Configuration and decision audit | Live | Decisions and configuration changes recorded with user and timestamp. Audit logs are a first-class report source. |
| Feature | Status | What it means for you |
|---|---|---|
| Features API keys, webhooks and delivery logs | Live | Scoped keys, webhook endpoints with signing secrets, inspectable delivery/retry/failure traces. |
| Features Developer sandbox | Live · on request | Request a separate environment and credentials to explore the integration before connecting production traffic. |
| Features API documentation | Live · on request | Request API documentation during a technical review to work through event payloads, authentication and responses with your engineer. |
| Feature | Status | What it means for you |
|---|---|---|
| Features SENTR.Tower guided operating model | Live · early access | The shared SENTR engine with guided presets and configuration. Your team reviews alerts and retains decision ownership; setup is assisted, not open self-service. |
| Features Shadow Mode evaluation | Qualified evaluation | Free, optional 50-day SENTR.Citadel evaluation alongside your current controls, without changing live decisions. Website report examples use synthetic data, not customer results. |
| Feature | Status | What it means for you |
|---|---|---|
| Features AML and sanctions screening | Not yet live | Planned, not available today. SENTR does not currently replace a dedicated AML or sanctions-screening service. |
| Not yet live | Planned, not available today. Current case records and decision evidence can support the dispute process your team already uses. | |
| Features iOS and Android SDKs | Not yet live | Not available. JavaScript SDK only today. |
| Not yet live | Planned agents would take on investigation and policy tasks with human oversight. Current automation follows configured decision and action policies. |
Some capabilities need an access conversation. Others are future plans, not current inclusions. No release date is committed here.
A separate environment lets your engineer work through mapped events, credentials and responses before connecting production traffic. Access is arranged with SENTR. A sandbox checks the integration; a qualified Shadow Mode evaluation compares decisions on your own traffic.
Plan a technical review →Work through authentication, event payloads and response handling with your engineer. Documentation access is arranged during technical review rather than through an open documentation portal. Bring a redacted event schema and the response your application needs to enforce.
Explore the integration workflow →Sector and global model tiers are available alongside customer-specific learning. Participation in broader-data learning is agreed per deployment with the required governance; it is not an automatic consequence of using SENTR.
Explore machine learning in SENTR →AI scoring is available alongside customer-specific anomaly detection and rule-based evaluation. Applicable score interactions and configuration are agreed for your deployment. AI explanation rendering remains a separate job: translating recorded findings into readable reasons.
Explore AI scoring →The AI rule builder is available alongside custom-rule authoring, tests, backtesting and Monitor. We confirm the supported workflow and approval permissions during setup; availability does not imply autonomous changes to live policy.
Explore the AI rule builder →Planned capabilities would extend SENTR beyond fraud operations. Dedicated AML and sanctions screening are not available today, so keep the services and processes you currently rely on. Configurable fraud rules and an audit trail do not substitute for those screening capabilities.
Review the current scope →Planned automation would handle steps in the financial dispute process. SENTR does not currently file or settle chargeback disputes. Today, investigators can assemble event evidence, record outcomes and export reports to support the process their team already runs.
Explore current casework →Native mobile SDKs are planned, not available today. The JavaScript SDK supplies web device and interaction signals. Server-side mobile business events can use the existing API integration; that does not provide native-device telemetry or a mobile SDK.
Explore available device and event inputs →The roadmap includes agents that could take on analyst tasks with human oversight. Those agents are not available today. Current automation follows configured policies for decisions, cases, notifications and webhooks; it is distinct from an agent independently investigating a case or changing policy.
Explore current workflow automation →Ask about a specific requirement, see the controls in context or compare the two operating models.