Launching today
Meteroid
Billing platform to launch, test, + scale business models
160 followers
Billing platform to launch, test, + scale business models
160 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
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!
minimalist phone: creating folders
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 :)
Meteroid
@busmark_w_nikaΒ Great to hear ! Always happy to share experience and feedback if you wanna chat !
Meteroid
Thanks @busmark_w_nikaΒ for your comment! Always happy to chat if you face billing issues ;)
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
Meteroid
@abod_rehmanΒ thanks a lot for your support!
You've put the finger on a massive pain point. That gap between GTM strategy and engineering capacity is exactly what turns pricing experiments into months-long projects.
I'm glad the mission resonates with you. Making advanced monetization accessible to everyone (not just big SaaS) is what keeps us pushing every day! ;) We truly think that advanced monetization capabilities are a must-have from day 1 and not a luxury you can only afford at Serie B.
Meteroid
@abod_rehmanΒ Spot on! Thanks a lot, really appreciate the support!
Meteroid
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!
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 !