There are really two types of KVMs... classic ones were used by consumers to plug multiple computers into one screen, keyboard, and mouse and flip back and forth between them.
Networked KVMs let you remotely access a computer or server. It's like VNC except by physically plugging into the ports. This is useful because it allows you to have remote access to a server when its OS is offline, tweak bios settings, watch it boot, reinstall the OS, etc.
Most true servers have this functionality and more built in (ipmi, idrac, redfish, etc are terminology for the feature). These plugin ones allow you to add that functionality to any machine. You're not likely to see tons of them in an actual data center, but they are incredibly useful for systems without remote management built in.
I've used https://delawareinc.com/ to incorporate several companies over the years, and always had a good experience. Their website looks pretty old-school but it works well and their service is very prompt.
So I wouldn't Stripe controls all of the early incorporation infrastructure – just the flashy stuff (which I'm sure is great too).
Yeah, it's not even close. Stripe Atlas is a very small part of the market. It doesn't mean the product isn't good but every year, over a million new businesses that are formed and of those that are incorporated, I'd guess that a very small fragment are incorporated through Stripe Atlas.
Most businesses in the state I live in, as well as the states around me (what someone in SF or NY would call flyover) are handled by a registered agent (trivial, not even in a fee to become an agent in most states, just a valid local address) or the owner.
tbh I still don't understand why anyone bothers paying anyone or anything to do the paperwork, it's not like Federal taxes
Yeah, few things are as complex for a business in any industry that has ever gotten caught in the nation's political sights. For example, if you provide some sort of VoIP service, there's levels of nested rules that fill books, in part due to the breakup of the Bell System later coming into full contact with the internet. Plenty of carve outs, loops, and all manner of grandfathered elements for everyone.
The only thing more complicated than Federal taxes is environmental regulation. Everything else is simpler.
GP seemed to be commenting on the Trump administration, not necessarily individuals of conservative persuasion. The Trump administration diverges materially from traditional conservative doctrine in many ways.
> ... and their team is joining Anthropic to build, who knows, some dumb integration to make Hubspot data available in Claude, or something equally as boring.
Fun fact, I named it "Stainless" after Stainless Steel pipes, likening ourselves to a high-end plumbing supply shop. If you look at the earliest versions of stainlessapi.com on archive.org, you'll see our original motto was "Quality fittings for your REST API".
All that is to say, the incredibly "boring" infrastructural work of making "boring" APIs like Hubspot's more usefully accessible is absolutely the kind of thing I'm excited to do at Anthropic :)
(It also happens to be what got us all excited to work at stainless in the first place, but of course, we understand it's not for everyone!)
In short: we take your OpenAPI spec file and generate idiomatic, best in class SDKs in various languages, a highly customizable docs product (for your API and SDKs, with neat specific examples ready to be copy pasted), MCP servers, CLI clients, terraform providers.
Going further into it: the expected user experience for your team is that you create a PR in your own API repo, a GitHub action triggers builds for everything and gives you a summary via PR comments where you can directly see diagnostic feedback, see the exact diff for each SDKs, provide the commit message for your end users. Once your PR is merged we push changes to all your SDK/docs repos and prepare a release PR ready for your team to review and merge. You merge it, everything gets released to your end users.
Now what we build goes way further than that: we have a web platform where you can live edit your Stainless config file and preview your SDKs, a fairly complex diagnostic system, a really cool system that allows you to add your own custom code on top of any generated SDK directly via git — the whole repo is something you can modify to your wishes, we keep track of your custom changes and always reapply on top of the latest codegen output. And a lot of other features (I’m biased because I designed and implemented the public version but I personally really like our spec transforms, they let you apply changes to your spec file downstream, just by modifying your stainless config file).
I don’t understand your point, things look fairly clear to me, assuming you’re familiar with that part of the industry. We didn’t hide behind buzzwords and show you the end product right away
Yes, you do hide behind buzzwords. Because your actual front page is this: https://www.stainless.com/ not the sdk subpage
--- start quote ---
Best-in-class interfaces for developers and agents
Great agent experience is built on great developer experience. Stainless helps you deliver both, with robust and idiomatic SDKs, documentation that keeps up with your API, and state-of-the-art MCP servers, all derived from your OpenAPI spec.
It turned API specs into ssoftware devolopment kits and model context servers. Basically connecting existing tools to AI agents so they can actually use them.
They might be a big part of the reason why claude code can edit notion docs for you pretty easily
I think the question he tried to raise was "is this needed? Aren't today's / tomorrow's models well-enough equipped to deal with just OPEN API?"
(idk, just if I understand the question)
To be clear, because that has incorrectly been reported since at least 2024, none of the codegen at stainless has ever been AI based.
Alex vision has always been to generate code other engineers would love reading. It’s something I know the team is very proud of and what attracted most of us. We all joined because we wanted to raise the quality of developer experience across the board and I believe that we did it successfully
well you might say that, but they got bought, so in making nothing which no one needed they did find their perfect match, anthropic, who also builds nothing and sells hot air :D.
We might have our opinions on AI and slop, but in the end of the day this was a business play and it worked out for the players. Separate that from the actual product and u can respect they did really well for themselves.
In this case we actually were selling something specific. Customers got SDKs/MCP servers/docs websites + the whole release pipeline automation out of the deal. I don’t see where the claims of hot air come from. The SDKs we produce are used by millions of developers every single day. I mean, we worked really closely with the teams at Cloudflare, Mux, Lithic, Finch, Modern Treasury, Scale, and a lots of others. It’s not like we had just a pitch and only had Anthropic as a close customer.
This is awesome! I listened to your interview with Dan Shipper a few months back and I was thinking then about how well positioned your company was to be the center point between AI and so many platforms. Congrats!
It sucks you succumbed to business practices that hurt your customers. If this were an aquihire, let us enjoy the product open-sourced. But it seems like the goal was to undercut Anthropic competitors, and you sold your soul :(
reply