JMjmacd·Jul 27, 2023Submission
1 points · Open discussiontierrun
tier
Go2022–2023
tierrun / tier · Archived
tier
The easiest way to add pricing to your SaaS. Get billing over with.
4Distinct people
12Mentions
0Explicit recommenders
970GitHub stars
What to know before exploring
What it is
The easiest way to add pricing to your SaaS. Get billing over with.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month12 dated mentions
Observed mentions: 2022-11-02 00:40:29 UTC to 2023-07-27 19:35:58 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Nov 2022 | 2022-11-01 00:00:00 UTC | 2022-12-01 00:00:00 UTC | 3 | 3 | 0 |
| Dec 2022 | 2022-12-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 2 | 0 |
| Jan 2023 | 2023-01-01 00:00:00 UTC | 2023-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2023 | 2023-02-01 00:00:00 UTC | 2023-03-01 00:00:00 UTC | 5 | 1 | 4 |
| Mar 2023 | 2023-03-01 00:00:00 UTC | 2023-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2023 | 2023-04-01 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2023 | 2023-05-01 00:00:00 UTC | 2023-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2023 | 2023-06-01 00:00:00 UTC | 2023-07-01 00:00:00 UTC | 1 | 0 | 1 |
| Jul 2023 | 2023-07-01 00:00:00 UTC | 2023-08-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
12 sourcesWe’ve built https://GitHub.com/tierrun/tier with a local sidecar that can talk directly to stripe to help simplify situations like this.
A pure SaaS model for billing doesn’t do much more for you at then end of the day other than to apply billing ratings and generate an invoice (which Stripe can and is doing for you already).
I’d love to learn more about what you’d like to do with Stripe and how you are handling entitlements, plan versioning, etc
In Launch HN: OpenMeter (YC W23) – Real-Time, Open Source Usage Metering> Webhooks for critical application paths just seem like a bad idea all around really
Well, put. I've been deep in the Stripe API for a while now, and the invoices API provides up-to-date account status information and what a customer is paying for. This can be referenced as needed and, if desired, cached with some TTL and referenced as the "truth." Then webhooks can be viewed as a convenient way to bust the cache quicker than waiting for the TTL to expire.
It could be better, but it provides the necessary information without relying on webhooks.
An example of how we use this API as a form of entitlement checks at Tier can be found here: https://github.com/tierrun/tier/blob/f7c32426d30ca314706ca7e...
In Down the Cloudflare / Stripe / OWASP Rabbit HoleAs all-in-Golang user, wish Tier to succeed too!
Want to say Thank you for putting all artefacts online. Same applies to Lago!
Admire your focus on Stripe and beginner friendly approach from the day one
https://github.com/tierrun/tier/blob/main/pricing/schema.jso...
https://docs.tier.run/docs/resources/mapping-to-stripe
https://github.com/tierrun/tier/wiki/Stripe-Glossary
Lago backend is built with Ruby and GraphQL ... which is kind of deal-breaker for me. No time to invest in Ruby ecosystem. I'm only using opensource products which I can fork and debug later on.
https://github.com/getlago/lago-api/tree/619a7a53f98d9a19908...
Lago is much closer the production ready however. Solid stand-alone tool already.
Tier like projects gives me hope to give SaaS user better embedded billing experience and more control in the future.
My biggest scar
Read the rest
e - successful open source projects are getting too many extraline of code overtime.
Ex. Sentry with 25+ containers inside
https://github.com/getsentry/self-hosted/blob/48c855aa3def45...
Exciting to see the progress of Lago and the attention being given to the challenges in the SaaS billing world.
We're also working in the billing space with a complementary tool, Tier (https://github.com/tierrun/tier). Although we currently do not support Lago directly, it's exciting to see more options emerging. Their content marketing has been particularly impressive on HN and in general.
With metering, entitlement management, CPQ, feature gating, and everything else required in a modern SaaS company, the PriceOps space can be quite complex for developers.
Congratulations on the launch and best of luck!
In Launch HN: Lago (YC S21) – Open-source usage-based billingI'd love your feedback on https://priceops.org
We recently open sourced Tier http://github.com/tierrun/tier which combines metering, entitlements, feature flags and a client side SDK to simplify things.
In Show HN: We built an open-source LaunchDarkly alternative for B2BsMajor Issues with Stripe's Test Mode
1 points · Open discussionStripe Needs Test Envs and Preview Deployments
2 points · Open discussionShow HN: Switch – like Git Branch, for Stripe
Hi, this is Jevon from Tier [1]. We posted our first product a few weeks ago. [2] Thanks to everyone who gave feedback and tried it out.
We've been building a lot of functionality on top of Stripe and we've been hearing from early users about the challenges of scaling Stripe's test mode.
Because you have 1 organizational account in Stripe and 1 test environment for that account, you can run in to a bunch of edge cases around how data is stored and deleted (or not). Blake wrote a separate post about those issues here [3].
We were excited to build this feature and write about it because we have gotten tired of making fake accounts which become hard to track because we're never sure what state each account is in.
Tier switch lets you spin up ephemeral test environments and you can instantly access them. It feels a lot more like a Netlify or
Read the rest
Vercel deployment preview. This is nice when you are creating new Stripe backed features but they aren't in your main branch yet and you want to avoid polluting the test account that other members of your team might be using.
It's a pretty specific itch to scratch, but it has been one we've seen ourselves and heard about from a few others. Hopefully it will be useful to you too at some point.
1: https://github.com/tierrun/tier
2: https://news.ycombinator.com/item?id=33429972
3: https://blog.tier.run/tier-switch-git-branch-for-stripe
Show HN: Tier.run – Terraform for Stripe
Hi HN, we are Jevon, Blake and Isaac, we've been working on Tier for a little while ( http://github.com/tierrun/tier )
Tier is "Terraform for Stripe" but it goes further and gives you feature flag style access checks, and allows you to count/report usage which can be used for metered billing.
When we started Tier, we knew that there was something interesting in the SaaS pricing and packaging space. Adjusting price is the single most effective lever a business can use to achieve product/market fit, and there's a strong correlation price nimbleness and market success.
In spite of overwhelming evidence of this, most startups pick the price for their product once and then never change it, opting instead to invest in less effective levers like CAC, sales efficiency, "virality", churn, etc. Why?
It's just too hard. Any change you make to the pr
Read the rest
icing model means refactoring not just the entire product, but sometimes the entire company. The path of least resistance leads to a place where there's no single source of truth, and changes anywhere require changes everywhere.After over 50 or so customer conversations and user research chats, this represents our third or fourth implementation (depending on how you count them), and our conception of how best to solve it has been refined and adjusted along the way.
The concept of "PriceOps" came out of those conversations, looking at where mature companies end up after several expensive rounds of iterating on how they implement their prices for flexibility and order. https://priceops.org
What we're releasing now is an open source tool you can use to set up your Stripe system that keeps everything organized around a single source of truth. With this, changes to your pricing model don't require changes to your application code or business processes.
As a bonus, I think it's actually easier to integrate with than integrating with Stripe the "normal" way. Use the identifiers for your customers and features that you already have. Define plans and subscribe customers to them. No ever-growing pile of object ids to manage.
If you are just starting to think about adding pricing to your product, or if you've built something custom but would like something less maintenance intensive, then please give Tier a try and we'd love your feedback.