Ripply: A waitlist platform, run from A to Z

Fifty thousand people can join in ten minutes, and two of them getting the same position becomes a public argument on social media.

A queue that cannot collide

Positions are assigned by the database itself, in one atomic step, never calculated in code that can race. Ten people or ten thousand in the same minute, every position is exact, unique and provable — and the live count updates without a refresh.

Every reward is real money — a gift card, a cash payout, a t-shirt in the post. Send one twice and the founder pays for it.

No reward ever goes out twice

Four locks in a row protect anything worth money. Each payout gets one permanent name derived from the person and the reward, so every retry lands on the same slot. The payment provider is handed that same name and refuses a duplicate. Incoming confirmations are recorded once and only once. And if a worker dies mid-payment, the slot is held for five minutes, then safely reclaimed and retried. Under load testing, not one duplicate got out.

Brands expect their campaign on their own domain, without raising a ticket or waking up to an expired certificate.

Their own web address, working in seconds

A brand points its domain at the campaign and the certificate is issued and installed automatically, with the page served from the edge network nearest each visitor. No tickets, no waiting, no expired certificate at midnight.

The page runs on strangers' phones and inside other companies' websites, where a slow script gets the whole product banned.

Pages that render anywhere, fast

Whatever a brand builds compiles into a self-contained page with no layout shift, and into an embed that loads fast, never touches the host site's styles and cannot see another brand's data. It renders in under 35 milliseconds on customer sites.

A discount code that lives only in the campaign, and not in the brand's real shop, is a reward nobody can actually use.

Shops that stay in step

Discount codes are created natively inside Shopify, WooCommerce, Wix and WordPress — money off products, money off the basket, buy-one-get-one, free delivery. Paid orders mark the reward as used; cancellations and refunds pull the code back. Every fifteen minutes the system re-checks recent orders, so a dropped message never leaves a reward in limbo.

Letting a model write raw pages is expensive on every generation and quietly produces broken, off-brand layouts.

An AI builder that does not cost a fortune

Instead of asking a model to write raw code, the builder fills a fixed set of brand-safe building blocks. It cuts the cost of each generated page by more than four fifths and, more importantly, the result is always accessible, always on brand and never broken.

The founder runs the whole business from one private console — a login screen on a guessable address is an invitation.

A locked door the internet cannot find

The founder's console lives on its own address, and anyone who is not on the allow-list gets a plain page-not-found — not a login screen to attack. Names on the list get only the powers their role needs, and anything destructive asks for a second factor again before it runs. Every action is written to a log that cannot be edited.

When a person asks to be erased, half-deleting them across payments, logins, artwork and passes is a breach waiting to happen.

Deleting someone properly

When a customer asks to be erased, the request is scheduled with thirty days to change their mind and a one-click cancel link in their inbox. After that, everything goes: records, uploaded artwork, wallet pass files, profile photos and the accounts held at the payment and login providers. The history log survives with the personal details scrubbed out of it, so the business keeps its books without keeping the person.