Chronon
chronon.ai
- Free plan
- API
- Self-hosted
What Chronon is
Chronon is an open-source feature platform for building and operating machine-learning data pipelines. It computes features in batches and in real time for online serving and offline training or evaluation. Teams define features through a Python API with transformations and aggregations, using inputs such as event streams, warehouse tables, databases, change data streams, service endpoints, and request-context data. Point-in-time-correct backfills are intended to keep offline training data consistent with online inference. Chronon can generate monitoring pipelines for training-data quality, training-serving skew, and feature drift. Batch processing uses Spark; streaming options include Spark Streaming and an experimental Flink connector. Online serving uses Java or Scala Fetcher libraries embedded in an application or service, with a user-provided key-value store such as Redis or DynamoDB. Jobs require Spark, and the data integration guide assumes a Spark environment connected to a warehouse. The quickstart describes local setup with Docker and docker-compose. Chronon is self-hosted and licensed under Apache 2.0; its open-source plan is listed as free.
Who it suits
Chronon is suited to machine-learning teams that need batch and streaming feature computation, offline training data, and online serving. It assumes access to Spark and a willingness to manage a self-hosted deployment.
Good to know, and what to watch
- Supports batch and real-time feature computation.
- Backfills aim to preserve point-in-time correctness.
- Generates pipelines for feature and data monitoring.
- Apache 2.0 licensed and self-hosted.
- Chronon jobs require Spark.
- The quickstart requires Docker and docker-compose.
- Online serving uses embedded Java or Scala libraries.
Plans
Every plan and priceOpen source
Open source
Getting started
- Visit https://chronon.ai/ and review the project quickstart.
- Install Docker to run Chronon locally with the described docker-compose file.
- Configure access to a Spark environment connected to your data warehouse.
- Define features with the Python API and configure jobs through spark_submit.sh.
- For online streaming, configure a StreamDecoder for Kafka message bytes.
- Choose a key-value store such as Redis or DynamoDB for online serving.
The verdict
Chronon brings feature computation, serving, and monitoring into an open-source platform. Spark is a core setup requirement, so teams should account for its environment and self-hosting needs.
Questions people ask
Is Chronon free?
Yes. The open-source plan is free under the Apache 2.0 license, with no usage limits stated.
Which data sources can Chronon use?
Documented inputs include event streams, warehouse tables, production databases, change data streams, service endpoints and request-context data.
What does Chronon use for batch and streaming jobs?
Batch processing uses Spark. Streaming options include Spark Streaming and an experimental Flink connector.
What is required for online serving?
Production serving uses Java or Scala Fetcher libraries embedded in a service or application, along with a user-provided key-value store.
How can users get help or report a security issue?
The project README points to GitHub Issues for bugs and feature requests, and community Slack for discussion and support. Potential security issues should be reported through Airbnb's Bug Bounty program.
What the maker publishes
- Adoption
- The project lists Airbnb, Stripe, OpenAI, Roku, Netflix, Uber, Intuit, Airwallex, Sardine AI, and Monzo Bank as adopters. source
- Batch and streaming
- Chronon uses Spark for batch jobs and supports streaming with Spark Streaming or an experimental Flink connector. source
- Compute integrations
- The homepage describes Apache Spark for batch processing and Apache Flink for streaming aggregations. source
- Consistency
- Chronon supports temporally accurate offline backfills intended to keep training data consistent with production inference data. source
- Data inputs
- Documented inputs include event streams, warehouse tables, production databases, change data streams, service endpoints, and request-context data. source
- Data sources
- Chronon can consume event streams, database snapshots, change data streams, service endpoints, and warehouse tables. source
- Deployment requirement
- Chronon jobs require Spark, and users configure execution through a spark_submit.sh script. source
- Feature computation
- Chronon supports batch and real-time feature computation for online serving and offline training or evaluation. source
- Feature definitions
- Features can be defined through a Python API that supports transformations and aggregations. source
- Feature definitions
- Users define features with a Python API using concepts such as GroupBy, Join, and StagingQuery. source
- Feature monitoring
- Chronon can generate monitoring pipelines for training-data quality, training-serving skew, and feature drift. source
- Getting started
- The project quickstart requires Docker and describes running Chronon locally with a docker-compose file. source
- License
- The Chronon project is published under the Apache 2.0 license. source
- Monitoring
- It can generate monitoring pipelines for training-data quality, training-serving skew, and feature drift. source
- Orchestration
- Airflow is documented as the best-supported orchestration method, while other orchestration integrations are also possible. source
- Orchestration
- Airflow is the best-supported orchestration method, though the documentation says other integrations are possible. source
- Point-in-time correctness
- Chronon supports point-in-time-correct training backfills to help keep offline training features consistent with online serving. source
- Product
- Chronon is an open-source feature platform for building, deploying, managing, and monitoring machine-learning data pipelines. source
- Security reporting
- The repository security policy asks users to report potential security issues through Airbnb's Bug Bounty program rather than public issues or pull requests. source
- Serving API
- Production online serving is provided through Java or Scala Fetcher libraries embedded in a service or application. source
- Serving API
- Chronon provides Java and Scala Fetcher libraries, and the Fetcher can also be used to create a service callable over REST. source
- Setup requirement
- Chronon jobs require Spark to run, and the data integration guide assumes access to a Spark environment connected to the data warehouse. source
- Storage integration
- Chronon uses a bring-your-own key-value store approach, with Redis and DynamoDB listed as examples. source
- Storage integration
- Online serving requires integrating a key-value store that supports point writes, point lookups, scans, and bulk writes. source
Checked against the maker's pages on 4 Oct 2026.