Intersting concept. I just can't get my mind off one of the blurbs from the page
>Code Storage is designed for modern workloads: Vibe Coding platforms generating 1m+ new repos a day, AI copilots writing thousands of commits per session, teams branching and merging in real time, and apps syncing code across devices.
This is sort of a rant, skip if you must
Those 1m+ repos all have code no human has ever seen or will see. I'm afraid of being a luddite. But I can't believe we're taking vibe coding seriously, especially with these enterprise SaaS startups aimed at it. Abstractions have always come up but this is knowledge handover, this is knowledge reduction or destruction.
What happens to all of humanities greatest inventions when the current generation of developers die out? Who's going to maintain the basement? Where things haven't been abstracted? Who's learning at that level, who's keeping the knowledge alive when everyone's being told you just need to vibe instead of thinking logically?
I know why the push, people who never wanted to be developers, people who never wanted to code got into this for a paycheck or something else, they're welcoming this with both hands. I've seen people slowly lose their abilities they tried so hard to make.
I'm being fricking dramatic here all because of that blurb.
It's basically hosted Git infrastructure as an API service, aimed at AI coding platforms rather than human developers.
Took me a really long time to understand this. The blob thing is cool but otherwise it's a really confusing website. The audio playing without me wanting it was not cool though.
I have a suspicion most of these types of agent-targeted SaaS will die out once the human equivalents implement their agent layers / MCPs.
Agents having no way to pay for their use is one thing; lack of deep integration within the business domain is another (e.g. if you're a Git provider, you'd probably want to offer CI/CD, PR workflows, release management, publicly discoverable repos etc., and boom - you just copied GitHub)
So what benefit does the API layer give over just being able to use git directly?
And agreed with other commenters about better explaining what this is - some examples and use cases side by side with the alternatives would work.
It's hard for me to trust a site that looks like a cryptic design portfolio from the early 2000s.
I am still curious why they stopped offering their original service. What was the feedback from users? Why did developers not want to use it?
Keep trying to sign up and get "Whoops, this email isn't allowed access. Try again." :( working for anyone else?
iirc like they pivoted from being a github replacement with their own vcs
[dead]
tldr: automated git repos. yknow, like normal git but for AI, bro
Hey everyone,
Wow, you scooped us! we weren’t really expecting to launch here just yet, but happy to answer any questions y’all have :)
First, Pierre is building code storage for machines -- think GitHub’s infrastructure layer, but API-first and tuned for LLMs.
What does that actually mean? We’ve spent the last 18+ months speed running GitHubs infrastructure (with a lot of help from early GitHub folks)… this is Github’s spoke architecture with a few modern twists + object store for cold storage.
Up until this point, GitHub is the only team that’s built a truly scalable git cluster (gitlab, bitbucket, etc. are all enterprise plays, with different tradeoffs).
Code.Storage is meant to be massively scalable… and we’ll be doing a larger post on what that means, and the scale we’re already doing soon hopefully :)
On top of this, we’ve invested a TON of time into our API layer – we have all the things you’d expect, list files, create branch, commit, etc. – with some new api’s that agents have found helpful: grep, glob based archive, ephemeral branches (git namespaces), etc.
Right now we’re in private beta – but happy to do my best to answer any questions in the short term (and if you’re working on anything that might benefit from code storage or storing code like artifacts – please reach out to [email protected]