Hello,

We are pleased to announce the release of version 0.4.0, which introduces contaminated data cleanup, user aliasing, and a simplified Docker deployment model.

New Features​

• Contaminated data cleanup: Hyppot now detects when a single person was exposed to more than one variant of the same experiment — either under the same user ID or across linked identities — marks those impressions as contaminated, and excludes them from conversion and metric statistics. Detection runs at alias time, via a background job (every 10 minutes), and at statistics time. The experiment Statistics tab now reports Contaminated users excluded: N. See Contaminated data cleanup for details.

• User aliasing: You can now link multiple user IDs as belonging to the same person (for example, anonymous and logged-in IDs at login). New REST API endpoints: POST {pathPrefix}/userAlias and GET {pathPrefix}/userAlias/{userId}. Available in-process via IUserAliasService and through the Hyppot.Sdk package. Aliases are retained for a configurable period (UserAliasRetentionPeriod, default 30 days) and cleaned up automatically. User aliasing must be performed from your backend — the browser SDK does not expose it.

Breaking Changes​

• Docker image is now PostgreSQL-only: The Docker version no longer supports selecting different database providers. The Docker image now works exclusively with PostgreSQL using the DB_CONNECTION_STRING environment variable. If you were previously using SQLite or SQL Server with the Docker image, you must migrate to PostgreSQL. Contact us for assistance to ensure a seamless migration. SQLite and SQL Server remain supported via NuGet integration.

Version 0.3.1 introduces improvements for validations on the initial configuration page for the Docker version of Hyppot. Please note that there are no NuGet or npm packages changes, so this version will be skipped for packages.

Hello,

We are pleased to announce the release of version 0.3.0, which introduces major new features and enhancements!

New Features​

• Feature Toggles: You can now model feature toggles in addition to experiments and define related configuration options. This enables trunk-based development and separates feature toggling management from A/B tests and experiments.
• API Key Authentication: You can now generate and manage API keys, providing enhanced security and integration flexibility.
• .NET SDK: The Hyppot SDK is now available as the Hyppot.Sdk NuGet package, allowing seamless integration with Docker-hosted Hyppot instances in .NET backends.
• CORS policy config: it is possible to easily set up CORS policies

Support for SDKs for other backend technologies, such as Node.js, is coming soon.

Other Changes

• API endpoints have been unified and reorganized to be more intuitive, self-explanatory, and future-ready as a public API. Also, We've renamed the npm frontend integrations package to hyppot-browser to clearly identify its purpose.
• a lot of other smaller, miscellaneous UI changes

Breaking Changes​

• All public interfaces are now asynchronous.
• As you can now resolve both experiments and feature toggles, IExperimentationResolver has been renamed to IRolloutResolver, responsible for both.
• For the same reason, IExperimentTracker is now IRolloutTracker.
• Namespaces have been unified and adjusted.
• npm package hyppot was renamed to hyppot-browser

Hyppot Docker Image Now Available​

We're excited to announce that Hyppot is now available as a Docker image, making it easier to deploy and run your A/B testing infrastructure.

What's New​

• Official Docker Image: Pre-built Docker container available in GitHub Container Registry
• Easy Deployment: Get Hyppot up and running with a single docker run command
• Production Ready: Includes all necessary components for running Hyppot in containerized environments
• Available at ghcr.io/hyppot/hyppot-server

Getting Started with Docker​

Pull and run the Hyppot server:

docker pull ghcr.io/hyppot/hyppot-server:latest
docker run -p 8080:80 ghcr.io/hyppot/hyppot-server:latest

What's Included​

The Docker image contains:

• Hyppot server with admin panel
• All necessary runtime dependencies
• Pre-configured for immediate use
• Support for all database providers (PostgreSQL, SQL Server, SQLite)

Visit our installation documentation for detailed setup instructions and configuration options.

Version 0.2.3 introduces improvements for loading view for conversion types definition section of the admin panel

Here's the list of changes and improvements in the 0.2.2 release of Hyppot:

• add possibility to upload the license file via admin panel in addition to placing a file on the server, using the dedicated panel shown when license validation failed
• Improve distribution of users across various experiments
• Add possibility to disable automatic impression tracking in JS SDK
• Improve error handling and empty states in admin panel

New features & changes​

• First variant created in experiment is always a baseline variant
• Conversion statistics and confidence intervals for conversions are calculated against baseline variant
• Improve Admin UI to better embed it in web applications
• Add possibility to customize base path for Hyppot endpoints

Fixes​

• Fix Hyppot routing configuration for admin panel routes
• Remove top margin in admin panel causing website to be centered horizontally
• Improve handling for non existing paths

Here's the overview of changes introduced in v0.2.0

New features & changes​

• new Typescript/Javascript SDK to allow frontend experimentation available as hyppot package available via npm
• add possibility to delete old, outdated experiments along with all its associated data
• unify tracking and conversion definition APIs as async methods.

This is the very first public Beta release of Hyppot. Instead of listing all functionalities here, we invite you to see the Hyppot documentation or check out the quickstart guide.