I run OpenOwl, an MCP server that lets Claude, Codex, and other AI assistants control your desktop (screenshots, clicking, typing, all that). We've been growing and I want to bring on affiliates before opening the program publicly.
The short version: you get 30% of every payment, every month, for as long as your referrals stay subscribed. Not a one-time payout. Most SaaS affiliate programs I looked at offer 25-30%, so I wanted to come in higher since we're early and I'd rather give more to people who get in now.
There's almost no public content on how to monetize a Chrome Extension.
Google invited us to do a podcast about it, sharing our learnings on how two bootstrapped guys grew Pretty Prompt to 40,000 users, 25% on annual plans, with ~7% weekly growth, with no VC money.
We recently implemented custom domain support in Inquir Compute, and it feels like one of those features that really changes a platform from works technically to ready for production.
For me, custom domains are a core part of production-grade infrastructure. They are not just cosmetic they affect branding, trust, onboarding, and the overall developer experience.
I d be curious how others think about this in serverless and deployment platforms:
At what point do you consider custom domains a must-have?
What parts are usually the hardest in practice: DNS flow, TLS issuance, routing, verification, or UX?
Do you prefer keeping platform subdomains as the canonical entry point, or treating custom domains as the primary one?
Being consistent with content is harder than building features. Here me out. Shipping a feature feels productive. There s momentum. There s code. There s progress you can measure.
Content? You show up. You write. You post. And most days, nothing happens.
No clear feedback loop. No passing test case. No deploy notification saying success. Just impressions. Maybe.
Building product rewards logic. Content rewards patience.
but I recently came across an article describing how someone used Claude Code to access robot vacuum devices across 24 countries and potentially observe their environments.
I am a Computer Science student doing research into how solopreneurs and small startups create new apps and what their stack looks like. Particularly, I'm interested in how you handle things like authentication, billing, and permissions/authorization in your apps.
Let me know what you're working on below and how you're going about it -- I'd love to connect for some quick calls to learn about your product and talk about your process in building it!
When I first started, I believed that as long as I built a great product, it would naturally become popular. But as I zoomed out, I realized the market is incredibly competitive. Having a good product alone isn t enough to truly convince users.
That s when I began building my presence on social media creating content about myself, sharing my journey, and talking about the product I m building. I ve come to see this as a very effective way to build trust and spark genuine interest not only in what I make, but also in who I am as a founder.
I recently saw a marketer with 10k+ followers launch and finish 6th with 348 upvotes. They followed a proper pre-launch and post-launch plan, did everything right, and still the outcome felt unpredictable.
Now I m launching @Curatora next week.
I m not a marketer. I have a little over 1k followers. Of course, asking for support helps. But I also keep hearing that a large part of the Product Hunt community shows up mainly for their own launch, then goes quiet until the next one.
That makes me wonder: how much of success here is strategy, and how much is timing and network effect?
