Builder & Investor. Early backer @Lovable @Etched @Modal more+ Blessed by time @Firestreakvc @SpaceX @NASAJPL

Joined March 2009
Amir Rustamzadeh retweeted
Over the past few months, my team and I have been building Blatent Struct. Today, we’re launching it. The idea was simple: an LLM should be fast, cheap and accurate. Of course, who doesn’t want that? But we also wanted to go beyond structured outputs and let you program the business logic that governs the answer. Structured outputs already let you constrain the JSON labels you get back. We wanted to express how fields depend on one another, what to loop over from the input or application state, and which paths the user’s permissions allow. With Struct, you define conditions, switch cases and loops, alongside constraints from OAuth scopes and OPA policies. Those rules are enforced during inference. Earlier decisions constrain what can come next, all within a single API call. So you can work through large trees of dependent decisions and get the complete JSON object back, without your application having to coordinate each step through separate model calls. The aim is dependable endpoints you can call throughout your software, with very little overhead. In our benchmarks, Struct achieves comparable accuracy to Claude Sonnet 5.5 at 11× the speed and over 100× lower estimated cost. It’s also over 2× faster than Jev, with higher average accuracy across 20 benchmarks. Across six extraction benchmarks, it scored 87.5% against Cloudflare Clairic’s 81.7%, at 62% lower estimated cost. I’m really proud of what our engineers and the wider team have built, and grateful to our investors and everyone who backed us. I hope you like it. I’m looking forward to seeing what you build. If you have questions, please reach out. It's free to get started (very cheap thereafter) and you can have 100m tokens on us :) My co-founder @R_Pisarczyk made an overview video here: xitter.cf/R_Pisarczyk/status/211… blatent.ai
Very excited to finally share what we've been building! Today, we are launching Blatent Struct, our first language model. 🚀 One thing that's always bothered us about building with LLMs is how much engineering you need around the model. Getting an answer is one thing. Making sure it follows the right decision path, returns everything your application needs and doesn't break your business rules is another. We wanted to change that. Struct brings programmability to language models. You can define complex, cascading decisions, conditional dependencies and exactly what each outcome must satisfy. You can also enforce business rules and permissions during inference. And rather than stitching together multiple model calls, Struct can handle the whole decision tree in a single run. We also spent a lot of time making sure this doesn't come at the expense of performance. In our benchmarks, Struct achieves comparable accuracy to Claude Sonnet 5.5, at 11× the speed and over 100× lower estimated cost. It's also over 2× faster than Jev, with higher average accuracy across 20 benchmarks. And on source-grounded extraction, it outperforms Cloudflare Clairic (87.5% vs. 81.7% across six benchmarks), at 62% lower estimated cost. For me, the exciting part is what this enables: everything from document processing and customer support to agents that can make complex decisions while respecting the rules you've set. This is just our first model, and there's a lot more to come. I'd love for you to give it a try and tell us what you think. We're especially keen to hear what works, what doesn't and what you'd like us to build next. 🚀 Get started for free (up to 100m input tokens are on us) : blatent.ai
6
5
1
17
561
Amir Rustamzadeh retweeted
Congrats to the whole team on the launch and super excited to have @daytonaio power @GoEntire’s new primitive- Trails 🔥
Agents reinvented how we produce code. It changed our tools and half of our workflow. It’s time for the other half to catch up. Today, we’re shipping Entire: the Git forge for agent-human collaboration. We’ve built @GoEntire using Entire. Now we want to see what you'll build with it. Here’s why and what’s different. 🧵
4
5
64
4,750
Amir Rustamzadeh retweeted
This means compute futures are about to EXPLODE. My prediction, Nvidia B300 1-year reservations will go for $9/gpu/hr in March 2027. $7 dollars will feel like the cheap old days. Bookmark this. @ComputeDesk
Replying to @chamath
Pretty much. As of the past few weeks, debt markets have almost entirely shut off access to money for any company that doesn’t have substantial revenue independent of AI data centers. SpaceX closed $40B of debt for GPUs, but we’re investment grade and have Starlink & launch revenue. That means the 200+ neoclouds are going to see guppy-level death and consolidation. Some will make it through, but not many.
15
8
3
112
8,051
Meet up with Peter.
Going to be in SF tomorrow and have a few open slots. If we’re mutuals or you’re building something great in dev tools or AI, hmu!
1
115
Amir Rustamzadeh retweeted
We just raised a $60M Series B at a $1B valuation to build @daytonaio into the Agent Cloud. @FirstMarkCap led the round, with all key existing investors and angels doubling down. We're also thrilled to welcome the founders of some generational companies aboard, including @patrickc (Stripe), @tobi (Shopify), @AravSrinivas (Perplexity), @BrendanFoody (Mercor), @oliveur (Datadog), @adamdangelo (Quora) and @ericsyuan (Zoom) We're a 35-person team. But that's about to change; we're hiring across the board, and we'd love for you to join us.
456
201
151
1,401
274,056
Amir Rustamzadeh retweeted
Previously, to build realtime apps you've needed some sort of special sync system. With Neon Realtime you now get realtime reactivity built directly into Postgres.
Neon now has realtime, built by the team behind Electric. Turn any SQL query into a live query, joins and aggregates included. All inside Postgres, and ready for agents. It’s in public beta and available in all Neon plans. Give it a try and tell us what you think!
4
6
4
72
7,685
Amir Rustamzadeh retweeted
In early 2022, the first “real” @modal user was using us for processing large scale weather data. We were anxious about going up to them and asking them to pay ~$500 for continuing to run these jobs. (We thought it was a lot!) Obviously the numbers are much bigger now. But we’ve also built so much more since then, and our velocity and ambition are growing even faster. This year, we figured out how to scale to millions of concurrent sandboxes, launch RDMA clusters securely and elastically for distributed training, train state of the art speculators for inference, build a whole new sandbox runtime, and more. So many great rabbit holes, and we’re going deeper down all of them. If this sounds interesting to you, we’re hiring! modal.jobs
Today we're announcing that Modal has crossed $1B in annualized run rate, as well as raised a $750M Series D at a $15.75B valuation, led by @Accel. Since our Series C, usage has tripled and we’ve grown more than 15x year-over-year. We are deeply grateful to the developers and companies building on Modal. There's still so much more to build, and we can't think of a better time to be building software.
41
26
6
412
25,370
Amir Rustamzadeh retweeted
Today we're announcing that Modal has crossed $1B in annualized run rate, as well as raised a $750M Series D at a $15.75B valuation, led by @Accel. Since our Series C, usage has tripled and we’ve grown more than 15x year-over-year. We are deeply grateful to the developers and companies building on Modal. There's still so much more to build, and we can't think of a better time to be building software.
86
106
112
1,245
325,395
Amir Rustamzadeh retweeted
There's a misconception: "a big compute market doesn’t imply a big hedge market. [...] a lot of capacity is locked into fixed-price deals." The entire compute market today is *FULLY* hedged. Fixed-price deals ARE the hedge. But, it's a horrible *full* hedge. Compute derivatives will replace the "offtakes" with instruments allowing a finer-grained control over risk. Sellers hate offtakes, because they want to get better rates on riskier shorter-term rentals. Buyers also hate them, because they want flexibility. Compute derivatives allow more risktaking and more flexibility. The reason there's a compute shortage is that risk-taking and speculation is not possible. This is otherwise a fantastic article, thanks for the @ComputeDesk mention.
When your X feed is all compute and commodities, it's time to put that Series 3 to use. My latest Power Bytes, Future(s) of Compute is my take on whether compute futures can do what commodity markets were designed to do. 🧵
6
5
3
62
31,391
Supabase Select 2026 Recap: ◆ we acquired Turso - big plans ◆ Supabase Compute ◆ Declarative Schemas 2.0 ◆ Local dev without Docker ◆ Notebooks ◆ MCP Elicitations ◆ Scoped PATs ◆ OrioleDB in Beta ◆ Multigres open sourced more in here → supabase.com/blog/supabase-s…
19
12
147
8,168
Amir Rustamzadeh retweeted
Team @Mentlio built a great yc startup, pinged me and then got acquired. You can too xitter.cf/maddiehfaulkner/status…
Factory has acquired @Mentlio
3
1
39
1,833
Amir Rustamzadeh retweeted
"Once upon a time there used to be hyperscalers". I cover @ComputeDesk, our compute indexes (incl. $DESKH100), the wheeler dealer compute traders making millions, and the inevitable consequences of compute capital markets. Along with my friend @BrettHarrison of @Architect_Fi .
NEW POD We Cover – Compute still trades in group chats – Why finding GPUs takes so long – Paying 2x to skip the queue – Why compute futures > perps – What’s really bottlenecking AI? @BrettHarrison @andrawesbahou @JasonYanowitz TIMESTAMPS: 00:00 Intro 00:59 Why Does Compute Need Markets? 08:53 Compute Still Trades In Group Chats 13:38 Why Finding GPUs Takes So Long 19:21 How Much Compute Should You Buy? 26:58 Why Are Compute Prices Rising? 33:27 Can Architect Take On CME? 38:13 How Do You Hedge Compute? 43:08 The Risks Behind GPU Lending 52:08 What Really Constrains The AI Market? 01:02:08 What Is Everyone Missing About Compute?
3
7
2
39
2,921
Replying to @supabase
@supabase has acquired @tursodatabase i'm been a huge fan of the team and what they've built. we have big plans together. more to share in our keynote in a few hours this is the tweet that convinced us they'll fit right in xitter.cf/glcst/status/209307402…
Yesterday I had a call with Bryan Johnson and shared with him our roadmap for Turso for FY26 and FY27. Today, he posts this. A coincidence? We'll never know.
66
75
58
807
178,272
Amir Rustamzadeh retweeted
Turso is joining @supabase. Together, we're building the database platform for the agentic era: everything agents need, from lightweight databases to Postgres at petabyte scale. More details in thread. 👇
135
180
180
1,757
244,021
Amir Rustamzadeh retweeted
Introducing Qodo 3.0: the quality and governance layer for the software factory. Engineering teams are building agentic software factories. Output is up, but code review hasn't kept up. And a factory with no quality control is just a faster way to ship defects. Qodo 3.0 governs your software factory from the first line an agent writes through review and into production. Instead of individual PRs, group your code into work packages as connected changes across repos. Reviewed, ranked, and measured together, with a clear map of impact.
34
15
16
94
414,880
Amir Rustamzadeh retweeted
We’re announcing our alliance with @EYnews, strengthening our conviction that the businesses who win will be those that best understand outcomes before they occur.
2
13
39
2,192
Amir Rustamzadeh retweeted
Edge Compute running globally with 9ms cold starts on average is a really amazing feat of engineering. Here's how our team rearchitected our Edge Functions from the ground up for better performance, more flexibility and operational resilience. netlify.com/blog/edge-functi…
1
2
26
1,610
Amir Rustamzadeh retweeted
Oren Yomtov of Accomplish AI found two separate ways out of OpenAI Codex's sandbox this year, disclosed September 20. One read an auth token straight out of a shared V8 heap to impersonate a trusted process. The other abused a patch tool to write outside its own directory and append commands to a shell config file. Different bugs, same root cause: the thing enforcing the sandbox was running inside the sandbox it was supposed to contain. Containers don't contain, and isolates don't isolate. This is the same failure mode wearing different clothes, whether it's a process boundary, a V8 isolate, or a container runtime. Every session on our platform gets its own microVM with hardware-level isolation and its own kernel, not a shared one. When a workload needs to execute commands or touch the filesystem, that goes through our *Plugin API* over an authenticated endpoint, not as code the workload can reach into directly. 🔗 Full story here: bleepingcomputer.com/news/se…
1
3
335