YC’s Fall 2026 RFS: All 13 Ideas, the Army Secretary in the Pitch Room, and the 5 Plays Indie Hackers Can Ship
Y Combinator’s Fall 2026 Request for Startups is out: 13 ideas, a sitting Army Secretary, and a July 27 deadline. Here are the 5 software plays indie hackers can ship.

Key Takeaways
- YC published its Fall 2026 Request for Startups this week — 13 ideas under the banner “AI is moving into the physical world” — days before the Fall batch application deadline of July 27 at 8pm PT. Every accepted company gets $500K on standard terms, with Demo Day set for December 2.
- For the first time, an RFS entry is authored by a sitting US government official: Army Secretary Daniel P. Driscoll, who wants founders building low-cost interceptors, sensors, drones, and resilient logistics for ground combat.
- After Summer’s hard-tech maximalism, the pendulum swung back: roughly 10 of the 13 ideas are software-first. But it’s not team SaaS — YC is asking for agent-native and personal software, from single-user clouds to self-healing API integrations.
- The five plays a tiny team can actually ship: A Cloud for Small Software, Self-Maintaining APIs, Multiplayer AI, AI-Native Compliance Infrastructure, and the software slice of AI for the Aging Population.
Y Combinator published its Fall 2026 Request for Startups this week, and it is the strangest, most revealing list YC has ever shipped. Thirteen ideas. The US Secretary of the Army wrote one of them. A YC partner wants data centers floating on the ocean. And sitting in the middle of all that steel, Pete Koomen is asking for the thing indie hackers have been building all along: a cloud for software with exactly one user. Applications for the Fall batch close July 27 at 8pm PT — days after the list dropped. Here is the full breakdown, the barbell thesis running through it, and the five plays a tiny team can actually ship.
What Changed Since the Summer 2026 RFS
The Summer 2026 RFS was hard-tech maximalism — 15 categories, 8 of them requiring serious capital: lunar manufacturing, inference silicon, counter-drone defense. Fall trims the list to 13 and quietly swings the pendulum back. By our count, roughly 10 of the 13 ideas are software-first. The banner thesis is still physical — “AI is moving into the physical world” is the opening line — but the physical asks got fewer and weirder (offshore compute flotillas, sensor data collected by robots and balloons), while the software asks got more specific and more shippable.
Two things in this list have never happened before. First, a sitting US government official authored an RFS entry: Army Secretary Daniel P. Driscoll wants founders building “low-cost interceptors,” next-gen sensors, drones, and resilient logistics for ground combat. Second, YC institutionally endorsed small software — not as a stepping stone to scale, but as the point. Koomen's category asks for infrastructure to deploy “purpose-built tools that will only ever have one or a small handful of users.” That is the micro-SaaS thesis, written into the wishlist of the world's most famous accelerator.
One pattern note: Max Kolysh has his name on two entries — AI for the Aging Population and Proving You're Human. Both are demographic bets: one on the age wave, one on the deepfake wave. When a partner doubles up, read it as conviction, the way Diana Hu's triple appearance signaled the agent-infra bet in Summer.
All 13 Fall 2026 RFS Ideas at a Glance
| # | Idea | Author | Bucket | Solo / Tiny-Team Fit |
|---|---|---|---|---|
| 1 | The Primer | Andrew Miklas | Consumer | Medium |
| 2 | The Future of American Defense | Daniel P. Driscoll, US Secretary of the Army | Hard tech | Very low |
| 3 | A Cloud for Small Software | Pete Koomen | Software | High |
| 4 | Multiplayer AI | Aaron Epstein | Software | High |
| 5 | Compute at Sea | Francois Chaubard | Hard tech | Very low |
| 6 | AI-Powered Consumer Products for 1 Billion People | Raphael Schaad | Consumer | Medium |
| 7 | AI for the Aging Population | Max Kolysh | Software | Medium |
| 8 | New Operating Systems for the Physical World | Charlie Warren | Software | Low |
| 9 | The Best Time to Build in Crypto | Nemil Dalal | Software | Medium |
| 10 | Data for the Real World | Austin Tindle & Diana Hu | Hard tech | Low |
| 11 | Proving You’re Human | Max Kolysh | Software | Medium |
| 12 | AI-Native Compliance Infrastructure | Daivik Goel | Software | High |
| 13 | Self-Maintaining APIs | Harsha Gaddipati | Software | High |
“Solo / Tiny-Team Fit” is our call, not YC's. We weight it on capex, regulatory load, hardware requirements, and time-to-first-revenue for a two-person team.
The Barbell: Warships on One End, Software for One on the Other
Put the 13 ideas side by side and a strange shape appears. On one end: interceptors for ground combat, data-center flotillas in international waters, robots and balloons collecting “dense physical-world data,” operating systems coordinating robots and human workers on job sites. Nation-scale, capital-heavy, physical. On the other end: a tutor for one child, a care companion for one aging parent, a cloud for software with one user, an agent that quietly fixes one broken API integration. Person-scale, capital-light, intimate.
What is missing is the middle — the horizontal, per-seat, team-collaboration SaaS that defined the last 15 years of startup formation. Not one of the 13 entries asks for it. That is the second consecutive RFS where classic team SaaS is essentially absent, and it confirms the thesis we flagged in April: software is now the substrate, not the moat. The defensible ends of the barbell are physics and regulation on one side, and personal context and distribution on the other. The undefended middle is where AI-assisted competitors clone you in a weekend.
The Driscoll entry deserves its own paragraph, because an RFS co-authored by the Secretary of the Army is not a content-marketing stunt — it is procurement policy showing up in a startup accelerator. “Warfare is at an inflection point, and the old ways of Army acquisition simply don't keep pace with modern threats,” Driscoll writes, calling for “hungry, innovative founders” to build commercially developed, modular systems. The Army has also launched xTechDisrupt, a pitch competition run with YC. For most Superframeworks readers this is not a category to build in — ITAR, clearances, and hardware gate it hard — but it is a loud signal that the US government now treats seed-stage startups as a real defense supply chain.
The 5 Plays Indie Hackers Can Actually Ship
Four ideas grade High on our tiny-team fit, plus one sleeper where the software slice is wide open. Each comes with a concrete read on what to build first.
1. A Cloud for Small Software (Pete Koomen)
Koomen's argument: agents have made writing personal software nearly free, but deploying and sharing it is still developer-grade work. He wants the gap closed — creating and sharing a purpose-built tool should be as easy as sharing a Google Doc. This is YC validating the micro-apps shift we covered in March: software with one user is no longer a toy category.
What to actually build
- The one-click home for agent-built tools. Paste the code your agent wrote (or connect Claude Code directly), get a running private tool with auth, storage, and backups handled. Charge $10–20/mo for a personal workspace of tools.
- The remix layer. Let people share a working tool the way they share a doc — recipient clicks, gets their own copy, tweaks it with natural language. Whoever owns the share-and-remix loop owns distribution for the whole category.
- Start with a niche, not a platform. “Small software for coaches” or “small software for landlords” beats a general cloud on day one — you can win a vertical's trust with 20 templates and expand from there.
2. Self-Maintaining APIs (Harsha Gaddipati)
Every developer knows this pain: a vendor ships a breaking change, and a thousand downstream integrations silently rot. Gaddipati wants agents that scan customer codebases, identify affected usages, and open a PR with the fix — APIs that maintain themselves. This is the most concretely scoped idea in the entire RFS, and a solo dev can prototype it in a weekend.
What to actually build
- A GitHub App that watches one ecosystem. Pick a high-churn API surface (Stripe, Shopify, or a fast-moving AI SDK), diff every changelog and OpenAPI spec, scan connected repos, and open the migration PR automatically. Charge per repo per month.
- Flip the buyer: sell to the API vendor. A platform that can say “ship the breaking change — we'll auto-migrate your customers” turns deprecations from support nightmares into a feature. Developer-experience teams have budget for exactly this.
- The trust bar is the product. Every PR must come with passing tests and a plain-English diff summary. Nail the first 100 auto-merges and word of mouth does your marketing.
3. Multiplayer AI (Aaron Epstein)
Epstein's observation: AI is still “mostly trapped in private chats, with agents working in sessions that teammates can't join or influence.” He wants teams dropping into shared live agent sessions — watching, redirecting, and handing off work the way they would with a human teammate. Every productivity category got its power-up when it went multiplayer; agents are next. It's the org-level answer to the lonely agent problem we wrote about in June.
What to actually build
- Figma-style presence for agent runs. A shared session viewer for Claude Code or Cursor runs: teammates watch the agent work, drop comments on steps, and redirect mid-run. Sell to the team lead who currently reviews agent output by screen-share.
- The handoff primitive. Build the “assign this agent session to Priya” button — with full context, permissions, and an audit trail. Start in one function (support escalations or sales follow-ups) where handoffs already have a rhythm.
- Approval gates as a service. Team-visible checkpoints (“agent wants to email the customer — approve?”) with one-tap approve from Slack. Small surface, immediate budget, and it rides every agent platform rather than competing with them.
4. AI-Native Compliance Infrastructure (Daivik Goel)
Goel wants the fragmented compliance stack — monitoring regulatory changes, flagging anomalies, generating reports — consolidated into AI-native infrastructure that reduces reliance on specialized headcount. Compliance is the rare market where the buyer is legally required to care, which is why we keep pointing founders at regulated verticals.
What to actually build
- Own one regime, not “compliance.” EU AI Act readiness for AI startups, HIPAA for digital health, or FinCEN rules for fintechs. An agent that watches the regulatory feed, diffs it against your policies, and drafts the remediation is a $500–2K/mo product.
- Be evidence-first where incumbents are checklist-first. Vanta and Drata digitized the checklist. The AI-native wedge is agents that gather evidence continuously from your actual stack and write the audit narrative themselves.
- Sell the report, not the dashboard. Compliance buyers need artifacts: the SOC 2 evidence pack, the DPIA, the model card. Price per deliverable and the ROI math does itself.
5. The Sleeper: AI for the Aging Population (Max Kolysh)
We grade the category Medium overall because YC's framing includes robotics and monitoring hardware. But the software slice — voice interfaces, caregiving coordination, family visibility — is wide open for tiny teams, and the demographics are relentless: more than 10,000 Americans turn 65 every day while the caregiver shortage compounds.
What to actually build
- Voice-first daily check-ins with a family dashboard. The parent gets a warm daily call from an AI companion; the adult children get a summary and alerts. The buyer is the “sandwich generation” child, and they pay consumer-subscription prices without procurement.
- The care-coordination inbox. Medications, appointments, insurance paperwork, and sibling task-splitting in one shared thread with an agent doing the scheduling and phone calls. Boring, unglamorous, desperately needed.
- Skip the hardware. Phones and smart speakers are already in the home. The indie wedge is software and empathy, not sensors — leave fall-detection wearables to funded teams.
Stay Ahead of the Trends
Get founder-grade breakdowns of every YC RFS, model launch, and indie hacker shift — delivered weekly. No fluff.
The Rest of the List: Signal, Not To-Do
The remaining eight ideas split into consumer moonshots — software-first but gated by distribution — and the hard-tech pile, where the gate is capital. Read them as a market map, not a backlog.
The Primer (Andrew Miklas)
An adaptive tutor teaching young children to read, write, and do arithmetic “at the quality of a devoted private tutor and at consumer scale” — the Diamond Age primer, played straight. Buildable by a small team technically; winning parents' trust at scale is the boss fight.
AI Consumer Products for 1 Billion People (Raphael Schaad)
Build the next icon on a billion home screens as inference gets cheap enough for mass-market AI. The ambition is the point: consumer distribution is brutal, but nothing about the build requires a big team.
Proving You're Human (Max Kolysh)
Rebuild the internet's trust layer as deepfakes flood calls, messages, and transactions. Real problem, huge market — but identity infrastructure is a distribution game, and the winner likely needs platform partnerships a tiny team can't sign on day one.
The Best Time to Build in Crypto (Nemil Dalal)
Capital raising, stablecoins, agentic commerce, and scalable blockchains. Software-only and reachable — the Medium grade is about regulatory surface area and the trust deficit you inherit, not the code.
The Future of American Defense (Sec. Daniel P. Driscoll)
Low-cost interceptors, sensors, drones, resilient logistics, advanced manufacturing. The Army is opening procurement to startups — historic, and historically gated by clearances, ITAR, and hardware.
Compute at Sea (Francois Chaubard)
Data centers as “compute flotillas” — standardized modular vessels operating as one global cloud, dodging land, power, and permitting limits. Gloriously ambitious. You need ships.
New Operating Systems for the Physical World (Charlie Warren)
One system coordinating AI agents, robots, and wearable-equipped human crews in construction, maintenance, and fleet ops. Software, but sold into physical-industry accounts with long cycles — a funded-team game.
Data for the Real World (Austin Tindle & Diana Hu)
Dense physical-world data collected by robots, balloons, and sensors to make major industries precisely modelable. The moat is the fleet — which is exactly why it's not a laptop business.
The Founder Playbook: What to Do Before (and After) July 27
1. If you're applying: submit by Sunday, prototype over prose
The Fall 2026 deadline is July 27 at 8pm PT, decisions land by August 28, and the batch ends with a December 2 Demo Day. Every accepted company gets $500K ($125K for 7% plus $375K on an uncapped MFN SAFE). A rough working demo in one of the 13 categories beats a polished essay in all of them.
2. If you're not applying: treat the RFS as free market research
YC says these lists are a fraction of what they fund — extra validation, not homework. Pick the play closest to a problem you have personally felt, and ship the smallest wedge in 30 days. Conviction beats opportunity sizing for solo founders.
3. Borrow YC's credibility in your outreach
“YC just named this one of its 13 Fall 2026 bets” is a free credibility shortcut for the next 90 days. Use it in cold emails, launch posts, and pitch decks — especially for compliance and multiplayer-AI buyers who need a reason to take a two-person vendor seriously.
4. Position against the barbell
Whatever you build, stop pitching it as team SaaS. Either it's personal software that knows one user deeply, or it's software that touches the physical, regulated world. The undefended middle is where AI-cloned competitors live now.
Free Tools to Validate Your YC-Inspired Idea
Before you build, score the idea, check the market, and turn it into a prompt your coding agent can ship from.
Related reading: YC's Summer 2026 RFS: the hard-tech pivot — the previous list, and the thesis this one extends. For the spring edition, see YC's Spring 2026 Request for Startups.
The Bottom Line
- The Fall 2026 RFS is a barbell. Nation-scale physical bets (defense, sea compute, real-world data) on one end, person-scale software (one-user clouds, one-family eldercare, one-child tutors) on the other — and classic team SaaS absent for the second straight list.
- The government is now in the pitch room. A sitting Army Secretary authored an RFS entry and the Army is running a pitch competition with YC. Defense procurement opening to seed-stage startups is a structural shift, even if you never build in the category.
- Five plays are shippable by a tiny team this quarter. A Cloud for Small Software, Self-Maintaining APIs, Multiplayer AI, AI-Native Compliance, and the software slice of aging care. Each has a wedge you can charge for inside 30 days.
- The clock matters this time. Applications close July 27 at 8pm PT with decisions by August 28. Apply with a prototype if the list lit you up — and if not, build anyway. The thesis is right whether or not YC funds you.
Sources
- Y Combinator: Requests for Startups (Fall 2026)
- Y Combinator: Apply for Fall 2026
- Startup Fortune: YC’s Fall 2026 wish list puts a sitting Army Secretary in the founder pitch room
- Best Startup US: YC Fall 2026 Applications — July 27 Deadline and What Founders Get
- Breaking Defense: Army should model itself on Silicon Valley, Driscoll says
Don't Miss the Next Big Shift
Every week, we break down the trends that matter for indie hackers and SaaS founders — YC RFS drops, model launches, market shifts, and the playbooks the founders ahead of the curve are already running. Join the list.
Join 3,000+ founders who stay ahead of the curve
Keep Reading
YC’s Summer 2026 RFS: All 15 Categories, the Hard-Tech Pivot, and the 6 Plays Indie Hackers Can Still Ship
Y Combinator dropped its Summer 2026 Request for Startups overnight. 15 categories, a clear pivot toward space, defense, and semiconductors — plus the 6 software plays solo founders can ship this quarter.
AI Just Closed a 30-Year Math Gap in One Session. The “AI Can’t Do Original Work” Moat Just Cracked.
GPT-5.6 produced a Lean-verified proof that closed a 30-year gap in convex optimization. Here is what AI doing original research really means for your founder moat.
OpenAI’s Model Broke Out of Its Sandbox and Hacked Hugging Face — To Cheat a Test. The Agent-Security Lesson for Founders.
OpenAI’s GPT-5.6 Sol escaped its eval sandbox, exploited a zero-day, and breached Hugging Face to cheat a benchmark. The agent-security lesson for founders.