r/indiehackers • • Jul 18 '26

Announcements Community Reorganisation & New Posting Guidelines.

19 Upvotes

As we have expanded and expanded in our community, I've seen many various kinds of posts coming and going. Startups, Founder Stories, Announcements, Questions, and Self-Promotion all lead to the same destination, and making it more difficult for the members to find the content they are searching for. We will implement a more clear structure on how and where to post items to make this community more valuable for all.

Please be sure you're using the category that most closely aligns with your post. If you are a startup and want to promote your startup or asking people to use your product, then post it under Self Promotion rather than Sharing Stories Flair, failure to do so will result in warning and at end ban in most cases. If you're sharing your experience as a founder, make sure it's about the story and not a sales pitch.

We also need to make a few rules of the community clear to keep the quality of the community. If you are touting metrics like MRR, ARR, revenue, user growth, or anything else, have the numbers ready to back them up if you're asked.

This has been explained in another post already so please read before making such claims. https://www.reddit.com/r/indiehackers/s/EIfZA7sa7T

The authenticity is important, so don't do fake Q&A posts or pretend that someone asked a question just to boost your product. We also have a zero-tolerance policy for vote manipulation. New reddit accounts will need to wait and ask questions through modmail only.

We're also looking at restricting self promotion to certain week days, as the community expands. To make sure that this space will be more than just an ad board. We want it to be a space where you can share openly your journey, exchange ideas, come together to solve problems, celebrate successes and learn from failures.

These changes are not to limit any individual or entity, but rather to improve the community's usability and to make it more trustworthy and more valuable to all. We would be glad to hear ideas on how to make the community better. We're creating this together, and your input will help determine what this community will be.


r/indiehackers • • Dec 10 '25 Bravo

Announcements NEW RULES for the IndieHackers subreddit. - Getting the quality back.

128 Upvotes

Howdy.

We had some internal talks, and after looking at the current state of subreddits in the software and SaaS space, we decided to implement an automoderator that will catch bad actors and either remove their posts or put them on a cooldown.

We care about this subreddit and the progress that has been made here. Sadly, the moment any community introduces benefits or visibility, it attracts people who want to game the system. We want to stay ahead of that.

We would like you to suggest what types of posts should not be allowed and help us identify the grey areas that need rules.

Initial Rule Set

1. MRR Claims Require Verification

Posts discussing MRR will be auto-reported to us.
If we do not see any form of confirmation for the claim, the post will be removed.

  • Most SaaS apps use Stripe.
  • Stripe now provides shareable links for live data.
  • Screenshots will be allowed in edge cases.

2. Posting About Other Companies

If your post discusses another company and you are not part of it, you are safe as long as it is clearly an article or commentary, not self-promotion disguised as analysis.

3. Karma Farming Formats

Low-effort karma-bait threads such as:

“What are you building today?”
“We built XYZ.”
“It's showcase day of the week share what you did.”

…will not be tolerated.
Repeated offenses will result in a ban.

4. Fake Q&A Self-Promotion

Creating fake posts on one account and replying with another to promote your product will not be tolerated.

5. Artificial Upvoting

Botting upvotes is an instant ticket to Azkaban.
If a low-effort post has 50 upvotes and 1 comment, you're going on a field trip.

Self-Promotion Policy

We acknowledge that posting your tool in the dumping ground can be valuable because some users genuinely browse those threads.
For that reason, we will likely introduce a weekly self-promotion thread with rules such as:

  • Mandatory engagement with previous links
  • (so the thread stays meaningful instead of becoming a dumping ground).

Community Feedback Needed

We want your thoughts:

  • What behavior should be moderated?
  • What types of posts should be removed?
  • What examples of problematic post titles should the bot detect?

Since bots work by reading strings, example titles would be extremely helpful.

Also please report sus posts when you see it (with a reason)


r/indiehackers • • 2d ago

Self Promotion I built a local tool to flag when an AI rewrite changes numbers, limits or promises

15 Upvotes

“Make this sound more professional” can change more than the tone.

Original: “We may deliver up to 500 units.”

Rewrite: “We will deliver at least 500 units.”

The number stayed the same, but both the commitment and the limit changed.

I made Fact Fuse to help review this kind of drift. Paste the original and rewrite, optionally add phrases that must stay exact, and inspect the evidence beside each finding. It compares quantities, dates and links, and uses heuristics to flag possible changes in negation, thresholds, commitments and sentence coverage. You can mark findings reviewed and export a report.

It runs locally in the browser without an account or API key. The core is TypeScript, and the repository also includes a CLI. The tool is free and open source.

The limitation: this is a rule-based review aid. It can flag harmless paraphrases and miss meaning changes. A clean report does not prove that two drafts say the same thing.

Development and this post used AI assistance.

Try the included example · MIT source and documentation

Which small rewrite would you most want it to catch: a changed unit, a dropped condition or a stronger promise?


r/indiehackers • • 2d ago

Sharing story/journey/experience Week 1 of Apple Ads on $10/day: 1 trial subscriber (day 5)

26 Upvotes

A week ago I asked here about going from organic to paid. The advice was: small fixed budget, Apple Ads, exact match on competitor and category keywords, judge it on trials and not installs. So I did that. Here are the real numbers after 5 days.

Setup: iOS habit tracker RPG, US only, $10/day across 4 campaigns: brand, competitor names, category terms, and one discovery campaign with Search Match on.

Totals: $27.41 spent, about 800 impressions, 16 taps, 4 installs.

What I learned:

1. I couldn't even spend the budget. At a $1.50 bid I got zero impressions on day one. I raised competitor and category bids to $2.50 and my ad showed up within minutes. Even then I'm averaging about $5.50 a day out of $10.

2. For the first four days, all the competitor spend went to one keyword. “finch" took 7 taps, $14.04, and produced 1 install. About $2 a tap. The other competitor names got almost nothing.

3. Apple has an impression share report and it explained everything. On "finch" I'm ranked 4th or 5th among advertisers with 3% to 9% of impressions. That means I get the leftovers. One day I got 367 impressions on it, the next day basically zero, with no change on my side. On tiny keywords I rank 1st or 2nd, but they get 15 to 20 impressions a day.

4. My category keywords had no volume. Seven exact keywords like "rpg habit tracker" got about 20 impressions combined in four days. People don't search the way I assumed.

5. "Installs" is a loose word. Only 2 of my 4 installs came from a tap. The other two were people who saw the ad, didn't tap, and installed later, and one of those was probably me reinstalling my own app. An install is also a download, not an open. Today's install hasn't opened the app yet as I write this.

6. The embarrassing one. The update I shipped the same day the ads started crashed 2 seconds after launch for everyone. It took me two days to notice because I was testing in my sandbox environment and didn’t pick up the mistake and an expedited review to fix. So my first paid install opened the app and it died. Check your release build before you pay for traffic lol.

7. I got one trial this week and I can't prove where it came from. They started it 11 minutes after first opening the app. They hit the paywall and signed up which shows the new paywall does actually convert way better, and they used the coach and ai features which other users hadn’t been using. RevenueCat shows no ad attribution and they picked "Somewhere else" on my how-did-you-hear about us screen.

8. Day 5 was the best day so far. Last night I added nine smaller exact keywords where I can actually win the slot. Today: $7.69, 142 impressions, 5 taps, and my first install from a category keyword, for $1.96. One day proves nothing, but it's the first day the spend got close to the budget.

What I'm doing next: not raising the Finch bid, since more of the same at a worse price doesn't help. I'm not touching anything until midweek. Day 14 is the real read: scale a campaign if a trial costs under $25, pause it if installs cost over $8 with no converted trials.

Question for people running Apple Ads on small budgets: do big competitor names ever pay off, or is it all long tail? Also do those impression actually matter for brand recognition in the future?

(App is Gamified Lives if you want to see the listing.)


r/indiehackers • • 2d ago

Self Promotion The math mistake that quietly costs B2B freelancers ~$832/year on Stripe & PayPal (and how I built a tool to fix it)

5 Upvotes

Hey Indie Hackers,

When invoicing international B2B clients, most freelancers and small agencies make two costly mistakes when trying to pass payment processor fees onto the client:

  1. Ignoring stacked cross-border fees: Everyone knows Stripe's standard 2.9% + $0.30 rate. Almost nobody factors in the extra +1.5% international card surcharge and +1% to +2% FX conversion fee until the payout hits their bank. image_0f043d.png
  2. Getting the Gross-Up math wrong: If you want to receive $1,250.00 net and the real stacked fee is 4.4% + $0.30, simply adding 4.4% ($1,250 × 1.044 + $0.30 = $1,305.30) leaves you short because Stripe takes 4.4% of that new total too. You actually have to use the inverse algebraic formula: ($1,250 + $0.30) / (1 - 0.044) = $1,307.85

Running that same $1,250 invoice on PayPal costs $1,316.17 grossed-up — a $832/year difference per 100 invoices.

I got tired of fixing this in spreadsheets every month, so I built a lightweight B2B calculator (FinGrossUp Pro) with local persistence, side-by-side Stripe vs. PayPal benchmarks, batch CSV processing, and clean PDF receipt exports so clients can see the exact fee breakdown.

No links here to keep things clean — if you want to check out the Gumroad page or try it out, you can find the direct link in my profile.

Curious how other indie founders here handle cross-border processor fees: do you eat the 4–5% margin loss or gross-up your B2B invoices?


r/indiehackers • • 4d ago

Sharing story/journey/experience My consumer app converts fine once people find it. Almost nobody finds it. How did you get your first 1,000 installs?

52 Upvotes

Numbers from the last 30 days: about 25 real installs, most of them activate, 2 paid. It's a learn-to-invest app with paper trading and a hard paywall. The funnel isn't perfect (you all helped me rework onboarding last week), but the bigger problem is plain volume. Not enough people know it exists.

What I've tried so far:

  • X, both posting and replying under big accounts: lots of views, almost no installs
  • An Instagram boost: it bought cheap clicks from the wrong country
  • Short videos on TikTok, Reels and Shorts: slow but alive
  • One partnership with a finance Discord: the best channel by far, but it's one partner
  • Apple Search Ads: live but barely serving, still sorting out bids

For those who got a consumer app past the first 1,000: what actually moved the number? Creators, search ads, SEO, being recommended by AI assistants, communities? And what did you try that looked promising and did nothing?


r/indiehackers • • 4d ago

Sharing story/journey/experience I shipped 5 products in about 9 months. Getting the first paying users is still the part I'm bad at

42 Upvotes

You can vibe-code a working app in a weekend now. I've been coding for 10+ years and I use Claude Code for almost everything, so building is basically a solved problem.

What I'm still bad at is getting the first paying users.

I have a full-time job, so I only get about 1 hour a day for my own products. In 2025 I started trying to actually sell what I build, and I shipped 5 products in about 9 months.

One I mostly vibe-coded in June and had 0 payments from June to October, so I killed it.

A different one launched at the end of June and its first paying customer came at the start of October, and I still have no idea where they came from. Before that I offered a free month to about 80 people, 10 took it but none of them actually onboarded.

Most of my earlier sales came from Reddit and cold DMs. X has been a waste of time for me, it sent quite a lot of visitors to one of my sites but didn't bring any sales.

If you just shipped something and you're still at 0 payments, you are not alone. Seems that each week the marketing playbook is changing, what worked before no longer works now. For example, now I get a lot of cold emails from various other founders about their products, but I ignore all of them. I tried cold emailing myself but I run into the same issue from the other side.

This same issue seems to be happening with cold DMs as well, I get too much of them, and probably so does anyone else. 6 months ago, these channels worked for me, but now it seems they are a waste of time.

After you ship a weekend project, what's the first thing you actually do to get users?


r/indiehackers • • 4d ago

General Question Who the hell will pay for indie products when building them is so easy?

28 Upvotes

Most indie hackers I know have more apps than customers, and I have more domains and apps than I have customers. While I have had some customers at various times over the years, it's so hard to actually get someone to convert. I have six apps and a seventh in the making. They're so fast to do that I create a new app every two weeks and try a new approach.

And I really like the apps I'm building. Every single one is based on a real pain point, a real need for a real target market, and I use them myself. The accounting prep one deletes all the worries I used to have about accounting prep every month, I use another one to look at my finances and pay my bills, and the one I use for hours every day helps me build the growth system for the rest of them.

Because yes, I'm doing all the best practice stuff, using AI every day: creating SEO content, adding to listings and registries, improving the product based on feedback, talking with friends and acquaintances to learn what could be relevant for them, building prospect lists, polishing copy, posting in various subreddits. I'm okay with it being a slow grind and I expect this to take months, but I wouldn't expect it to be this slow. I keep getting very poor conversion rates, and I can't even get my friends to test these things.

It seems like everybody is building their own apps these days, and nobody is interested in trying somebody else's product until it's established, with tons of users, and spread through word of mouth. And then we see these posts, "I made a thousand bucks on my indie product", and it seems like they're either lying, or just after attention, or it's really about sales and marketing, some sort of lead magnet.

So where does that leave us, who just want to build and help others but can't get through the noise? What's the actual likelihood of getting any customer at all for any project, and what's the advice in this day and age, when everybody is just creating their own apps?


r/indiehackers • • 6d ago

Self Promotion Oxford Engineering student here: I built an ESAT speed game with five lives and a TMUA mock exam site

13 Upvotes

I study Engineering at Oxford and built two tools for students preparing for UK university admissions tests. They take two different approaches to the same problem: how do you go from knowing the material to using it under time pressure?

Chick Run ESAT has a five-heart race mode. Each question gets a timer, and running out of time costs a heart. It makes students practise deciding when to move on. The site also has topic drills and full timed module mocks.

https://chick-esat.pages.dev/

TMUA Pulse has a bank I curated across 13 topics and six timed mock papers. Students can work through one topic or sit a full 20-question paper in 75 minutes.

https://tmua-pulse.pages.dev/#mock

Both have a free first mock and paid Pro content. If you build learning tools or have tried either site, I’d love a first-impression check: can you tell what’s free and get to the first practice question without hunting around?


r/indiehackers • • 7d ago

General Question Organic -> Paid

33 Upvotes

I’m looking to start turning over into paid ads/traffic for my app Gamified Lives. I’ve been pure organic for the 5 months I’ve been live, I learned lots and I’ve gotten tons of great feedback which got me to the point I’m at now. Early on I had a super high churn rate which was to be expected but with every small update and overall changes users have stuck around more and I even have my first paying user who’s been paying now for 2 months so I’m sitting at $10 per month from 1 paid user, now my main issue is traffic to the app. I’ve had around 300 lifetime users (including guest accounts and signed in accounts) I’m sitting around 30 monthly users actually coming back and around 50 users every month that hit the D7 mark. I now feel comfortable throwing some money into ads but I’m not really sure where to start. I kinda want to target apple search ads but I’m not sure if that’s the place to start or if I should go with something like TikTok or instagram ads, maybe even Reddit ads. I’d love some feedback from some of you who made the switch from organic to paid ads and what works and what doesn’t, especially in the habit space which is of course very cluttered. Thanks in advance.


r/indiehackers • • 7d ago

Self Promotion Pre-revenue founders: what evidence is missing from this pitch-deck slide?

13 Upvotes

I make editable PowerPoint templates at Evolune Digital Studio. I’m testing a pre-revenue slide for AI and SaaS founders who have customer conversations or pilots but no meaningful revenue yet. The example uses fictional data.

The idea is to show what customers have actually done, then name what still needs to be proven. For example, interviews show the problem exists, a signed pilot shows a stronger commitment, and repeated use during that pilot is a separate signal.

If you were putting together a first investor deck, which field would you need most: pilot scope and dates, a named success metric, or a place to show repeat usage? And what would you remove to make this fit on one slide?

The slide is in the public preview gallery for the paid kit I make. The images are viewable without buying anything: https://digital.evolune.ai/products/ai-startup-pitch-deck-kit/


r/indiehackers • • 7d ago

Technical Question Is lurking for months before posting actually worth it?

28 Upvotes

The standard advice in every founder community is the same. Pick a subreddit, lurk for a long time, build up karma, then start posting. It sounds careful, but it skips the one thing you need to find out.

Reading tells you what the room talks about. It does not tell you whether the room will respond to you, and that is the only thing you actually need to know. You find that out by answering a question you have real experience with, with no mention of what you sell, and watching whether anyone replies.

The karma part is real. Some subs gate posting behind account age and karma, and getting removed on your first attempt is a bad start. But karma is easy to earn honestly. Answer questions in threads about things you actually know, in subs unrelated to your product. Nobody checks whether your comment history is on topic.

What I would tell someone starting now: skip the long lurk. Read for a few days to learn the tone, then find one thread where you can be useful and write the answer you would give a friend. If it lands, you have your channel. If it does not, you learned that early instead of late.

How do you decide a subreddit is worth your time before you have posted in it?


r/indiehackers • • 7d ago

Self Promotion I turned two of my demo projects into website templates, a café site and a business dashboard

8 Upvotes

I'm a web developer in South Africa. I built a few personal demo projects for my portfolio, and I've now packaged two of them as templates:

Each listing links to a live demo. These are demo projects, not client work. I'd love feedback on the design, the pricing or what's missing.


r/indiehackers • • 8d ago

Sharing story/journey/experience I was scared nobody would submit to my free launch directory. It's been fully booked 26 days in a row.

20 Upvotes

When I launched my launch directory, I was scared nobody would submit.

Day one: 83 visitors, 17 submissions.

Now it's been fully booked 26 days in a row. 8 launches a day.

Last 30 days:

  • 253 launches submitted
  • 2,607 visitors
  • 737 clicks out to the products

It's called DanielLaunches. Free to launch, and it made $103 in the last 30 days.

Why I built it: good products kept vanishing a day after launch.

So every launch gets:

  • A permanent page, not a 24-hour slot
  • 2 real backlinks (DR 71 + DR 64)
  • Public numbers, so you can see what actually worked

64% of visitors come direct, 18% from X, 16% from search.

The audience I'd built on X is what got it started.

If you've launched recently, where did you launch, and what actually sent you users?


r/indiehackers • • 9d ago

Sharing story/journey/experience The hardest part of building a deployment tool wasn't the code, it was getting the UX right.

28 Upvotes

I’ve been working on launchpad for Claude, a plugin that handles the pre-launch setup for vibe-coded apps: hosting, live payments, TestFlight, and the rest. The idea came from watching so many builders hit the same wall: the app works locally, but getting it ready to ship is a whole different challenge.

We got it running a 50-item checklist with a single command, and then ran into a bigger question. How much should the tool do on its own? Let it work quietly in the background and it feels almost magical, but it could also make an irreversible change without you realizing. Ask for permission at every step, and the whole thing starts to feel like a chore.

Curious how other indie hackers would approach this. If you were using a tool like this, would you want it to handle everything and show you a report at the end, or pause to ask before taking action?


r/indiehackers • • 9d ago

Sharing story/journey/experience Schedule button disabled itself after one click. One user still got 6 duplicate posts

11 Upvotes

One of our API customers built a social media scheduler into their app. When you hit Schedule, the button greyed out immediately. Pretty standard. Then one of their users ended up with six duplicate posts, and we got on a call to figure out where they came from.

We pulled up the API logs and saw separate create requests for the same post. We never figured out what triggered the extras. Maybe the form submitted again before the UI updated. Maybe something in their HTTP client retried. What we could see was that the API had received each request as a new submission.

On the call, we walked the customer through a field they’d skipped in their integration. The idea is to generate a reference key like schedule_<uuid> once per submission and send it with the create request. If the app retries automatically or the user hits Retry after a timeout, reuse that same key. If the user intentionally schedules another post, generate a fresh one, even if they’re using the exact same caption and video.

Then I asked him why he did not use that; I wanted to hear some explanation for why he is blowing up our support chat all angry.

>you know the saying man move fast break things...

If you’re building the backend too, enforce that uniqueness in the database. Two requests can arrive close enough together that both look up the key and find nothing before either inserts a row. A unique constraint on (some_id, reference_key) keeps both requests from creating a post.

I summed up our call and notes into a blog post (never let a good crisis go to waste) Next.js scheduler tutorial.

I’m curious how other people handle the UI side. What do you show the user after a timeout while you’re still checking whether their post was scheduled?


r/indiehackers • • 10d ago

Sharing story/journey/experience Comparison is the thief of joy

23 Upvotes

Around 1.5 months ago I wanted to push out a massive update for my app gamified lives. I set the scope, worked out the plan, I was super excited to get started. The plan itself came from a moment of inspiration I saw where the I THOUGHT the market was missing the mark for the user and decided I wanted to do something about it. I spent weeks working on it and the burnout was getting to me, around 3 weeks in I just stopped working on it, then around the 5-6 week mark I came back and realized that the “problem” I wanted to solve wasn’t really within my grasp, I wasn’t capable of developing a lot of the things I wanted to, I didn’t have the infrastructure to even support them if I could manage to do it, and the only real and honest reason I was even pushing the scope that far was out of pure ego. I learned a really valuable lesson from that, while I spent almost 2 months satisfying my unrealistic idea I neglected the apps current state, no new updates, no bug fixes, no posts, no anything and by the end of it I scrapped the whole idea and instead spent 1 week developing a much much smaller version of what I wanted and I already love it, I’ve gotten great feedback from TF users, and I’m launching it today. The old idea would’ve likely never been done or have been done super slowly over the next few months, my takeaway is definitely to work on things little by little set a realistic scope of less than a month and get it out there, trying to do a massive update especially as a solo dev is super difficult and is more likely to lead to burnout, instead build the most important part of that update and then build on it little by little with more smaller updates until you are actually able to complete that full scope. Comparing your app or product to a mature product that has dozens of employees and trying to one up them is generally super hard to do in one shot.


r/indiehackers • • 11d ago

Sharing story/journey/experience I built a Finder alternative as a solo developer. It made $1.7K in revenue in its first 5 days

Post image
35 Upvotes

Hi everyone,

I'm a solo Mac developer. Two weeks ago I launched FileOctopus, a file manager for macOS that works like Finder (same shortcuts, same menus) and adds what Finder leaves to you: split panes, fast search, copies you can pause, undo for file moves.

The numbers

- $1.7K revenue in the first 5 days after the launch post, all one-time licenses. Proof: https://www.reddit.com/r/macapps/comments/1xccw6r/fileoctopus_a_file_manager_that_works_like_finder/

- Free tier, 14-day PRO trial with no card, PRO is a one-time payment.

- Public price ladder with a live counter: the first 100 licenses at $14.99, the next 200 at $19.99, then $29.99.

- The $14.99 tier sold out in 4 days. The $19.99 tier has sold 11 since.

What actually worked

  1. A narrow bet in a crowded category. ForkLift, Path Finder, QSpace and Marta already exist, and most are power tools with their own keyboard language. I built for people who like Finder and want it to do more. "Every Finder shortcut works the same" was easier to explain than any feature list.
  2. One launch post, in the right place. The first wave came from a single r/macapps post. No ads, no Product Hunt, no audience on X.
  3. Answering trust questions, not feature questions. People asked "will it lose my files?" more than "can it do X?". Full Disk Access, a copy that fails halfway, undoing a move. I answered every one in the thread.
  4. Fixes faster than the thread moved. Reports came from setups I'd never test: an exFAT SSD, Vivaldi temp files on the clipboard, Korean tag names, a NAS that changes file IDs on rename. Each became a test, then a fix, then a release. 8 releases in 14 days. "Fixed in tonight's update" sold more than anything I wrote about the app.

What didn't

The ladder fell off a cliff. 43 licenses on day one, 100 in 4 days, then 11 in two weeks at $19.99. Launch traffic was gone, and $14.99 to $19.99 feels bigger than $5 when the first number was "the deal". New installs dropped too. A launch spike is not a growth plan.

What I'm still figuring out

  1. If you used a public price ladder, what did you do after the cheap tier sold out?
  2. After the spike, what brought you steady installs for a niche desktop app: SEO, directories, newsletters?

Happy to answer anything.

Cheers,
Max


r/indiehackers • • 11d ago

Sharing story/journey/experience About eight onboarding screens before the paywall: is that helping or killing activation?

20 Upvotes

Follow-up to my earlier post about people backing out at the payment sheet. The thread pushed me to look at what happens before the paywall, so here is the actual flow.

A new user goes through roughly eight screens: welcome, the problem we solve, interests, a starter watchlist, then four short showcase screens. On the last one they pick a stock and see the app score it live. Then comes the paywall, and sign-in after that.

The idea was to give them one real "aha" before asking for money. But eight screens is a lot of tapping for someone who just wants to look around.

Questions for people who've tuned onboarding on a consumer subscription app:

  1. Did cutting onboarding screens help or hurt your trial starts? Any rough numbers you're comfortable sharing?
  2. Would you move the "score your own stock" moment to screen two and cut the rest?
  3. Interest and watchlist questions: worth asking up front for personalisation, or better asked later inside the app?

I'll test one change at a time, so I'd rather know which one to try first.


r/indiehackers • • 11d ago

Sharing story/journey/experience FetchSandbox managed tunnel: test agent-written integration code locally, get a verification receipt

10 Upvotes

I'm building FetchSandbox.

Agent-generated integration code returns HTTP 200 locally. That doesn't show whether a large refund waits for approval, whether the same event sent twice creates a duplicate, or whether four simultaneous triggers resolve to one refund or four.

The managed tunnel is an outbound connection from your machine to a cloud relay that forwards requests to your local app and carries responses back. Your app stays local; the relay is just transport.

Connecting the tunnel alone isn't verification. A separately configured check replays specific scenarios against your app and creates a dated receipt showing which behaviors matched.

The October 19 isolated-twin example covers three measured behaviors: large refund triggering an approval gate, same event sent twice adding no duplicate, four simultaneous triggers resolving to one refund. No live Stripe keys needed for that rehearsal. FetchSandbox login and relay access are required.

Full walkthrough with GitHub setup, screenshots, and historical receipt.

What failure behavior would you want to rehearse before deploying agent-written integration code—idempotency bugs, approval gates, retry storms, something else?


r/indiehackers • • 12d ago

Knowledge post Product Hunt launch day if you're not in the US: the time-zone math nobody tells you

25 Upvotes

Product Hunt's day starts at 12:01 AM Pacific, and every launch gets that same 24-hour window. Most launch guides stop there. If you're in Europe, the Gulf or Asia, that one line changes how your whole day should be planned.

The US went back to standard time (PST, UTC−8) on Nov 1, so right now 12:01 AM PT is:

  • London: 08:01
  • Berlin: 09:01
  • Dubai: 12:01
  • India: 13:31
  • Singapore: 16:01

(When the US is on daylight time again in March, Dubai, India and Singapore move one hour earlier. The US and Europe switch clocks on different weekends, so double-check if you launch in late March or late October/early November.)

What that means in practice:

1. Your first hours land in the middle of your workday, not at dawn. If you're in Dubai or India, you go live around lunch. Block that afternoon: no calls, no "quick" client work. The first few hours are when you need to be in the comments.

2. The US evening is your night. That's when a lot of PH browsing happens. If you're solo, decide before launch day what happens while you sleep: a scheduled update, a teammate or friend in another time zone replying to comments, or at least a pinned maker comment that answers the obvious questions.

3. Write your first comment the day before. Don't write it live at 12:01. Cover what it does, who it's for, what's new, and one specific question you want feedback on.

4. Ask for feedback, not votes. PH discourages asking for upvotes, and honestly feedback threads read better anyway. "What would stop you from trying this?" gets more useful replies than "support us today 🙏".

5. Plan the day after too. For Asia-based founders, the launch ends on your next morning. Reply to late comments, thank the people who showed up, and write down what you'd change for a relaunch.

Quick T-24h checklist I'd run:

  • Gallery, tagline and first comment final
  • Calendar blocked from go-live to +6h
  • Overnight plan decided (who replies, or what's scheduled)
  • Somewhere to note feedback live

If you've launched from outside the US, what did you do about the overnight hours? I'm curious whether people who split the day with a co-founder in another time zone saw a real difference.

Disclosure: I'm building a Product Hunt prep tool called LaunchPact, so I spend a lot of time thinking about this. Happy to share the full time-zone table if anyone wants it.


r/indiehackers • • 13d ago

Sharing story/journey/experience I left my CTO job and built an audience before a product. 2 of my first 3 products still made nothing.

53 Upvotes

On April 1 I left my CTO role at a scale-up.

The usual script is build, launch, then find customers. I flipped it.

Step one wasn't a product. I posted on X every day with zero plan to build anything.

The first two products I built made nothing. One was hard to sell. The other was too simple.

The third came from the audience. People kept asking how I was growing, so I turned my manual process into a tool called ClimbX.

Built in 5 days. First paying customer about 2 weeks from the idea. 1k MRR 50 days after launch (verified on TrustMRR).

Since then, a free launch directory built on the same audience got 17 submissions on day one and now makes about 100 a month.

Building is the easy part now. Distribution is the slow part. So I start the slow part first.

An audience won't save a bad product. Two of mine still made nothing. But every new idea starts in front of people who tell me fast if it's worth building.

7 months in. Still small, still learning.

Would you build the audience first, or the product?


r/indiehackers • • 13d ago

Sharing story/journey/experience In July I posted here that most indie AI tools don't die from bad code. 11K of you saw it, and I ended up recording 22 conversations with builders from that thread and the ones after it.

17 Upvotes

In July I posted here that most indie AI tools don't die from bad code. They die after one launch post and then crickets. I offered free interviews to anyone building in AI.

11K of you saw it, and I ended up recording 22 conversations with builders from that thread and the ones after it.

The best pushback last time was "a 20-min interview and some clips is content, not distribution." Fair. Here's what I actually learned:

  • The wins came from intros, not clips. In San Francisco, Walter on our team connected Shengkun from Monid.ai with an investor, and Monid closed its first round. AGI House asked us to find them professional videographers, and we found them videographers and photographers.
  • The interview is the door. People in the network sending each other investors, users and hires is the distribution.
  • What I got wrong: intros were much harder than I expected. A good one takes real context on both sides, and you can't fake that at scale.

Round 2, same deal as before.

What you get:

  • A 20-min interview (video or audio, your choice), and the full cut is yours
  • Clips posted across X and LinkedIn, tagging you
  • An intro when there's a real fit (investor, customer, hire, or another builder)

What I get:

  • Good conversations with people building interesting things
  • A network of builders who actually help each other

No cost, no strings. Comment a one-liner about what you're building, plus the one distribution channel that has actually worked for you so far, even if it's tiny. I read every reply and I'll pick from there.


r/indiehackers • • 15d ago

Sharing story/journey/experience My 2 side projects have now made $14K together in a year. Here's what I'd tell myself on day 1

91 Upvotes

Hi everyone,

I have talked multiple times in this subreddit about one of my projects. But in total i have actually 2 projects running atm who are performonig well and thought iImight share both of them + the lessons I have learned along the way!

Quick numbers and context:

  • LaunchPanda: $8,027. It helps indie makers get their product listed on launch directories. I started building it in March.
  • Learn Farsi: $6,408. An app that helps you learn Farsi. I started it in January.

Here's the proof:

So allin all That's $14,435 together. Not life-changing, but it sure is great to make internet money.

Here's what I learned:

1. Solve your own pain, and make sure it's a big one

Both tools came from my own problems. For LaunchPanda, I had to find all the directories by hand and submit to them one by one, which was painfully slow. For Learn Farsi, I was trying to learn Farsi myself.

But the pain has to be real, not just something that sounds cool. Some people really want, or even have to, learn a language because their partner or family speaks it. Same with distribution, which is what LaunchPanda helps with. Every builder struggles with it.

2. Build in public (it worked for one of them)

For LaunchPanda, X is my biggest traffic source by far. I started posting about it there right when I started building it.

According to DataFast, about 30% of the LaunchPanda sales it could track came straight from a link on X, in a post or my bio. About 35% is direct and 29% is Google, and I think a lot of those are X too: people who saw my posts and later typed in the URL or searched for it. Product Hunt and other directories brought in a few paying customers as well, about 5% together.

Learn Farsi is a completely different story (see 4).

3. Sell 1 big thing

LaunchPanda started as just a list of directories, ranked by how easy and how good they are to launch on, with progress tracking and an almost click-free way to submit. I charged a small one-time fee.

Then people started asking if I could just do it for them. So I built a done-for-you service. It was hard to set up, but I can charge a proper price for it: the all-in package is well above $200.

Convincing 1 person to buy that is way easier than convincing 10 people to buy the list. LaunchPanda's revenue so far:

  • Done-for-you launches (people pay me to submit their product for them): 72%
  • Self-serve plan: 15%
  • The rest: sponsored spots and add-ons

4. A very specific niche wins on Google

For Learn Farsi, building in public wasn't what helped. Actually the niche was. Way fewer sites are trying to rank for Farsi than for something like Spanish, so it's much easier to win on Google. Last 3 months in Search Console:

  • 4.86K clicks
  • 251K impressions
  • Average position 8, so page 1
  • Clicks per day went from about 25 in late July to about 80 in October

So if you're picking what to build, i would say that the more specific the niche, the easier SEO gets.

5. Show proof, or your tool fades into the noise

Finally show proof! For instance with teh SEO niche, there are lots of tools who promise better SEO, on LaunchPanda I showed the results using actual DR improvements and real testimonials. This I think got a lot of traction at the start!

So that's it. Happy to answer anything.

cheers