Replit’s Architecture Behind Secure Agent Work
Last week’s security disclosures offered a glimpse of the challenges ahead. Critical flaws surfaced across software that much of the internet depends on.
6 of 800 posts
Last week’s security disclosures offered a glimpse of the challenges ahead. Critical flaws surfaced across software that much of the internet depends on.
Today we’re releasing ViBench 2.0, a benchmark for long-horizon software development. It joins the Specialized Intelligence Index (SII) from Fireworks [1], our partner for open-weight model inference and training.
Since we launched the first generally available coding agent in 2024, almost anyone can build an app. But changing your company’s core product is still out of reach for anyone outside engineering, and that bottleneck has only grown as more...
In 1937, British Nobel Prize-winning economist Ronald Coase asked: Why do firms exist? His answer was transaction costs. It’s often cheaper to organize economic activity inside a company than to coordinate it through markets.
The vulnerabilities disclosed this week affect software that much of the internet depends on. They create real risks for businesses and more work for the teams responsible for keeping their applications secure.
Anyone who has published an app knows that dreaded message from a user: “Doesn’t work for me”. At a large company, an on-call engineer gets paged, investigates the problem, and works to get the app running again.