Spiro 2.31 — Release Overview

New filtering and segmentation paradigm

We've moved from a static list of parameters to a dynamic condition-building model across segments, API roles, and reports. Previously, configurations were built around a full array of properties — static, dynamic, and user relations — from which users had to select the ones they needed.

In the new version, the logic has changed:

Selective configuration: users now define and add only the attributes required for a specific query or report.

Streamlined interface: tabs are no longer cluttered with unnecessary fields — only relevant variables are displayed.

Result: reduced operator workload, faster configuration of complex business logic, and consistent interaction across system modules. This makes Spiro an even more effective tool for teams handling large volumes of data.

Unified Social Auth

In Spiro 2.31, we revisited the logic for working with authentication providers (Google, Apple, Facebook, LinkedIn, and others) to deliver a consistent user experience across all platforms.

Unified logic: we implemented identical token and data processing mechanisms for both web and mobile applications.

Simplified integration: structured configurations allow new authentication methods to be connected faster, without additional code adjustments across different platforms.

Data format standardization

To prevent duplicate accounts and identification errors, we added automatic lowercasing of property values.

Scenario: during registration or authentication, the system automatically normalizes incoming data — for example, email addresses regardless of how they were entered.

Benefit: guaranteed database integrity and elimination of cases where [email protected] and [email protected] are treated as separate entities.

Simply enable the corresponding option, and all values will be stored in a unified format.

Stability and performance

Spiro 2.31 includes deep engineering improvements aimed at enhancing system stability and maintainability.

Improved migration mechanism: the update process is now safer, minimizing downtime risks when deploying new versions.

API logging: API request log display has been improved in the operator panel, making it easier to monitor service interactions when needed.

Performance boost: data processing algorithms have been optimized, resulting in faster system response times under high load.

👉 We’d love to demonstrate how Spiro 2.31 can support your project’s goals. Just fill out the form, and our technical expert will walk you through a personalized overview of the new features.