Ninite, YC Founder Story

Company: Ninite (formerly BaseShield / Secure By Design Inc.) Founders: Patrick Swieskowski & Sascha Kuzins YC Batch: Winter 2008 Industry: Developer Tools / Windows Software Utilities Founded: 2008 | Public Launch: October 2009 Funding: $125K (YC + angels), then entirely self-sustaining Team Size (2024): 2 people. Still running. Still profitable. Clients: NASA, Tupperware, and thousands of IT professionals worldwide

---

---

The One-Line Summary

Two open-source hackers were so fed up with the ritual humiliation of reinstalling Windows, the toolbar junk, the "click next 47 times" installers, the adware hiding inside free software downloads, that they built the cure. Fifteen years later, it still runs with 2 people and serves NASA.

---

Lens 1, The Before State

Who Were They Before YC?

Patrick Swieskowski and Sascha Kuzins were not startup types by any conventional definition. They were serious open-source hackers, people who built things because things were broken, not because they had a pitch deck or a growth target. Both were deeply embedded in the Windows development community, the kind of engineers who understood the Windows API at a level most developers never bother with. They coded in C++ against raw platform primitives because they believed software should feel like it belongs on the system it runs on, not wrapped in some cross-platform abstraction that makes everything feel slightly off.

They were, in the language of the open-source world, people who solved problems for themselves and then shared the solution. Not entrepreneurs. Not founders. Just builders who happened to also hate bad software.

The Personal Pain They Were Living

Anyone who has ever set up a new Windows computer in the 2000s knows exactly the frustration that made Ninite inevitable. You buy a fresh machine or reinstall your OS, and then you spend an entire afternoon, sometimes an entire day, downloading software one application at a time. Firefox from Mozilla. VLC from VideoLAN. 7-Zip from somewhere. Adobe Reader from Adobe's labyrinthine website. Java, which inexplicably also wants you to install the Yahoo toolbar. Google Chrome, which sneaks in as a bundled extra alongside something else entirely.

Each installer had its own "next, next, next" ritual. Each one had checkboxes pre-ticked for toolbars and browser hijackers and "bonus" software that would quietly install itself and then prove nearly impossible to remove. It was a process that everyone just accepted as the cost of owning a computer. Not because it was acceptable. Because nobody had fixed it yet.

Patrick and Sascha had been doing this same painful reinstall dance themselves, for their own machines, for their families' machines, for friends who called them because they were "the tech person." Every time, the same ninety minutes of mechanical clicking. Every time, the same toolbar infestation to clean up afterwards.

Why They Almost Didn't Look Like "Founders"

In 2008, the YC archetype was beginning to solidify around young, often Stanford-adjacent engineers building consumer web apps. Patrick and Sascha were building a desktop Windows utility in C++ to solve a problem that most of Silicon Valley considered beneath notice. This was not a social network. This was not a mobile app. This was infrastructure for a platform that the tech world was already dismissing as legacy.

There was no obvious venture scale story. No network effects pitch. No billion-dollar market map. Just two people who were deeply annoyed by something broken and technically capable of fixing it.

Key Insight for Aspiring Founders

The problems that "everyone just accepts" are frequently the best ones to solve. Patrick and Sascha didn't find an underserved market through analysis. They found it through personal exhaustion. The strongest signal that a problem is worth solving is that you've already been solving it badly, by hand, for years.

---

Lens 2, The Idea Origin

How the Idea Was Actually Born

The concept started with a straightforward observation: Linux and macOS had package managers. Linux had apt-get. Mac had the beginnings of what would become Homebrew. Windows had nothing. Every application was an island, its own website, its own installer, its own update mechanism, its own bundled junkware.

Patrick and Sascha, as open-source engineers, lived in the Linux world enough to feel the contrast viscerally. On Linux, you could install a dozen applications in one terminal command. On Windows, you were clicking through GUI wizards one at a time, watching progress bars crawl, declining toolbar offers, and hoping nothing broke.

The idea: bring the Unix package manager concept to Windows consumers, without requiring them to know what a package manager is.

The First Version, BaseShield

What they brought to YC in Winter 2008 was not Ninite. It was something called BaseShield, a more ambitious, technically complex idea. BaseShield was envisioned as a full Windows application store with sandboxing: each app would run in its own virtualised environment, isolated from the rest of the system. Think of it as a secure, open version of what Microsoft's own store would eventually become.

This was genuinely impressive engineering. BaseShield launched in November 2008 and got a TechCrunch write-up. It offered about two dozen free open-source apps. The technology worked. But the complexity of the sandboxing approach was also its weakness, it required developers to package and submit their apps specifically for BaseShield, which created a chicken-and-egg catalogue problem.

The Pivot That Created Ninite

Here is where the story gets instructive. At some point between the BaseShield launch in late 2008 and October 2009, Patrick and Sascha made a decision that most founders struggle to make: they stripped the product down to its most useful core and threw away the complexity.

BaseShield's sandboxing was elegant. It was also unnecessary for what people actually needed. What people needed was simple: pick some apps, get them installed, no junk attached. Full stop.

The result was Ninite. No sandboxing. No app store infrastructure. No virtualisation layer. Just a web page where you tick checkboxes, click "Get Installer", download a single executable, run it, and watch all your chosen apps install themselves silently, cleanly, without a single toolbar offer in sight.

They launched it quietly on Hacker News on October 22, 2009, timed deliberately to coincide with the release of Windows 7, when millions of people would be setting up new computers. The timing was not accidental.

The Signal That It Was Working

Within hours of the Hacker News post, the response was immediate and emotional. Patrick Mackenzie, a well-known developer in the HN community, wrote that Ninite would make him buy a new laptop six months ahead of schedule, simply because he no longer dreaded the day of setup. People were describing it not as useful software but as something that made a previously dreaded experience feel effortless.

Patrick Swieskowski later described the core insight behind that reaction: "Software installation has just been so crappy for so long, people just assume it's going to suck. The first reaction to Ninite is frequently amazement."

When your product's first reaction is amazement at something being fixed that was always broken, you have found product-market fit.