Hacker News Reader

This came up two months ago, the pricing was described as "insidious." [1]

I replied that this description could be extended to include how it generated and associated unique customer IDs. The way it is built now-a-days it is trying to be the central key for SaaS user accounts. Effectively: store all your user data with us.

I thought it was some kind of oversight but it is most likely about lock in.

[1] https://news.ycombinator.com/item?id=33269824

View on HN

I am the original commenter you had replied to.

I am actually working on https://tier.run in part to help create a clean separation of interests between billing (and entitlement, and metering, and feature flagging) systems and how you store and access application and user data.

With Tier we have `tier whois` [1] which lets you get the Stripe Customer ID based on your own userId.

I'd love your feedback if you think there are improvements we could make.

1: https://www.tier.run/docs/cli/whois/

Reply on news.ycombinator.com