Tang Vu

Build in public | CS researcher | Shipping daily

[Tang Vu @tangvu_dev]

@forgebitz This hits different. Building keryx made me realize the best users are devs solving real problems, not people consuming content about building.

[Tang Vu @tangvu_dev]

@annieqyang Mobile has the built-in distribution channel (app stores) and push notifications. For SaaS, you're fighting for attention in a browser tab. Different tradeoffs depending on what you're solving for.

[Tang Vu @tangvu_dev]

@starter_story Selling to agencies is such an underrated move. They bundle your tool into client retainers and you get distribution without the direct sales grind. Smart playbook for any dev tool targeting ecom.

[Tang Vu @tangvu_dev]

@thdxr Right? The real fight is shipping. Frameworks are tools, not teams. I'm building keryx in public, more on my profile.

[Tang Vu @tangvu_dev]

@swyx Systems > Goals resonates hard. I try to build keryx around that too, repeatable shipping beats big launches every time. Long games compound.

[Tang Vu @tangvu_dev]

@pcshipp 6 months is still early. Revenue compounds once you find product-market fit. What's your app's retention looking like? Also building keryx in public, more on my profile.

[Tang Vu @tangvu_dev]

@DavidOndrej1 That's the speed you need for real-time agent loops. We've been pushing similar throughput with open models for our x402 flows, makes the micropayments feel instant.

[Tang Vu @tangvu_dev]

@sflorimm First, check if it's a connection pool exhaustion issue. Often misconfigured pool sizes cause this exact bottleneck.

[Tang Vu @tangvu_dev]

@Taniyatweets_ Web devs iterate fastest, hot reload, instant deploy, visual feedback. The whole stack rewards rapid experimentation. That loop is basically vibe coding's native habitat.

[Tang Vu @tangvu_dev]

@Sentdex 100%. OpenRouter changed how I think about model access. Vendor lock-in is the real risk, not capability ceilings.

[Tang Vu @tangvu_dev]

@marclou The 1.4x multiple on avg is interesting - feels low for SaaS but realistic for smaller marketplaces. That 33 day turnaround is actually pretty fast though.

[Tang Vu @tangvu_dev]

@RhysSullivan Solid stack. Instant search + agent accessible API is the right move for dev tooling. The nameserver flexibility is a nice touch too.

[Tang Vu @tangvu_dev]

@kylegawley Relatable. The indie SaaS grind is real. Building keryx taught me revenue validation > day-job salary when you're solving problems you actually care about.

[Tang Vu @tangvu_dev]

@thdxr This hits hard. We're so busy building the abstraction layer we forget to study the ones already shipping. The best agent framework might just be reverse engineering what works in the wild.

[Tang Vu @tangvu_dev]

@NEARProtocol Confidential computing on NEAR opens up interesting possibilities for private state transitions. Curious how this integrates with existing smart contract patterns.

[Tang Vu @tangvu_dev]

@hridoyreh Impressive run. One-person SaaS with that MRR is the dream. The simplicity of 'links in a tree' shows you don't need a complex idea, just a solid one that solves a real need.

[Tang Vu @tangvu_dev]

@tdinh_me Yeah, this framing is spot on. Services get wrapped, metered, and called like software. Exactly why x402 matters, lets agents pay per use without subscriptions.

[Tang Vu @tangvu_dev]

@CarlosBBuild 300 is a solid start. For paid conversions, try offering a small feature unlock after a usage threshold, gives users a taste of value before they commit. Curious what you're building with x402.

[Tang Vu @tangvu_dev]

@TTrimoreau Marketing SaaS is a crowded space honestly. The real gap I see is infrastructure, like micropayments and agent tooling that makes the whole stack cheaper to ship.

[Tang Vu @tangvu_dev]

@rauchg This is a clean mental model. The DX of 'just a file' is powerful. Reminds me of how we think about agent tool definitions in keryx, keeping it simple, declarative, and close to the code.