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 jacob@pierre.co
It would be nice to see a side-by-side comparison with Github on pricing and features. We are using github and creating hundreds of repos everyday without any issues (except for the occassional API outages that Github has). Curious to see your take on where Pierre is better.
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.
Why is that? Personally I appreciated the throwback look and it probably accomplished its goal of being memorable. Turbopuffer is another notable one seemingly leaning into this flavor of marketing
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)
We're actually meant to be less of a consumer product than i think you mean by this (but i may have misunderstood).
We're more targeting enterprise as storage infrastructure provider – selling directly to platforms who generate a bunch of code and need a place to put it.
There's probably still going to be a box of hard drives in a datacenter somewhere, it does make sense to have a layer to manage the agent interface, rather than letting agents completely loose on all your storage.
Agreed, but I'm making a distinction between the platform (whether it be Cloudflare Moltworker or a Mac Mini), which a human chooses for the agent to run on (for now), and tools designed to be discovered and consumed by the agents themselves (e.g. code.storage, AgentMail).
pretty much - low friction git* repos for massively parallelized agentic use.
(can think of it kinda like what stripe does for payments… headless git infra, where you get an api key, and store / create as many repos as your customers need).
3 years ago we started building a direct competitor to GitHub with the theory that you need to build code storage, code review and CI to truly compete.
We spent about a year prototyping this all out, raised some money, and then started building this for real [tm].
Code storage felt like a HUGE moat for GitHub. Most of our competitors in the code review space:
- graphite
- linear
- (now cognition)
- etc
All built directly on GitHub's apis – but we wanted to go down to the metal (something wrong with us).
A year and half into doing this, a few folks reached out and asked how we were scaling git… i waved my hands around a bunch and explained how hard of a distributed systems problem scaling git was… explained git three-phase commits, etc.
Fast forward a few more months, and we started standing up single tenant clusters of our infra for a few different codegen companies that also needed storage solutions.
sadge, thoughts on when live? This is very good idea I can even imagine right now how good it could feel, if it's what I expect, that will be very good.
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 jacob@pierre.co
It would be nice to see a side-by-side comparison with Github on pricing and features. We are using github and creating hundreds of repos everyday without any issues (except for the occassional API outages that Github has). Curious to see your take on where Pierre is better.
To be fair to GitHub (which i have a lot of love and respect for), we're building very different products.
GitHub is a social consumer coding product first. There's user models, review and discussion primitives, ci, etc.
Code Storage is just a headless, api-first infra product. No users, no review primitives, no rate limits, etc.
Our company is obsessively focused on only 3 things:
1. reliability at scale 2. performance 3. code api surface
happy to dive into any of these in more detail if you want to shoot me over an email jacob@pierre.co
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.
thanks for the feedback – we definitely have work to do on communicating what we're up to.
Sorry about the audio - will get that patched
"git init --bare" as a service what a time to be alive
And it only costs $30K per year for a single terabyte of usable (NVMe?) storage. The value!
$1 GiB/month x 3 minimum replicas x 1024 GiB x 12 months
And according to the status page they only have CDNs in us-east and eu-central.
If youre not fishing for AI backed VC tricklnomics, do you even deserve to call yourself a programmer
It's hard for me to trust a site that looks like a cryptic design portfolio from the early 2000s.
Why is that? Personally I appreciated the throwback look and it probably accomplished its goal of being memorable. Turbopuffer is another notable one seemingly leaning into this flavor of marketing
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)
We're actually meant to be less of a consumer product than i think you mean by this (but i may have misunderstood).
We're more targeting enterprise as storage infrastructure provider – selling directly to platforms who generate a bunch of code and need a place to put it.
end users wont really know we exist.
There's probably still going to be a box of hard drives in a datacenter somewhere, it does make sense to have a layer to manage the agent interface, rather than letting agents completely loose on all your storage.
Agreed, but I'm making a distinction between the platform (whether it be Cloudflare Moltworker or a Mac Mini), which a human chooses for the agent to run on (for now), and tools designed to be discovered and consumed by the agents themselves (e.g. code.storage, AgentMail).
maybe i'm too stupid but i dont have a clue what this is
low friction github repos for massively parallelized agentic use. which may also be ephemeral.
pretty much - low friction git* repos for massively parallelized agentic use.
(can think of it kinda like what stripe does for payments… headless git infra, where you get an api key, and store / create as many repos as your customers need).
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?
Ahh good question…
Here's the timeline if you're interested.
3 years ago we started building a direct competitor to GitHub with the theory that you need to build code storage, code review and CI to truly compete.
We spent about a year prototyping this all out, raised some money, and then started building this for real [tm].
Code storage felt like a HUGE moat for GitHub. Most of our competitors in the code review space:
- graphite - linear - (now cognition) - etc
All built directly on GitHub's apis – but we wanted to go down to the metal (something wrong with us).
A year and half into doing this, a few folks reached out and asked how we were scaling git… i waved my hands around a bunch and explained how hard of a distributed systems problem scaling git was… explained git three-phase commits, etc.
Fast forward a few more months, and we started standing up single tenant clusters of our infra for a few different codegen companies that also needed storage solutions.
And now here we are :)
probably ai became the bigger opportunity
Keep trying to sign up and get "Whoops, this email isn't allowed access. Try again." :( working for anyone else?
not open access yet, sorry :(
sadge, thoughts on when live? This is very good idea I can even imagine right now how good it could feel, if it's what I expect, that will be very good.
planning to share more in the next month or so :)
But have been slowly signing folks up – if you want to shoot me an email, can get you setup jacob@pierre.co
iirc like they pivoted from being a github replacement with their own vcs
tldr: automated git repos. yknow, like normal git but for AI, bro