KuppingerCole’s newest report on “Passwordless Authentication for Consumers” includes FUTURAE! The right time to integrate the future is now. Book your demo!

We value your privacy

We use cookies to improve your experience on our site through website traffic analysis. To find out more, read our updated privacy policy.

Policy

Product Lifecycle & Platform Support Policy

Version 1.2 — Effective May 20, 2026

About

This Policy describes Futurae’s general approach to product lifecycle management and platform support and is provided for general guidance. This Policy outlines the availability, support levels, and technical compatibility of Futurae’s products and features.

The product lifecycle defines the stages Futurae products or features go through, indicating who can access it and what level of support and guarantees apply at each stage.

The platform support policy specifies the technical environments required to use Futurae’s offerings, including supported browsers, operating systems, and hardware.

Futurae may update this Policy from time to time.

The Product Lifecycle

Futurae Services and features may be in one of the following states: Beta, Early Access, General Availability, Discouraged, Deprecated, and End of Life (EoL).

Beta Early Access General Availability Discouraged Deprecated EoL
Availability By invitation By invitation Not recommended for new use Scheduled for removal With ELS*
API Changes Subject to change Backwards compatible Backwards compatible Backwards compatible N/A N/A
Service Level Agreement (SLA) ✗** With ELS*
Support service ✗** With ELS*
Documentation Limited Limited With ELS*
Security & Bug fixes Critical fixes only Critical fixes only With ELS*
Functional updates and enhancements N/A

* Extended Life Support (ELS) agreement
** May be provided at Futurae’s discretion

Lifecycle Stages

Beta

Beta products and features are under active development and are subject to change at any time during the Beta period. Access is typically by invitation to a Beta Program only, often provided through closed preview environments. The purpose of Beta releases is to enable early testing and gather feedback, which helps ensure the maturity of the product or feature.

Beta products and features are supported by a dedicated Futurae team. Documentation is minimal and typically provided directly to invited customers. Features are primarily enabled in Preview Deployments, but may be available in Production environments (marked ‘Beta’) in select cases.

Service Level Agreements and support agreements do not apply to products and features in Beta. Beta products and features are provided on an “as is” and “as available” basis. To the maximum extent permitted by applicable law, Futurae disclaims all warranties, express or implied, with respect to Beta products and features, including warranties of merchantability, fitness for a particular purpose, and non-infringement. Beta products and features are not intended for use in production environments and should not be relied upon for business-critical operations.

Early Access (EA)

A product or feature in an Early Access (EA) stage is new or enhanced functionality made available for customers by invitation. Futurae aims to keep Early Access APIs backwards compatible and stable, although changes may occur during the EA period. Documentation may be limited.

While Early Access products and features are not generally subject to Service Level Agreements (SLAs) or formal support agreements, such provisions may be extended at Futurae’s sole discretion. Except as expressly agreed in writing, Early Access products and features are provided on an “as is” basis, and Futurae disclaims all warranties, express or implied, with respect to Early Access offerings to the maximum extent permitted by applicable law.

General Availability (GA)

A feature or product in General Availability (GA) is available to all customers whose subscription package, tier, or contract includes it.

Features move from Beta or EA to GA when Futurae determines that they meet its internal readiness criteria for general availability. Documentation for features in GA is generally made publicly available on Futurae’s website.

For features or products in GA, we adhere to Service Level Agreements (SLAs) and provide support according to your Customer Agreement with Futurae.

Discouraged

This feature or product remains fully supported for existing implementations but is not recommended for new projects. Functional updates or enhancements are not provided for features or products in this stage. Applicable service level agreements continue to be honored, and support remains in place. In most cases, offerings at this stage are no longer available for purchase (end of sales), though exceptions may apply.

Deprecated

A product or feature in the Deprecated stage is no longer recommended for use and will receive no functional updates. The product or functionality will be removed in the future according to an End-of-life schedule. Futurae will continue to address critical security vulnerabilities (as assessed by Futurae) until the end-of-life date is reached, except where doing so is not technically or commercially practicable. Where reasonably practicable, necessary workarounds, migration paths, and applicable End-of-Life (EoL) schedules will be set out in the relevant documentation or announcement.

Futurae will announce the deprecation and End-of-life schedule of a product or feature on its official channels or directly to affected customers. Customers are advised to upgrade to the next available non-deprecated version or replacement to ensure continued support and functionality.

End of Life (EoL)

When a product, feature, or service reaches its End of Life (EoL), it will no longer be generally available and will not receive standard support or updates, unless otherwise agreed in writing (for example, under an Extended Life Support arrangement). The EoL for features and products is announced according to the predefined schedule below.

Exceptions to the Lifecycle

Not all products and features may go through the full Beta-EA-GA lifecycle. Exceptions may include:

  • Bug fixes that change only the incorrect behavior of a functionality

  • Cosmetic changes, such as changing the label of a field in a user interface

  • Changes that are narrow in scope or effect, or purely additive, such as adding an attribute

End-of-Life Announcement Process

When a feature or product is deprecated and scheduled for End-of-Life (EoL), Futurae communicates according to this schedule:

Schedule from Announcement to Decommissioning:

  • T-(6+) Months: Futurae typically provides at least 6 months’ notice, and aims to provide 12 months’ notice for changes Futurae deems material changes. Longer notice periods may apply where contractually required. Notice periods may be shorter, or modified, where required for security, legal, regulatory, or critical operational reasons, or where continued operation of the product or feature would, in Futurae’s reasonable assessment, pose unacceptable risk. Communication will be made through the appropriate channels (email or the Futurae announcements page). Notice periods are intended to give customers commercially reasonable time to prepare and, where applicable, migrate. The exact notice period may vary depending on the nature and impact of the change.

  • T-3 Months: Reminder notifications are sent.

  • T-1 Month: Final reminders are sent, and limited support is available for non-migration issues.

  • EoL Date: The service is decommissioned or set to read-only mode. Standard updates and support will no longer be provided, unless otherwise agreed in writing.

  • EoL + 30 Days: A data export window will remain open for at least 30 days following the EoL date, after which associated data may no longer be accessible. Longer retention, export, or deletion periods may be specified in the applicable Agreement or Data Processing Agreement, which prevail to the extent of any conflict with this Policy.

Customer Responsibilities:

  • Reviewing EoL announcements and planning their transition.

  • Exporting data before the EoL date.

  • Updating integrations or workflows to supported versions or replacements.

Failure to transition may result in loss of access or data after the EoL period.

Extended Life Support

Futurae may, at its sole discretion, offer Extended Life Support (ELS) for specific products or features beyond their official end-of-life date, upon customer request. ELS will be provided only for a limited duration and is subject to a separate commercial agreement. ELS pricing is set on a per-engagement basis and typically increases over time to reflect the growing effort of maintaining legacy systems. This service is intended to give customers additional time to transition to newer versions or alternative solutions offered by Futurae.

The Platform Support Policy

The platform support policy specifies the technical environments required to use Futurae’s offerings, including supported browsers, operating systems, and hardware.

Supported Android and iOS Versions for Mobile SDKs

Minimum supported mobile OS versions are determined based on the active support lifecycle of the respective platform vendor ecosystem.

SDK support is typically limited to OS versions that are broadly supported within the Apple and Android ecosystems and continue to receive vendor-provided security patches, maintenance releases, or other official support from Apple or Google.

Current minimum supported OS versions for each SDK are documented in the applicable SDK documentation and release notes.

Reference Devices for Testing and Development:

Futurae performs compatibility and validation of its SDKs across a broad range of supported mobile devices and OS versions. The devices listed below serve as Futurae’s primary reference devices for validation and compatibility testing, and may be updated from time to time:

Platform Reference Devices
Android Google Pixel (Latest available model)
Samsung devices:
  • Latest Available S model
  • Latest Available A model
iOS Latest versions of iPhone

Supported Android and iOS Versions for Whitelabel Apps

Our mobile applications follow the same mobile OS support policy as our SDKs. Minimum supported OS versions for each application are documented in the applicable product documentation and release notes, and may be revised over time to align with platform security, reliability, performance, and compatibility requirements.