Overview

Hopsworks brings feature storage, governance, and deployment choices together. Teams can use its managed SaaS offering or deploy on cloud Kubernetes, with an air-gapped data-centre option for Enterprise. That flexibility suits organizations with differing infrastructure and security needs, though self-hosting calls for meaningful Kubernetes capacity and operational commitment.

Key features

The offline store uses Apache Hudi tables on HopsFS, while the online store uses RonDB. Keeping both in one platform supports historical training workflows alongside online feature access. Point-in-time training datasets reproduce feature values from a past moment, helping prevent data leakage when assembling model training data.

The Feature Registry offers metadata search, automatic feature analysis and statistics, version comparison, and access control. These tools help teams discover and govern shared features as definitions change. Monitoring tracks feature distributions, detects drift, and can send alerts, making it useful for teams that need visibility into changing production inputs.

Integrations include Airflow, Apache Flink, Databricks, Snowflake, Spark, AWS SageMaker, Vertex AI, and Weights & Biases. Security includes encryption at rest and in transit, project-based access controls, and authentication options such as two-factor authentication and SSO. Hopsworks states ISO 27001 and SOC 2 Type 2 certification and GDPR compliance.

Pricing

Hopsworks uses a freemium model. The Free plan is free and includes one project, Feature Store, Model Registry, and community support, with no credit card required. Its single-project ceiling makes it suitable for evaluation or a contained initiative, but restrictive for teams coordinating several projects.

The SaaS plan has custom pricing, billed Pay as you go. It includes unlimited projects, Feature Store and Model Registry, Model Serving, usage-based pricing, community support, and a platform SLA. This is the more suitable managed option for teams that need to expand beyond one project and add serving; the usage-based model means costs depend on use.

Enterprise has custom pricing and includes all SaaS features, on-premise and air-gapped deployments, a dedicated support team, custom integrations, and a guaranteed SLA. It is aimed at organizations that need deployment control or dedicated support rather than a self-service plan.

Platforms

Hopsworks supports API, Linux, self-hosted, and web access, with both managed and self-hosted deployment and both online and offline stores. The documentation describes managed SaaS and deployment on AWS, Azure, or GCP Kubernetes, as well as air-gapped data centres. The Kubernetes installer lists AWS EKS, Google GKE, Azure AKS, and OVHCloud, requires Kubernetes 1.27 or higher, and recommends at least 4–5 nodes. That is a substantial starting footprint for smaller teams considering self-hosting.

Who it's for

Hopsworks is designed for data scientists, data engineers, developers, platform engineers, security engineers, and administrators building production AI systems. It is particularly compelling for teams that need feature reuse, historical training data, monitoring, and deployment flexibility in one platform. A single-project free tier is less suited to evaluating multiple workloads in parallel.

Pros and cons

Pros: Online and offline stores plus point-in-time training datasets support both serving and leakage-conscious training workflows.
Pros: Registry search, analysis, version comparison, access control, and drift monitoring address feature governance and production visibility.
Pros: Managed, cloud Kubernetes, and air-gapped deployment options give organizations room to match infrastructure and security requirements.
Cons: The Free plan is limited to one project, which constrains teams evaluating or using the platform across multiple initiatives.
Cons: Self-hosting requires Kubernetes 1.27 or higher and a recommended 4–5 nodes, raising the infrastructure bar.
Cons: SaaS and Enterprise have custom pricing, so neither offers a fixed price for straightforward budget comparison.

Alternatives

For teams choosing among Feature Store Software, Hopsworks stands out for its combination of online and offline storage, registry, monitoring, and deployment choices. Consider these alternatives when their pricing or platform model better fits your needs.

Amazon SageMaker Autopilot is a paid API and web option with a free trial and pay-as-you-go pricing; its listed on-demand pricing has no minimum fees or upfront commitments.
Canal is a free, open-source option for API, Linux, macOS, and self-hosted environments.
Feast is a free, open-source feature store for API, Linux, self-hosted, and web environments.
JFrog ML Feature Store is a paid option with a free trial and API, Linux, self-hosted, and web support; pricing is custom.
Metarank is a free option supporting API, Linux, macOS, self-hosted, and Windows.
OpenMLDB is a free, open-source machine-learning database with standalone and cluster versions.
Feathr is a free option for API, Linux, self-hosted, and web environments.
Chronon offers an Apache 2.0 open-source plan at no cost, with no usage limits stated; it supports API and self-hosted environments.

Verdict

Choose Hopsworks if your team needs a production-oriented feature platform that connects online serving, historical training data, governance, and monitoring, with managed and self-hosted deployment paths. Look elsewhere if you need a fixed SaaS price, a free tier for multiple projects, or a self-hosted option with a smaller infrastructure footprint.

	Databricks Feature Store	Hopsworks Feature Store
Free plan		Yes
Free trial	Yes
Paid from		Free
Platforms	api, Web	api, Linux, self-hosted, Web
Online store	Yes	Yes
Offline store	Yes	Yes
Point-in-time joins	Yes	Yes
Feature monitoring	Yes	Yes
Deployment model	cloud	both
Serving modes	both	both
Free plan		Yes

Databricks Feature Store vs Hopsworks Feature Store

Databricks Feature Store

Hopsworks Feature Store