Well this is kinda fun. Thanks for boosting my cred @Replit 🙏

We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity. This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.

AI has stopped being a feature and started being the foundation. We're excited about a new wave of startups rebuilding software, services, and silicon— and pushing AI into the physical world. ycombinator.com/rfs

We will ship again this week. Codex has achieved escape velocity and will keep improving rapidly.

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. 🧵

You can also easily add a mobile app to your project once imported. More details here: replit.com/mobile

We’ve invested deeply in security at Replit, including our recent launches with Security Agent Auto-Protect. If you want to move your app to Replit, we’re offering free app imports for a limited time. Bring your app over and keep building safely. Get started here: replit.com/free-import

Solo founders — how long is your app's feature list? Be honest? Is it an entire page of bullet points? If so, you're not alone. Almost every new founder starts with a list that could keep a ten-person team of full stack devs busy for a year. But it's also how most solo startups quietly die before they even launch. If it makes you feel any better, even established big tech companies do this (the "enshittification" of Facebook is the best and most common example). Don't be Facebook. Learn to practice the art of ruthlessly cutting features until your product truly fits your customer's pain. And don't fall into the trap of building a new feature because your cousin Dave thought your app was "cool" and said the feature is a must-have. Why? Because features are not free. They always have costs, but those costs often stay hidden. Every feature needs love. A feature doesn't just sit there, inert. Each one is a new thing to design, build, test, fix, debug, fix again, rework, debug again, fix again, and then explain to your user by rewriting the copy of your landing page. You don't have the time for that. Instead, use this test: if you take a feature away, does the product still solve the customer's pain? If so, cut it. A product with one to three frictionless core features beats a product with 15 features that are all "nice to have". Every. Single. Time. So be ruthless about your feature set.

Introducing Claude Design by Anthropic Labs: make prototypes, slides, and one-pagers by talking to Claude. Powered by Claude Opus 4.7, our most capable vision model. Available in research preview on the Pro, Max, Team, and Enterprise plans, rolling out throughout the day.

The solo founder disease nobody posts about: Building 5-10 different products in various states of near-completion. You know you should focus. But when you see a new problem, you start building a new app. Guilty as charged.

Second and third order effects of every app/website becoming an app store: 1. The 30% Apple and Google collected for decades gets distributed across millions of builders. The biggest wealth transfer in the history of software happens 2. Your data is now scattered across 500 micro apps. The person who aggregates it sells it back to you. 3. Microapps become a massive headache for IT because they aren’t approved and we all get addicted to them. 4. Data fragmentation gets so bad that the person with clean unified data about you becomes more valuable than any single app. 5. Physical retailers start shipping micro apps as part of the product. You buy the blender and get the app that runs it. 6. Insurance companies can't underwrite software liability anymore. Every app is a new unknown risk. 7. Software distribution becomes a real estate business. The platforms with existing eyeballs extract all the margin. 8. Doctors, lawyers, and accountants etc start competing on software 9. Micro apps expose how little most SaaS products actually do. Turns out you needed four features not four hundred and the incumbents cannot unbundle themselves fast enough. 10. Every niche industry gets its first real software. The dry cleaning industry, the fishing industry, the funeral industry. Sectors that enterprise software never touched. 11. The gap between knowing an industry and being able to build for it collapses. Domain experts become the most dangerous founders. 12. Lawyers start winning cases based on who has better micro apps 13. Micro apps make pricing transparency unavoidable. When anyone can rebuild your product in a weekend you cannot charge rent forever. 14. Kids who grow up now will never understand why you had to wait for a company to build what you needed.

Vibe coders are product managers who code

The best SaaS founders aren't SaaS founders. They're real estate brokers. Lawyers. Construction managers. Team leads who've sat through the same broken workflows for 10, 15, 20 years — and finally decided to do something about it. Their experience creates an execution advantage you can't buy or learn on Youtube: ➡️ Professional network = initial distribution ➡️ Domain expertise = content ➡️ Years of real experience = social proof ➡️ Deep industry knowledge = moat Everyone gets hyper-fixated on product. Because it's fun. But product is easy to build now — AI tools like @Replit and @AnthropicAI's Claude Code have collapsed the barrier to entry, just like @bubble did during the nocode boom. Distribution, marketing, and operations (i.e., building a real business, not just a Product Hunt launch) have always been the real problem. And niche founders with experience already have these. So, what's a painful workflow that you've dealt with forever? And why don't the tools you use solve it?

Did @claudeai just do an end-run around @openclaw? support.claude.com/en/articl…

Software was eaten by AI.

This is amazing.

Why is truly high quality UX/UI so difficult? You know it when you see it (@stripe, @linear, @NotionHQ, etc). But producing it is another thing entirely.

Most @OpenAI Codex content is still too technical for non-developers. So I made a guide to show you how to use Codex to do more with AI across GTM, sales, content, customer support, research, and operations without needing an engineering background. I’m using Codex on the $20/month ChatGPT plan, and after spending the past month testing it as a non-engineer, I’m convinced most people are still underestimating how practical it already is. What’s in the guide: - How to install and get started with Codex - How to set up your workspace, folders, and context - How to use and create skills - When to use local vs GitHub - How to use threads, handoff, and commit without getting confused - How to do research, write content, and run quality checks across your work - How to set up automations and use slash commands like fast mode and plan mode This is for creators, marketers, operators, sellers, support teams, and anyone who wants to do more with AI using Codex as a non-developer. I recorded the full walkthrough and put together a free repo with the templates, prompts, skills, and setup I use. I’ll drop the guide in the comments below. Bookmark this and send it to a friend 🙏🏽

After a conversation with my plumber yesterday, I'm announcing new standard hourly developer rates for taking on vibecoded projects: $100/hr . . . If I build it $150/hr . . . If you watch $200/hr . . . If you help $250/hr . . . If you already built it $300/hr . . . If you tell me how to build it

we are building auth for ai agents auth0.ai