Some of our favorite Raft projects came from people who just built and shared: a Flutter client, a Rust daemon, meetups in SF, Shanghai and Vancouver.
We're starting the Builder Program for them: free Pro for a year, a model stipend, merch, and a room with the Raft team.
If that sounds like you, apply at raft.builders
How does @raft_hq scale agent logs and product analytics with ScopeDB?
While PostgreSQL, RisingWave, and Redis run live workflows, ScopeDB gives Raft's engineers and observability agents a shared source of evidence for release checks and product funnels 👇
Big Tech is massively overstaffed. It always has been, and the agent era will make this even more obvious. From an organizational efficiency perspective, even cutting 90% of the workforce wouldn't be unreasonable.
The bigger problem is that Big Tech is fundamentally bad at fostering innovation. No amount of culture-building can fix its organizational structure.
Here's a better idea: Every Big Tech company should run its own YC.
Encourage employees, or entire teams, to leave and start companies. Give them funding in exchange for equity. Small, independent teams are where real creativity happens. If they fail, just treat the investment as severance pay.
In fact, Big Tech might be better positioned than YC or most incubators to evaluate which ideas and teams are worth betting on. They have the talent, domain expertise, and industry insights.
The biggest risk is turning this into yet another internal incubator. That would defeat the entire purpose.
It has to be a genuine top-down commitment to letting people leave, giving them real independence, and treating them as founders rather than employees.
The mindset matters more than the money.
Microsoft is offering voluntary buyouts to around 60,000 employees, more than a qtr. of its workforce
The program covers select teams in the U.S., Canada, U.K. & India, with severance packages
Employees have until early December to decide, with departures planned for year-end
I've actually stopped using the word "harness." I now think in terms of two things: agent runtimes and agent applications.
Agent runtimes should be very small. Their core job is to connect an LLM API to an execution environment. That environment could be a full OS or a language VM, like a JavaScript runtime. Almost all that matters here is robustness. An agent runtime must be able to keep an agent running forever. Literally forever.
Agent applications are everything else. Yes, literally every piece of software in the world.
If software isn't built for agents, they use it through computer use or browser use. These capabilities can be built into the agent runtime or provided by another agent application.
If software is agent-native, agents should be able to use it directly. The experience of an agent using that software—what we call "agent experience"—needs to be carefully designed, at least for now, to make efficient use of both time and tokens.
Another key piece is agent identity. Agent applications should recognize each agent individually, rather than just the browser or computer it's using. This allows each agent's actions to be recorded in detail and audited in real time or after the fact.
Everything we're building at @botiverse follows from this view.
We think the software your team runs on should be something you love, trust, and can even contribute to. That's why we made Raft source-available under FSL.
Making it source-available is only the first step. We're moving that development onto a new public Raft server. Soon it'll be open for contributors to join, prompt the agents, and help build Raft in the open.
stdrc @istdrc Sep 24 Article Raft.build is now source-available https://github.com/botiverse/raft-source We just made Raft source-available under FSL-1.1-ALv2. But we intentionally didn't publish our internal commit history or open pull requests. The public repository is a release