RippleStore
Sign in Sign up
Developer guide

How to submit here,
and do it well.

What gets accepted, how the board ranks, and how to write a listing that earns the click. Written down rather than implied.

What belongs here

Ripple Store lists software people can use today. That's the whole bar. It can be free, paid, open source or a weekend project — but it has to exist.

Accepted: desktop apps, web apps, CLIs, MCP servers, libraries, browser extensions, mobile apps, APIs, design systems, self-hosted tools, hardware with software, and paid services with a real product behind them.

Not accepted: waitlist pages with nothing behind them, affiliate link farms, resold white-label templates presented as your own build, anything requiring payment before you can see what it does, and listings posted on someone else's behalf without them knowing.

The one rule that matters: if a person clicks your link, they should reach something working within one click. A signup wall is fine. A "coming soon" is not.

Submitting

Sign in with Google or GitHub — or an email and password if you prefer — then hit Launch. The form takes about two minutes.

The logo

Upload the logo, not a screenshot. A square mark on a transparent or solid background reads correctly at 56px, which is the size it will be seen at most often. PNG, JPG, WebP or GIF up to 3 MB; it gets squared to 512×512 automatically.

Skip it and we generate a clean monogram tile from your product's name — which looks deliberate, not broken. But a real logo does better.

The one-liner

This is the entire pitch. It appears on the board, in search, and under your product name. Two hundred characters, hard limit.

Write what it does, not what it aspires to. Compare:

  • Weak — "The revolutionary next-generation platform empowering developers to unlock their potential."
  • Strong — "Insurance for AI-generated code — know what else breaks before you ship."

The second one tells you what the thing is, who it's for, and why you'd care, in eleven words. Cut every adjective you can and it usually improves.

The description

Blank lines become paragraphs. Three or four short ones beat one long one. Cover: who it's for, the problem it solves, what makes it different, and — if it applies — what it deliberately does not do. Naming a limitation buys more trust than another feature bullet.

Platforms and licence

Tick every platform your product actually runs on — Web, iOS, Android, macOS, Windows, Linux, CLI, browser extension, API, self-hosted or MCP server. These become filters, so being accurate helps the right people find you.

If you choose Open source the licence field becomes required. Pick the real one — MIT, Apache-2.0, GPL-3.0, AGPL-3.0, BSD-3-Clause, MPL-2.0 and the rest are all in the list. Closed products can leave it blank or mark it Proprietary.

Category and pricing

There are 207 categories across 20 areas. Pick the closest — it's a starting point, not a cage, and you can change it later.

Be straight about pricing. Nobody minds paid. People mind finding out it's paid three clicks in. "Freemium" means there's a genuinely usable free tier; if the free tier is a trial, choose Paid.

How ranking works

Two tiers, and it's not a secret.

The four Ripple products sit at the top, marked with a Ripple badge, ordered by their own vote counts. They're house entries — labelled so nobody mistakes them for competition you have to beat.

Everything else ranks by a decay score:

score = (votes + 1) ÷ (hours since launch + 2)0.55

Ten votes in an hour outranks thirty over a week. A launch stays visible for roughly two to three days before decay pushes it down, which is long enough to matter and short enough that the board keeps moving.

One vote per account per product. Click again to take it back. There is no paid placement and nothing to buy — the only way up is people liking what you made.

Launching well

  • Post it yourself. Makers get asked questions in the comments. Be there to answer them.
  • Morning is better than evening. A launch gets its whole window in the first day; starting it at midnight wastes half of that.
  • Reply to every comment. Including the critical ones — especially the critical ones. It reads better than a wall of thank-yous.
  • Don't buy votes or ask a group chat to brigade. It is obvious in the data, and it gets the product delisted.
  • Relaunch when something real changes. A major version, a rewrite, a new platform. Not every patch.

Moderation

Listings go live immediately. Removal happens after the fact, and only for: broken or dead links, vote manipulation, impersonation, malware, listings for products that don't exist, and submissions posted on behalf of someone who didn't ask.

If something of yours is removed you'll get an email saying which of those applied. If you think it's wrong, reply to it — a person reads those.

Accounts

Sign in with Google, GitHub, or an email and password. GitHub is the one worth using if you ship code — it fills in your handle and avatar automatically, and it's the account most makers here already have.

Passwords are stored as bcrypt hashes. We never see them in plain text, and there's no password field to leak because OAuth accounts don't have one.

Your email is never shown publicly and never sold. Your profile shows your name, bio, links and products — nothing else.

About the Ripple products

Four products are built in-house and pinned to the top of the board.

  • RippleCheck — AST-based impact analysis for AI-generated code. Open source, MIT.
  • Ripple Lead Finder — finds local businesses with no website, across 111 countries. Open source, MIT.
  • Ripple Foundry Co — websites in four days, business software in three to six weeks. Paid.
  • Business + Freelancer Bundle — the two above, wired into one pipeline for agencies. Paid.

They're marked rather than hidden, because a store that pretends its own products are community submissions isn't worth trusting.