NoSignups, published on GitHub as BraveOPotato/FckSignups, is a curated directory of open-source tools that run in a browser and never ask you to create an account. It is aimed at anyone who needs one small job done right now — resizing an image, converting a file, checking a piece of text — without first handing over an email address, and secondarily at developers who want to add entries to the list or run the site themselves. The project was renamed from FckSignups to NoSignups, though the repository path still carries the older name.
What it does
The directory collects tools that pass a single admission rule: you can open them and use them immediately. No registration wall, no email verification step, no payment prompt before the first action. Alongside that, every listed tool is open source and free.
Entries are sorted into categories so the list stays browsable rather than being one long wall of links. The categories shipped by default include productivity, design and graphics, and development, with an "all" view on top; the video covering the project also points to privacy tools among them. The catalog is described as holding more than two hundred tools.
The project states its position plainly in the README as a pair of columns — what it believes against what it rejects. It backs tools that work immediately, data that stays with the user, open source as the default and simplicity over bloat; it rejects forced registration, data harvesting, proprietary black boxes and unnecessary complexity. That is not decoration, it is the filter that decides what gets listed.
How it works
NoSignups is a React and TypeScript project, so the list is a running site rather than a plain README of links, with search and category filtering built around the data.
Each tool is a structured record, and the README documents the schema. Required fields are an id (a URL-friendly unique identifier), a name for display, a one-sentence description, a url pointing directly at the tool, and a category that must match one of the defined category ids. Optional fields fill in the rest:
tags— an array of searchable keywordsgithub— a link to the tool's own source repositorylicense— an SPDX license identifierstars— a GitHub star count, for displayfeatured— a boolean that pins the entry to the topnotRecommendedReason— a reason the entry is not recommended
That last field is the interesting one. Rather than silently dropping a tool people will search for anyway, the schema lets a maintainer keep it listed and attach the reason it is not the one to reach for. Categories are themselves records with an id, a name and an icon, so the navigation is data too.
Because entries are data conforming to a documented shape, adding a tool means writing one record, not building a page.
Getting started
To read the list, you browse it, click a tool and use it — there is nothing to install and nothing to sign into, which is the entire point.
To run the site yourself, the README gives a single chained command that clones the repository, installs dependencies and starts the dev server:
git clone https://github.com/BraveOPotato/FckSignups.git && \
cd FckSignups && \
npm install && \
npm run dev
The project is licensed under GPL-3.0, so a fork or a modified internal version carries that license with it. There are community links in the README to a Discord server and a subreddit for discussion around the list.
When to use it / when not
Reach for NoSignups when the task is a one-off and the friction is the problem: a single conversion, a quick edit, a format check on a machine that is not yours. It is also a reasonable thing to hand to non-technical friends and family who keep getting funnelled into accounts, and a sensible starting point if you want to assemble an internal page of approved tools for a team.
It is not the right place to look when you need an account on purpose — saved projects, shared workspaces, sync across devices, anything with persistence behind it. It is also a list, not a product: entries are links out to third-party sites, so their uptime, their behaviour and their continued adherence to the no-signup rule depend on those projects rather than on this repository. Treat the curation as a strong filter, not as a guarantee.
The repository is young — created in May 2026, with pushes continuing through September — and it has picked up roughly 3,500 stars and over 200 forks in that time, including a 436-star day around the video's release. That is momentum, but it is also a reminder that the list is still settling.
Anyone who has walked away from a task because a site demanded an email first should keep this bookmarked; it solves a small, constant annoyance well, and it does so without asking anything in return. Developers get a second reason to look: the tool schema is clean enough that forking the site into a private or team-scoped directory is a short afternoon's work rather than a project. Judge it as a curated index, not as software with features, and it holds up.