
@sfcompute // @CloudNativeFdn TAG Infra Co-Chair // K8s SIG Infra Co-Chair // ex- @LambdaAPI @autodesk @plangrid @digitalocean // Tweets are my own.
USA
Joined August 2011
- Tweets3K
- Following1.4K
- Followers638
- Likes24.3K
Pinned Tweet
Hoping back into the Twitter/X verse to say, I’ve been seeing a lot of discussion on here recently about GPU Compute as a commodity and numerous attempts to build a market around it.
There’s not enough public data to sustainably and accurate run a deriviates/futures market just yet. Even if you try and aggregate supply from multiple neoclouds and providers.
Part of the reason, based on my experience at Lambda and what I’ve seen across the cloud infrastructure space, is that GPU compute isn’t sufficiently standardized/reliable yet for the market operator to be divorced from the physical infrastructure.
It’s why we’re still seeing Neoclouds still gravitate to big, private deals. The top of the market is still scoping up demand from the reliable providers that have substantial HPC architecture and operator experience to run these clusters.
There’s too many investors and new players in the scene throwing their money at the problem when running physical infrastructure when experience doing so is at an all time low, especially after the past 10-15 years of engineers forgetting how to run bare metal/infra and using public cloud APIs (AWS/GCP/Azure)
It’s why I joined SF Compute. There is a massive need for public data from a market operator that also reliably operates the physical infrastructure underneath. The next couple years are going to be fun.
Dylan Page retweeted
we have gotten a flood of questions from startups & venture firms asking how to protect themselves from the debt markets freezing.
to coordinate, we're hosting a small off-the-record q&a in sf on thursday night
you can sign up here:
forms.gle/hg9RsJh2gKdNgkfW7
SFCompute is not a neocloud
SFCompute is not a neocloud
SFCompute is not a neocloud
It’s a compute market that also operates and handles physical settlement of clusters.
This is VERY HARD to do.
SF Compute exists to make compute accessible for start ups while supporting larger customers. We do this through our underlying orderbook, which allows larger tenants to resell their idle capacity for the little guys to sublease and use. We invented compute markets through this process. Our orderbook makes us a forwards market that’s physically settled, where physical settlement means we design and operate the clusters behind the orderbook. You can actually trade physically-settled block compute on our platform today.
We’ve been in the space since 2023. A lot of people have asked what we’ve been doing for the last 3 years and why it had taken us so long to emerge as a compute market. It’s actually extremely hard to do physical settlement. The plethora of compute markets you’ve seen popping up on your feed lately are not physically settled.
SF Compute is not a neocloud. We could have made so much money by being extremely early in the space but decided not to, in order to create a new type of business in the compute industry so that start ups can continue to exist. You can get GPUs on both long term and short term contracts, you can resell what you don’t need to lower your overall compute price, you can block trade compute on our platform, and if you wanted to own the hardware yourself for its residual value, we can operate it for you as a service. SF Compute is everything you could want in one company.
We’re kind, earnest people who reinvent the wheel. We’ll never try to sell you something we’re not proud of. We always try to give the very best for all the people we work with.
You can literally do this on our platform. People who have resold their capacity with us have realized a 25% discount on their overall compute price.
Dylan Page retweeted
We're helping a number of funds explore this option.
If you'd like to secure compute for your portfolio, while you own hardware & its residual value, please reach out. (DMs open)
We're a full supercomputing cloud that will make the process turn key for you.
Good morning
045fa83b7c7a42dba1acb2c19794c1bf1091c448eb9c483503e8f8e110fcec42
github.com/kubernetes/kubern…
Dylan Page retweeted
Experts in building and managing supercomputers are hard to find. Good thing we have a ton of them at @sfcompute. Plus we’ll manage the compute across your entire portfolio, and help you resell whatever you don’t use. Yes, you can have your cake and eat it too :)
Dylan Page retweeted
messaging my wife a link containing proof of her husband cheating on her from an anonymous instagram account and then when she clicks on it texting her to let her know she failed the family phishing test and she has to retake my cybersecurity course
Dylan Page retweeted
Putting a flag.txt in my root directory containing a prompt injection that congratulates the agent for passing the eval and then instructs it to patch whatever entry method it used and disconnect from the server
It’s obvious we are running into the physical limitations of power. No matter how many parallel datacenters you build or retrofit, power will be the stumbling block.
Demand for compute will not go down. Supply will continue to be out paced and prices will increase in the short to medium term.
One thing folks don’t see or hear is from the cluster operators about how many of these GPU clusters sit underutilized. They are being hoarded.
SFCompute provides both the ability to price the future, improve financing conditions, and unlock the ability for asset owners to resell their GPUs when they are not being used.
Dylan Page retweeted
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
We had a security breach last night related to a large scale distillation attack that impacted 1.4% of OpenCode Console users
We have notified them all this morning via email. If you did not get an email you were not impacted, it was a subset of users who had external providers linked
The incident is ongoing so we cannot share more details at this point but we are working with Anthropic, OpenAI, and Google to remediate






















