It's hard for me to trust a site that looks like a cryptic design portfolio from the early 2000s.
Code Storage by the Pierre Computer Company
31–40 of 46 posts
Re: Code Storage by the Pierre Computer Company
#32Hey 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 Githu…
I've been look for a way to use Git for smaller, high volume document storage - think something like Google docs where every doc is a repo and every change is a commit - but also, where the vast majority of docs age out and are effectively archived and not used, but still need to be available.
This looks like it technically, I just wonder how well the pricing scales for that case of docs that might never be read again...
Re: Code Storage by the Pierre Computer Company
#33It'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
there are numerous inconsistencies and broken links
The link text that says they raised $23M but doesn't go anywhere is real sus
Re: Code Storage by the Pierre Computer Company
#34"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.
They are a no way for me, especially the network fees
Re: Code Storage by the Pierre Computer Company
#35And agreed with other commenters about better explaining what this is - some examples and use cases side by side with the alternatives would work.
Re: Code Storage by the Pierre Computer Company
#36>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.
Re: Code Storage by the Pierre Computer Company
#37Hey 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 Githu…
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.
Re: Code Storage by the Pierre Computer Company
#38Earlier quoted context omitted.
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. performa…
Re: Code Storage by the Pierre Computer Company
#39Hey 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 Githu…
Wow, this looks potentially amazing! I've been look for a way to use Git for smaller, high volume document storage - think something like Google docs where every doc is a repo and every change is a commit - but also, where the vast majority of docs age out and are effectively archived and not used, but still need to be available. This looks like it technically, I just wonder how well the pricing scales for that case…
Re: Code Storage by the Pierre Computer Company
#40Hey 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 Githu…
Wow, this looks potentially amazing! I've been look for a way to use Git for smaller, high volume document storage - think something like Google docs where every doc is a repo and every change is a commit - but also, where the vast majority of docs age out and are effectively archived and not used, but still need to be available. This looks like it technically, I just wonder how well the pricing scales for that case…
We have folks using us to back crms, design tools, and all kinds of "non-code" stuff.
Please reach out - would love to connect!