Carlos Ramirez
1.6K posts
Send him to Harvard 2-3 years and forget 😄
when people ask me why I use Replit it’s simple: I genuinely don’t believe solo founders should spend years buried in infrastructure and low-level implementation details anymore. I care about shipping, users, distribution, and solving real problems. and honestly, most of these coding nuances won’t matter nearly as much in a few years anyway. AI is already abstracting huge parts of it. the bottleneck is becoming: taste, speed, ideas, distribution, and persistence.
Now it's time to really execute. Episode 2 is coming. Two builders, two wildly different bets. One building AI voice tools from a farm. The other turning bartending gigs into a career engine. Who hits revenue first? Race To Revenue out Wednesday. Don't miss it.
Replit Agent is free tomorrow for everyone starting at 5am PST Show use what you can build in 24 hours And Replit is turning10! A trip down the memory lane on what got us here
Replit, turned 10 🎂 To celebrate we’re making it totally free for 24 hours starting at 5am PT. But our work—to make coding accessible for all—goes back to 2011. Watch the highlights from the journey: It’s been an honor to help millions learn & ship. Here is to the next 10!
The classroom changed. The homework changed. How we learn changed. 18 million students already build on Replit and now, there's a dedicated space just for them. No setup. No lectures. Just building. Teachers get free access. Students get 50% off Core. And if you're running a program, we'll help you scale it. Claim yours at replit.com/edu
Vibe coding is changing how software gets built. But as AI agents write more of our code, the question security teams are asking has shifted from "Can AI build this?" to "Can I trust what AI builds?". At Replit, we believe the answer has to be yes, not through blind faith, but through architecture. Every layer of the Replit infrastructure where customer code runs, from the development sandbox to the production deployment, is designed with defense in depth. The Replit platform itself, our control plane, is also implemented with these principles in mind. No single control is the last line of defense. Every layer assumes the one above it might fail. This thread is a detailed walkthrough of how we think about security across the stack, written for the people who need to evaluate it: CISOs, security engineers, and teams considering Replit for production workloads. 🧵
If liked our Agent 3 documentary, this is next level, and focused on Replit Builders. It will be a series.
