Over the past year, the GreptimeDB team has been steadily refining the product, making major gains in both performance and stability. Version 1.0 is a huge milestone on our path to maturity — marking stable APIs, production readiness, and proven, verifiable performance.

This post walks through key achievements from the past year, what we’re currently polishing for the final release, and the roadmap leading up to v1.0.

---

Highlights from the Past Year

In the past twelve months, we’ve shipped 7 major releases and 23 minor ones, each bringing meaningful improvements across the stack. Some of the most notable updates include:

• Enhanced Logging Capabilities – Introduced the matches_term retrieval function and a new skip index built on Bloom filters, significantly cutting index storage overhead.
• Bulk Ingestion Protocol – Rolled out a high-throughput Bulk Ingestion protocol for large-scale data imports, boosting write performance and minimizing write amplification.
• Stronger Metrics Engine – Optimized sparse primary key encoding to speed up time-series aggregations and improved PromQL compatibility.
• RDS Support for Metadata – Added the option to switch the metadata backend from etcd to RDS, improving stability and reliability in large clusters.
• Dual-Engine Stream Computing – The Flow engine now supports both batch and streaming modes, covering real-time alerting and offline processing scenarios.
• Read-Only Replicas – Enabled on-demand scaling of read-only replicas to isolate heavy queries from write workloads, maintaining smooth performance even under large query loads.
• Ecosystem Integration – Added full OpenTelemetry metrics, logs, and traces ingestion, with support for Jaeger, Loki, and ElasticSearch protocols/backends.

---

What We’re Working on Now

• Core Feature Finalization – Wrapping up Table Repartition, New JSON Type, Async Index Building, and optimization of merge requests for Region migration.
• Hardening for Stability – Expanding our test coverage with more comprehensive scenarios, incorporating real-world feedback from the community, and stress-testing under production-like conditions to ensure enterprise-grade reliability for v1.0.

---

Release Roadmap

We’ll move toward the v1.0 GA in two-week iteration cycles. The tentative timeline is as follows:

• Beta1 (November 10, 2025) – Introduce bulk data ingestion, a new bulk memtable, and other major enhancements; gather community feedback.
• Beta2 (November 24, 2025) – Address feedback from Beta1, add async indexing, global index rebuilding, and Region batch migration for testing.
• RC1 (December 8, 2025) – Tune performance and stability based on Beta2 feedback, complete Table Repartition, and run long-duration stress tests.
• RC2 (Optional, December 22, 2025) – Release if critical issues arise during RC1 testing; otherwise, proceed to GA directly.
• GA (January 10, 2026) – Freeze APIs and protocols, officially release v1.0 along with upgrade guides, benchmark results, and a list of known issues.

---

Why v1.0 Matters

Version 1.0 will freeze external APIs and protocols, ensuring long-term compatibility without frequent adjustments. We’ll also publish performance and reliability benchmarks — including zero data loss under continuous high-concurrency load and stable operations during automatic, load-balanced Region migrations.

This release not only provides confidence for existing deployments but also establishes a solid foundation for everything that comes next.

---

Closing Thoughts

Since open-sourcing in November 2022, GreptimeDB has continued to grow with tremendous support from the developer community. Version 1.0 is a major milestone, and we couldn’t have reached it without your contributions — whether through code, issue reports, or discussions.

We’re deeply grateful for your support and can’t wait to share the v1.0 release with you.

Let’s build the next chapter of GreptimeDB together!