Meteroid
Billing platform to launch, test, + scale business models
290 followers
Billing platform to launch, test, + scale business models
290 followers
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. 🚀
Meteroid
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! 🚀
@ddu Congrats on the launch! How does it differ from products like @Dodo Payments or similar?
Meteroid
@rohanrecommends thanks for asking! Here is how we stand out:
Dodo Payment is a Merchant of Record - like Paddle, handling everything from payment to taxes, focused on simplifying the B2C flows (marketplace, "hands on" self serve for small teams). We're focusing more on the B2B flows
We fully support Sales-led motions with Quotes
Also we don't lock you in: we let you pick the best payment providers for your specific markets/geographies
And last but not least, we are fully open source!
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? 🔥
Meteroid
@ryan_thill Hi Ryan ! We're using an idempotency key (event ID) to deduplicate, both via a specific Clickhouse table construct (eventual dedup) and at query time to guaranty true exactly-once processing. It's a bit more costly and we'll evaluate alternatives to do more within Kafka, but at our scale it works perfectly. We do support late events as long as they stay within the current period + grace period (once finalized you enter the credit note category).
Regarding audit, invoices do keep a copy of all the data used to compute them, we don't expose proration audit info though, if needed we can.
Regarding the revenue recognition, our goal throughout the year is to build a complete data-driven decision platform for finance and sales, through advanced and realtime analytics. We do not plan at this point GAAP/IFRS-compliant deferred revenue accounting though (but we can integrate with accounting softwares that do).
Product Hunt
Meteroid
@curiouskitty thanks for your question.
We offer different plans with varying levels of service (community support, email support, dedicated account manager, SLA to handle the "2am call"...) depending on users' needs.
Regarding our roadmap, we fully support Sponsored Developments. You can fast-track critical integrations or features by sponsoring them. This ensures you get exactly what you need on your timeline while contributing back to the open-source ecosystem.
Helply
Nice! Are you planning on supporting subscription schedules as well? Side-note, this page in your docs is 404ing: https://docs.meteroid.com/subscriptions/what-is-a-subscription
Meteroid
@jared_scheel Hey Jared ! Subscription phases is not there yet but it's definitely on the roadmap. If you have a specific use case for schedules let us know, we prioritize based on the community feedback !
Thanks for the report, we'll look into it !
Meteroid
Thanks@jared_scheel! We currently support controlling the timing and lifecycle of subscriptions. Full-on phasing isn’t live yet, but is indeed definitely on the roadmap.
Meteroid
@jared_scheel what do you mean by subscription schedules? We already support creating subscriptions in the past/future, is that what you meant?
Happy to further discuss the topic 😉
Helply
@ddu schedules are definitely a complex case, but they are useful for managing phased trials, controlled upgrade / downgrade flows, contractual plans, etc.
Meteroid
@jared_scheel thanks for the clarification. Indeed not yet there but definitely something we can do. What’s your specific timing? If you have a deadline in mind for when you'd need this shipped, we can see how to make it happen.
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!
Meteroid
@jasminiii your story is exactly why we built Meteroid!
What you described—pricing living in Excel and outdated wikis—is the reality for so many SaaS companies. The fundamental problem is that pricing data is usually scattered among many teams (Sales, RevOps, Finance, Product) creating massive data silos.
Meteroid acts as the single source of truth by managing the entire Product Catalog in one place. By unifying metering, billing, invoicing and quoting we break those data silos and ensure that what Sales quotes is exactly what Finance invoices and what the Product actually delivers.
Beyond the internal efficiency, this is also about Customer Confidence. When pricing is a "black box", too complex to explain or source of mistakes, trust vanishes. Having a clear, automated system brings that transparency back to the client (ultimately reducing churn).
We’d love to help you get "there" and finally retire those spreadsheets! Good luck with your ongoing project! 🚀
Meteroid
Thanks@jasminiii! This is exactly the type of scenario we’ve experienced ourselves and had in mind when building @Meteroid. Appreciate the support!
Triforce Todos
So you’re telling me I don’t need a PhD in Stripe webhooks anymore? I’m listening :D
Meteroid
@abod_rehman That's right 😄 We're abstracting out the payment provider complexity. We've started with Stripe, but are working on adding cheaper and local alternatives !
Meteroid
Monetization is indeed complex to handle. We built Meteroid to make it easy. @abod_rehman forget about your PhD! ;)
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?
Meteroid
@kxbnb thanks for your comment. We truly believe as well that an open source billing platform really brings transparency into the revenue stack. And of course, you're free to inspect & extend it if required!
The path is actually quite straightforward:
Set up your invoicing entities and payment info (we support a native integration with Stripe Payment for example)
import your customers into Meteroid (can be done via API or a file)
create your plans (an billable metrics if you need usage based billing) and create your subscriptions (can be done via API)
And basically that's all! ;)
If required, you can find more details here
Always happy to discuss if you face any issue :)