# I launched Prototyped > I launched Prototyped, a store for working software prototypes with full source code, tests, documentation, and instructions for coding agents. Author: [Flavio Copes](https://flaviocopes.com/about/) | Published: 2026-08-01 | Topics: [News](https://flaviocopes.com/tags/news/) | Canonical: https://flaviocopes.com/i-launched-prototyped/ Today I launched [Prototyped](https://prototyped.dev). It is a store for working software prototypes you can download, change, and run yourself. You get the full source code, tests, setup instructions, architecture notes, and instructions written for coding agents. Open the project in Cursor, Claude Code, Codex, or your favorite coding agent. Tell it what you want to change. Remove what you do not need. Add what is missing. Move it to another stack if you want. The idea is simple: > Skip the blank repository. ## This took me a while I have been thinking about this idea for a long time. The first commit in the Prototyped repository is from March 10, 2026, almost five months ago. The idea was already in my head before that. I built the first storefront. I added a few prototypes. I connected the checkout. I expanded the catalog. Then I stopped. In April I redirected the site back to flaviocopes.com and moved on to other things. But the idea never went away. In the past few weeks I built a ton of products during my [Summer of Code](https://flaviocopes.com/the-summer-of-code/). Every one left me with working code, tests, decisions, and a lot of knowledge about how the product fits together. Some of those products will become businesses. Some will stay free. Some were experiments I wanted to build because the idea was interesting. But the code can still be useful. Now feels like the right time to bring Prototyped back to life and see what happens. ## Why prototypes? Starting from an empty folder is slow. Even with a coding agent, you still need to decide what the product does, how the data fits together, where the difficult parts are, and what a working version looks like. A prototype gives you that starting point. It is not a screenshot, a landing page, or a generic dashboard with buttons that do nothing. It is a working project with the important paths already implemented. Maybe it already does 80% of what you need. Maybe you only want the architecture and tests, then you will rewrite the interface. Maybe the prototype uses Astro and Cloudflare, but you want Next.js and Vercel. The working product becomes the specification your agent can follow. You are not locked into my choices. ## What you get Each prototype is a separate $20 one-time purchase. The package includes: - the complete source code - tests and a clean project structure - setup and deployment instructions - architecture and decision documents - security notes where the product needs them - instructions for coding agents - an MIT license I clean every package before releasing it. Private data, credentials, account identifiers, deployment history, build output, and other files that should not leave my computer are removed. The result is an audited source ZIP you can open, run, and change. ## Two prototypes are available now I am starting with two. ### Waiting Lists [Waiting Lists](https://prototyped.dev/apps/waiting-lists) is the self-hosted version of the product I run at [waitinglists.dev](https://flaviocopes.com/waitinglists-dev/). It gives each of your products a separate waiting-list endpoint. You keep the form on your own site. Waiting Lists handles what happens after someone submits it. A new subscriber receives a confirmation email. The address only becomes confirmed after the person presses the confirmation button. The dashboard shows confirmed and pending subscribers, delivery problems, list settings, and the websites allowed to use each endpoint. When you are ready to launch, you can export the confirmed addresses as a universal CSV, a complete consent archive, or a file ready for Sendy, Kit, or Mailchimp. The download also includes a private JSON API and a command-line client. You or your coding agent can create a list, connect a form, inspect it, change its settings, and export the subscribers without opening the dashboard. The complete service runs in your Cloudflare account. You own the Worker, D1 database, email configuration, subscriber data, and retention rules. You could use it as a private waiting-list service for all your projects. Or you could ask your agent to add customer accounts, teams, billing, webhooks, or another email provider and turn it into a hosted product. ### Livestream Recorder [Livestream Recorder](https://prototyped.dev/apps/livestream-recorder) is a native macOS app for saving live YouTube streams as local MP4 files. Paste a livestream URL and choose whether to record from the current live point or catch up from the available beginning. The app shows download progress, captured media time, and when a catch-up recording reaches the live edge. For streams that require a signed-in YouTube session, you can choose a local browser and let `yt-dlp` use its cookies. The app does not store those cookie values. Stopping a live recording is not as easy as killing a process and hoping the file works. Livestream Recorder handles cancellation, retries, separate audio and video tracks, interrupted recordings, FFmpeg finalization, and verification of the finished MP4. It is built with Swift 6 and SwiftUI. The package includes the Xcode project, 10 test files, setup instructions, architecture notes, and detailed documentation for coding agents. You can keep it as a small personal recorder, customize the macOS interface, add quality and format controls, or use the working recording engine as the blueprint for a Windows app, Linux app, or command-line tool. You need macOS 14 or newer, Xcode 16 or newer, and locally installed copies of `yt-dlp`, FFmpeg, and Deno. Only record streams you are allowed to save. The catalog already contains many more prototypes. I am not opening them all at once. Each one needs a clean source package, useful documentation, a safe checkout, and one final review. They will become available gradually. ## Liquid software I call the bigger idea [liquid software](https://prototyped.dev/liquid-software). The prototype is a working implementation, not a technical constraint. The product behavior, architecture, edge cases, and tests matter more than the framework used for the first version. Your coding agent can keep the current stack or move the product into another one. It can turn a web app into a desktop app, replace a hosted service, simplify the product for one person, or expand it for a team. The source code is the starting material. ## Let's see what happens I do not know yet what Prototyped will become. Maybe people want small tools they can adapt for themselves. Maybe they want complete product starting points. Maybe the most useful part will be the documentation and agent instructions. The only way to find out is to put it out there. [Browse the first prototypes](https://prototyped.dev).