Launch kit
A platform-native draft for every channel — written to that community’s rules, with the ban-safety note baked in.
How to post it — without getting banned
Each draft is written for its channel: a build-story for Show HN, a problem-first post for r/devops, a shootable video concept for TikTok. The safety note tells you the one thing that gets posts removed. LaunchWake never posts for you — you stay in control.
Hacker News — Show HN
Best · Tue–Thu, 8am ETShow HN: Cascade – database migrations that never lock a table I kept taking production downtime whenever a migration rewrote a big table, so I built Cascade. It runs schema changes in the background and swaps them in without an exclusive lock — even on tables with millions of rows. It's open-source (MIT), works with Postgres and MySQL, and installs as a single binary. Happy to answer anything about how the online swap works.
No link in the title. Post the GitHub link as your first comment, then reply to questions for the first hour — that's what carries a Show HN to the front page without tripping the self-promo filter.
Product Hunt
Best · Tue, 12:01am PTCascade — open-source database migrations that never lock a table. Run schema changes in the background and swap them in with zero exclusive locks, even on huge tables. Postgres + MySQL, MIT-licensed, single binary. I'll be here all day answering questions.
Don't ask for upvotes anywhere — Product Hunt shadow-ranks that. Share the page and let the demo GIF do the work.
r/devops
Best · Weekdays, 9–11am ETA migration locked a 40M-row table during a deploy last month and took us down for 9 minutes. I've been chasing zero-lock schema changes since. Wrote up the approach (background copy + atomic swap) and open-sourced the tool — happy to compare notes on how other teams handle big migrations.
Post this in the weekly self-promo thread only. A standalone link post here will be removed and can cost you the account.
Lobsters
Best · WeekdaysHow Cascade does online schema changes without an exclusive lock — a write-up of the background-copy + shadow-table + atomic-rename approach, the edge cases (triggers, foreign keys, huge tables), and where it still falls short.
Submit the design write-up, not the product page. Tag it 'databases' and stay for the discussion.
TikTok — Build in public
Best · Weekdays, 6–9pmText on screen: 'watch a migration lock a prod table' over a terminal.
- 0–2s hookTerminal runs a normal ALTER TABLE; a 'locked / requests piling up' meter spikes red.
- 2–6s problemCut to a dashboard showing 9 minutes of downtime — 'this took us down last month.'
- 6–12s fixRun the same change with Cascade; the meter stays green, traffic keeps flowing.
- 12–15s CTA'Open-source, link in bio.' Show the repo name.
Posts can't hold a clickable link — keep your one tracked link in bio and point to it verbally.
In your own account you can edit every draft, regenerate with a different tone, and mint a tracked link per post. Start free.