Meteroid is a monetization platform built so early-stage teams can ship like they're already at scale: ✅ One engine for subscriptions, usage-based pricing, quote-to-cash, invoicing and business intelligence ✅ Support any Go-to-Market motion ✅ Open-source (not open core) and extendable. Self-host it or let us run it. Either way, it’s yours. 🚀
I'm Donatien, maker of Meteroid, along with Gaspard and Teake. We’re excited to finally share what we’ve been building in the open.
• Why another billing tool? Honestly, we were frustrated. The billing space has exploded, but the pattern is always the same: powerful features are gated behind "talk to sales" banners and 5-figures contracts. Early-stage teams are left with duct-taped Stripe setups or rigid systems that can’t evolve.
We wanted to flip that. Meteroid is built on a simple philosophy: Advanced billing capabilities should be accessible from day one (not something you "graduate" into at Series B).
• What we're building: 🔓 Open Source: A monetization platform you can inspect, extend, and self-host (check our repo). For the devs: We are built with Rust, React, Postgres, Clickhouse and Kafka 🦀
⚙️ All-in-One: Usage metering, plans management, quotes, and invoicing in one hub.
💰 Full Flexibility: Usage-based, hybrid, subscriptions, grandfathering, and custom deals.
📊 Data-Driven: Next steps focused on churn signals and upsell triggers, not just invoices.
🤝 Community-Led Roadmap (with a Fast Lane): We build in the open and prioritize features based on the feedbacks of our 900+ community members. But we know business needs can't always wait. Need a feature yesterday? We fully support Sponsored Development. You can fast-track critical integrations or features by sponsoring them, getting exactly what you need while contributing back to the open-source.
We'd love your support on this launch and your honest feedback. Whether it's feature requests, deep technical questions, or even a friendly roast, we're here for it! 🚀
Congratulations on the launch! How about processing cards from other countries? For example, in the Netherlands my US card is often not accepted.
How easy is it to migrate from an existing Stripe-based setup to Meteroid without breaking current subscriptions or usage logic?
Open source billing infrastructure is crucial for SaaS builders who want transparency into their revenue ops. Really appreciate that this is on GitHub - being able to fork and customize pricing logic is a real advantage over closed billing platforms. What's the migration path like for teams already on Stripe Billing?
Congrats on the launch guys! Really useful one, especially for small teams like my stage now. Best of luck!
Open-source and self-hosting are powerful but raise trust and operational questions: how do you think about supportability and reliability (e.g., “who do I call at 2am”), and what’s your long-term model for balancing community-led roadmap with business-critical, time-sensitive needs?
So you’re telling me I don’t need a PhD in Stripe webhooks anymore? I’m listening :D
Meteroid being fully OSS (not open-core) + the Kafka → ClickHouse metering pipeline is a strong “ship pricing like you’re at scale” stance. How are you ensuring exactly-once / idempotent usage ingestion so retries don’t double-bill (event IDs, dedupe windows, replay)? We dealt with similar at scale and “late events + corrections” was the constant headache. Any plans for native revenue recognition + proration audits out of the box? 🔥
Really impressed by the vision here. We often see a gap between how GTM teams want to price and what engineering can actually support.
Upvoted for the mission to make advanced monetization accessible to everyone!
The struggles sound very familiar. I’ve worked on a pricing project that took months to get even close to right, largely because the billing architecture itself was fundamentally broken. Everything lived in Excel spreadsheets, scattered across internal wikis, with outdated pricing details and highly complex logic. With over 100 options influencing the final price a client sees, pricing was AND is difficult to understand for both customers and internal teams. Spoiler alert: we’re still not there yet, which is exactly why this billing platform be a very interesting product to explore!
Hey all! I’m Teake, co-founder at Meteroid 👋
I’m on the product/design side, and I’ve spent way too much time dealing with billing systems that were built for one very specific case and then left untouched. They work fine as long as nothing changes. But the moment you want to tweak pricing or try something new, the whole thing becomes fragile overnight.
We built Meteroid because billing shouldn’t be a black box. It should be flexible by default, so teams can experiment and iterate without breaking things.
Happy to chat product & design!
Cool. I am now working on some payment stuff. Tho a little bit different things (like merchants, ISO, PSP etc.) So definitelly will have a look at it :)
Hey everyone! I'm Gaspard, co-founder and engineer at Meteroid 👋
I've been in the data-driven billing trenches for years and got tired of watching teams rebuild the same infrastructure over and over. So we built what we wished existed, a flexible platform, open-source, and actually enjoyable to use and work on.
Happy to chat about the tech stack (Rust, Kafka, Clickhouse), scaling, architecture decisions, self-hosting or anything else. Ask away!
Hi Makers! 👋
I'm Donatien, maker of Meteroid, along with Gaspard and Teake. We’re excited to finally share what we’ve been building in the open.
• Why another billing tool?
Honestly, we were frustrated. The billing space has exploded, but the pattern is always the same: powerful features are gated behind "talk to sales" banners and 5-figures contracts. Early-stage teams are left with duct-taped Stripe setups or rigid systems that can’t evolve.
We wanted to flip that. Meteroid is built on a simple philosophy: Advanced billing capabilities should be accessible from day one (not something you "graduate" into at Series B).
• What we're building:
🔓 Open Source: A monetization platform you can inspect, extend, and self-host (check our repo).
For the devs: We are built with Rust, React, Postgres, Clickhouse and Kafka 🦀
⚙️ All-in-One: Usage metering, plans management, quotes, and invoicing in one hub.
💰 Full Flexibility: Usage-based, hybrid, subscriptions, grandfathering, and custom deals.
📊 Data-Driven: Next steps focused on churn signals and upsell triggers, not just invoices.
🤝 Community-Led Roadmap (with a Fast Lane): We build in the open and prioritize features based on the feedbacks of our 900+ community members. But we know business needs can't always wait. Need a feature yesterday? We fully support Sponsored Development. You can fast-track critical integrations or features by sponsoring them, getting exactly what you need while contributing back to the open-source.
We'd love your support on this launch and your honest feedback. Whether it's feature requests, deep technical questions, or even a friendly roast, we're here for it! 🚀