GreptimeDB is a high-performance, open-source, and cloud-native observability database purpose-built for real-time observability. As more developers and enterprises adopt it in production, we believe every journey with GreptimeDB—from initial trials to deep integration—is worth documenting.

To celebrate our growing community, we’re launching a writing campaign: “GreptimeDB in the Wild - Share your real-world story. Get featured. Get rewarded”. Whether you're migrating from another solution, deploying GreptimeDB on the edge, building tools around it, or analyzing its source code—we want to hear your GreptimeDB-related experience.

🧭 Why Participate?

✨ Build Your Technical Influence

Your article may be published on the Greptime official blog, and shared across our global channels including X (Twitter), LinkedIn, Slack, and WeChat. It’s a great way to showcase your engineering mindset and practical skills to a wider developer audience.

🎁 Win Exclusive Swag and Recognition

Every approved submission receives a Greptime swag pack.

Exceptional pieces will receive Amazon Gift Card prizes and a special contributor badge within the community.

Reward	Bonus	Amount
Grand Prize	$500 Amazon gift card + certificate of honor + Greptime customized power bank + customized backpack + matching palm rest (keyboard) + customized badge + exclusive title	1 slot
First Prize	$200 Amazon gift card + certificate of honor + customized backpack + matching palm rest (keyboard)	2 slots
Second Prize	$50 Amazon gift card + certificate of honor + customized backpack	5 slots
Participation Prize	Greptime Customized Gift Packages	selected submissions

💬 Get in Touch with the Core Team

We’re genuinely interested in your technical scenarios. Selected authors may be invited to a 1:1 session with the GreptimeDB engineering team, and even contribute to upcoming product features.

📌 Submission Guidelines (Greptime-Relevant Only)

We're looking for real, technical, GreptimeDB-related stories in either English or Chinese. Suggested word count: 800–2000 words.

Examples of acceptable topics:

• Your migration journey to GreptimeDB (from Prometheus, InfluxDB, Loki, etc.)
• Production use cases or edge deployment experiences using GreptimeDB
• Personal growth stories related to working with GreptimeDB
• Architectural deep dives or source code analysis of GreptimeDB features

✅ All content must be directly related to GreptimeDB.

To enrich your post, we encourage adding:

• Performance benchmarks or comparisons
• Architecture diagrams and workflows
• Screenshots, dashboards, configuration samples

🔍 Evaluation & Translation Notes

• Submissions in English is welcome.
• No fully AI-generated content allowed. We use AI-content detection tools and will reject submissions with over 20% AI-generated content.

🏁 Selection Criteria (based on the original manuscript):

• Logical clarity and readability
• Relevance and value to the GreptimeDB community
• Technical depth and originality

Final winners will be selected by a panel of Greptime Committers and Community Advocates.

✉️ How to Submit

📨 Email your article or story to [email protected] or [email protected]

🗓 Submission Deadline: October 31, 2025

🏆 Results & Rewards Announcement: November 30, 2025

🎙 From X to GreptimeDB: It's More Than a Migration

Choosing GreptimeDB isn’t just about replacing a tool—it often reflects a shift in how teams approach real-time data, observability, and scalability.

We’re excited to hear your GreptimeDB story.

— Greptime Community Team

Event terms subject to Greptime's interpretation.