Live data from Hacker News

Stripe Projects: Provision and manage services from the CLI

projects.dev

11–20 of 34 posts

Re: Stripe Projects: Provision and manage services from the CLI

#11
In the era of enshittification I can't really see the logic in tying a bunch of your infrastructure/services to the likes of stripe.

Then again I also don't see the logic in asking spicy autocomplete to write code or provision services for you either.

Maybe I'm just not the target market. I guess if you're spinning up 5 new toy todo list apps a week to show off how well you can talk to a predictive text engine maybe this is actually useful.

Re: Stripe Projects: Provision and manage services from the CLI

#12

In the era of enshittification I can't really see the logic in tying a bunch of your infrastructure/services to the likes of stripe. Then again I also don't see the logic in asking spicy autocomplete to write code or provision services for you either. Maybe I'm just not the target market. I guess if you're spinning up 5 new toy todo list apps a week to show off how well you can talk to a predictive text engine maybe…

It probably also doesn't make much sense to me because I see external services as something to use when we have to, not as default choice.

When your application runs on VMs you control and just uses a payment gateway and an email gateway it's hardly a challenge to get the services setup.

Re: Stripe Projects: Provision and manage services from the CLI

#13
I think this is smart and very interesting. I see it like an aggregator marketplace. A powerful position to be in.

Cloudflare, GitHub (if they shipped more), Anthropic and OpenAI are also in decent positions to do this.

I wrote notes on this previously [1]. If you believe agents are going to be big consumers, it's helpful to make things that today allow users of agents to easily discover and purchase services via apis.

[1]: https://x.com/chrisbarber/status/2026331038994321898

Re: Stripe Projects: Provision and manage services from the CLI

#14

Creating accounts and managing billing across multiple platforms is a real pain. This is a good solution, but I’m wondering if this should be more like an open standard that platforms implement, with Stripe providing a way for platforms to charge and optionally for users to pay (in addition to credit cards, wallets like Tempo, etc) Use cases: create accounts, set up billing, manage secrets, manage resources, get invo…

[dead]

Re: Stripe Projects: Provision and manage services from the CLI

#18

I personally think stuff like this should be made as protocols and done in the open instead

Stripe's valuation depends on this implementation mechanism, capturing the platform as an economic intermediary versus championing open protocols.

https://www.forbes.com/sites/jeffkauflin/2026/03/17/why-an-u...

(TLDR Stripe's valuation [$159B] is ~5x Adyen's [which is public, allowing for use as a comp] for somewhat similar payment volumes [$1.9T vs $1.6T, respectively], so Stripe is trying to grow into the valuation current fundamentals do not support)

Re: Stripe Projects: Provision and manage services from the CLI

#20
post #3

Nice idea, but I'd love a more open approach to this (or more support for OpenTofu / Terraform). This is just another vendor-locked-in way and might only work with selected platforms. Stripe has the incentive to add platforms that use Stripe as a payment processor so they can cash on the payment fees, they don't really have any incentive to add a platform that doesn't bring money to them (except affiliates are possib…

Exactly. The marketing makes this look like something general for deploying cloud stacks.

But what it seems to be is just a fast way to deploy resources to platform providers that use Stripe to bill you?

Or maybe the marketing is just confusing?

I don’t think this is for me though. I’m using things like AWS, Azure, and dedicated servers from companies that lease out dedicated servers. For my company Stripe is nothing more than a payment processor.

Post reply on HN