You keep promising yourself a 9 pm cutoff. CaughtShipping holds you to it — publicly. Set a curfew, and a tiny desktop app notices when an editor is open past it. You get 5 minutes of grace, then your fall is posted to the public blotter: streak reset, custom roast, receipts. Keep your word instead and climb the Wall of Rest. It only ever sees app names, never your code. Free, on macOS, for developers who lie to themselves nightly.
No reviews yetBe the first to leave a review for CaughtShipping
Maker
📌
Hey everyone 👋
I built CaughtShipping because I've told myself "9 pm cutoff, for real this time" roughly 900 nights in a row, and the only thing that ever actually worked was the fear of getting caught.
So that's the whole product:
- Declare a nightly curfew. 9pm is the crowd favorite. The latest we allow is 11pm — if you need later than that, we can't help you, but a therapist might.
- A tiny tray app watches locally. The second it catches an editor open past your cutoff, a 5-minute grace countdown starts. Close it, and you're safe.
- Don't, and you're on the blotter. Your fall goes public: timestamp, streak reset to zero, and a roast picked for the occasion. Anonymous handles allowed. Dignity non-refundable.
- Keep your word, and you climb the Wall of Rest instead — a public leaderboard ranked by consecutive nights you actually logged off.
Because life happens: you get 2 overrides a month for genuine prod fires (no roast) and 4 pauses to skip a night. Hardcore mode sets grace to zero, if that's the kind of person you are.
On privacy, one hard promise: the app only ever sees which app is open — never window titles, files, code, or keystrokes. We publish the broken promise, never the work.
It's completely free — macOS today, Windows soon. Would love your roasts… I mean, feedback. And if you fall tonight, own it. The wall forgives. It does not forget.
Report
Love the accountability angle, the public fall is genuinely clever. One thing I'd want though: let me whitelist specific apps like a long-running debug session or a prod incident bridge so the blotter doesn't punish me for legitimate late nights. Maybe a "this counts as work" quick toggle that requires a small repo commit as proof.
Really good comment — and you're putting your finger on something real, so let me be straight about where we land.
First, the thing you might not know: this already partly exists. You get 2 Overrides a month — one tap during your grace window and the night just doesn't count. No blotter, no roast, no charge. That's exactly the "prod incident at 2am" escape hatch. There's also Pause today if you know ahead of time it's going to be a rough night.
On the "prove it with a commit" idea — I love the instinct (make the exemption honest, not a free cheat), but we're going to say no to that specific mechanism, for two reasons:
1. Caught Shipping never looks at your code, your repos, or your commits — only which app is in the foreground during your curfew. Our one hard promise is "we publish that you broke curfew, never what you worked on." Wiring in commit-reading would break that.
2. A commit actually proves you were shipping — which is the exact thing we're ribbing you for. It doesn't prove the night was an emergency you couldn't avoid. That's why our Override runs on the honor system. As the button says: "lying about prod fires is between you and your conscience." 🫡
Appreciate you pushing on this — this is exactly the kind of edge that makes the product better. 🙏
Report
Downloaded it last night and the five minute grace period felt just long enough to panic close everything, which is honestly the point. Love that it only sees app names, not the code itself.
Report
Maker
@aye532679654385 Yes, we don't track anything that you do in the app. We just check if you have it open. If we are missing some apps, please feel free to let me know so I can add them.
Report
The "never your code" promise is a really smart trust move for something that lives on your machine — shows you actually thought about why a dev would hesitate before installing it.
Report
Maker
@dnd1112360 Yep! The app does not look at the code at all. We check the actual application name.
Love the accountability angle, the public fall is genuinely clever. One thing I'd want though: let me whitelist specific apps like a long-running debug session or a prod incident bridge so the blotter doesn't punish me for legitimate late nights. Maybe a "this counts as work" quick toggle that requires a small repo commit as proof.
@tunahan155609
Really good comment — and you're putting your finger on something real, so let me be straight about where we land.
First, the thing you might not know: this already partly exists. You get 2 Overrides a month — one tap during your grace window and the night just doesn't count. No blotter, no roast, no charge. That's exactly the "prod incident at 2am" escape hatch. There's also Pause today if you know ahead of time it's going to be a rough night.
On the "prove it with a commit" idea — I love the instinct (make the exemption honest, not a free cheat), but we're going to say no to that specific mechanism, for two reasons:
1. Caught Shipping never looks at your code, your repos, or your commits — only which app is in the foreground during your curfew. Our one hard promise is "we publish that you broke curfew, never what you worked on." Wiring in commit-reading would break that.
2. A commit actually proves you were shipping — which is the exact thing we're ribbing you for. It doesn't prove the night was an emergency you couldn't avoid. That's why our Override runs on the honor system. As the button says: "lying about prod fires is between you and your conscience." 🫡
Appreciate you pushing on this — this is exactly the kind of edge that makes the product better. 🙏
Downloaded it last night and the five minute grace period felt just long enough to panic close everything, which is honestly the point. Love that it only sees app names, not the code itself.
@aye532679654385 Yes, we don't track anything that you do in the app. We just check if you have it open. If we are missing some apps, please feel free to let me know so I can add them.
The "never your code" promise is a really smart trust move for something that lives on your machine — shows you actually thought about why a dev would hesitate before installing it.
@dnd1112360 Yep! The app does not look at the code at all. We check the actual application name.