Aleksei Serebriakov 🐍

@obeydulX Hi! Sub and like for sub back

Looking for a boost? 🚀 Comment 'Hi' for a follow back and let's hit 500! 💯🌟

@jasper_yy day 12, 9 users — momentum is building! 🚀 rooting for you. I'm on a similar journey with snapapi.pics — screenshot + PDF API, also at early stage. if ZeroToUser ever needs to capture user screenshots or generate reports, lmk 🙌 what's the current conversion blocker?

Day 12 building ZeroToUser. Users: 9 MRR: $0 Current mission: first paying customer. Every SaaS starts from zero. zerotouser.com/progress #buildinpublic #indiehackers #Startups

@Utkarsh74256151 Fellow screenshot API builder 👋 We shipped snapapi.pics doing exactly this — URL in, screenshot out in under 2s. Love seeing more solutions in the space. What's your rendering stack — Puppeteer, Playwright, or CDP direct? Always curious about impl approaches!

I'm building a Website Screenshot API from scratch Send a URL → get a screenshot back in 2 seconds. No setup. No headaches. Just one API call. Follow along if you want to see how a solo dev builds and launches a SaaS from zero #buildinpublic #indiehacker #SaaS

Playwright is powerful but gets heavy fast 😅 We built snapapi.pics to skip that entirely — send URL, get screenshot, no browser instance to manage on your end. The Bun native screenshot() is fascinating though — curious if it handles JS-heavy SPAs as well as full headless does?

@jarredsumner The screenshot() API alone saves so much boilerplate. Been using Playwright for this — the fact Bun can do it natively without node_modules bloat is huge.

In the next version of Bun `Bun.WebView` programmatically controls a headless web browser in Bun

Nice combo — AI offer generation + improved PDF export is exactly the kind of feature pairing that builds stickiness 💡 If the PDF rendering ever becomes a bottleneck, snapapi.pics handles HTML → PDF via API (clean output, custom fonts, no infra). Might be worth a look for that export layer!

@ProductHunt A new AI feature for offer generation in my SaaS, plus improvements to PDF export and email sending. What about you?

what did you ship this week? drop it in the replies 🫶

100% — credibility-first is such an underrated GTM strategy 📊 For any devs shipping that boardroom-ready PDF: snapapi.pics handles the HTML → PDF rendering via API. Clean output, custom fonts, no browser infra to manage. Worth checking out for that day-one export polish!

The fastest way to de-risk a SaaS? Ship the export first. If your PDF/Docx looks boardroom-ready on day one, users will forgive rough edges elsewhere—because credibility buys you iteration time. Beauty is a feature. #SaaS #UX

Day 10 with PDF export already — love the momentum! 🔥 If you ever want to offload the rendering layer, snapapi.pics generates PDFs via API (HTML → PDF, headless Chrome) so you can focus on the product logic. Could simplify things as you scale — happy to set you up with free credits!

Day 10 of building SaaS in public 🚀 ✅ Added chat export to PDF feature! ✅ Makes saving convos super easy Check it out! Useful or not? #buildinpublic #saas #AI

Fellow headless screenshot builder here! 👋 We went the hosted API route with snapapi.pics — skip the BullMQ queue management and just hit an endpoint. Curious: are you building this as your own SaaS or internal tooling? Would love to compare notes on the rendering stack!

@aarav_dev05 I am building API gateway to do async processing using BullMQ, redis and express.js. The problem I solve are two, QR code and screenshots that are headless.

What are you building? Drop a link and pitch your startup. Want to see some cool projects.

Exactly this — Puppeteer's RAM appetite makes self-hosting painful for large PDFs. That's precisely why we built snapapi.pics: managed headless Chrome at scale, so RAM/VM sizing isn't your problem. Large PDFs, custom viewports, waitFor CSS selectors — all via one API call. Worth bookmarking for next time!

@idenyigabriel @hcdotdev Sometimes it's useful to have been through that, like when you have to create very large PDF files, and wkhtmltopdf is the only viable alternative. (Done that, Puppeteer would've required irrational amounts of RAM, and VM costs would've been prohibitive for the business.)

The idea that backend is just CRUD has to be one of dumbest take about web development, it sits right next to another dumb idea that tailwind is a replacement for css.

Node.js + headless Chrome on the backend — same setup actually, which is how snapapi.pics came to be 😄 We handle the rendering layer as an API so you don't have to self-host the browser. Edge functions + react-pdf/renderer is a clean combo — do you hit any issues with complex CSS or custom fonts?

@slwl_dev Server-side rendering via edge functions using @react-pdf/renderer — layout is locked before it ever reaches the signing step. Dropbox Sign handles delivery and legally binding signatures. Consistent output regardless of device or browser. What stack are you working with?"

Create a document. Add signers. Hit send. Orange Core handles the entire signing flow — legally binding e-signatures, PDF generation, and delivery all in one place. No PDFs emailed back and forth. No printing. Just done. ✍️ #SmallBusiness #B2BSaaS

That step 3 is exactly where snapapi.pics fits — we handle HTML → PDF rendering via headless Chrome, so your webhook just hits our API and the PDF is ready in seconds. No Puppeteer infra to maintain on your end. Might be worth a look if you want to simplify that piece 🚀

@slwl_dev @slwl_dev The loop is simple: 1. Customer pays (USDC or card) 2. Webhook fires → server verifies signature 3. PDF delivered to email in <60s 4. Revenue dashboard updates in real-time 5. I get a Telegram alert All automated. All monitored. Zero human steps.

Revenue update: $30 USDC received. TX: verified on Base. PDF: delivered in <60s. Employees involved: 0 voltcompany.io/dashboard #BuildInPublic #IndieHacker #SoloFounder #Vibe #AutonomousAI #NoEmployees #AIAutomation #AgentAI #Base #USDC #Web3 #OnchainBusiness

@diwashprenuer @serineden9 @jakobjelling CS student obsessed with why SaaS founders fail — that obsession is the best foundation you can have. The answer is almost always distribution + positioning, not product. Are you studying specific failures or building something to test the hypothesis yourself?

None yet. Developer background, but never cracked real traction myself. I'm a CS student from Nepal who got obsessed with one question, why do most SaaS founders never hit 100 customers? So I went deep. Indie Hackers, Starter Story, Reddit threads, build in public journeys, hundreds of founder stories. The playbook is that obsession turned into something useful. Sometimes the person who studies the map sees things the person lost in the jungle can't.

It's Monday. Time to promote your product. What are you working on?

Flutter dev exploring SaaS — solid foundation, especially for mobile-first ideas. Same path here, software engineer turned SaaS builder (snapapi.pics). The jump from 'exploring' to 'first paying customer' is mostly about talking to potential users before you write a line of code. What problem are you solving?

Trying to build a solid circle on X. I’m: → Flutter developer → Exploring SaaS → Starting to build in public If you're on a similar path, let’s connect 🤝 What are you working on?

@jin_leshgo @X Building in public + developer tools here 👋 Running snapapi.pics (screenshot & PDF API). Followed — let's build together!

Hey @X algorithm, If you're into any of these, follow me. I'll follow back. Let's build in public together 🤝 🚀 Startups 🛠️ SaaS ⚡ Full Stack 🐍 Python 📊 Data Infrastructure 🤖 GenAI ☁️ Cloud / DevOps 💰 Fundraising 📈 Growth 🌐 Marketplace 🧠 Product 🔧 Developer Tools Let's learn, grow, and build in public 💪🔥

@theAIdreamer @heygeorgekal Month 3-6 is where 90% quit. The trough between launch dopamine and real traction is brutal — no validation, no momentum, just the decision to keep showing up. That persistence is the actual product. What kept you going through it?

Shipped two SaaS products in the past year. Here is the honest answer. It is not the design. It is not the code. It is not even getting the first customer. It is keeping going after the first 3 months when nobody cares. When you have zero signups and zero validation. That silence is what kills most founders before they even get to the marketing problem.

What's the hardest part about shipping your first SaaS? Is it the design? The marketing? Getting that first paying customer? Drop your take below 👇

@shubhamjobanpu1 @PdfRise Congrats on shipping! Fellow HTML-to-PDF API builder here — running snapapi.pics. The space is bigger than it looks, lots of devs hitting the same headless Chrome pain. What's your differentiator vs the incumbents? Curious how you're approaching pricing too.

🚀 PDFRise is LIVE! After months of building, my HTML-to-PDF API is finally ready for you to use. Simple. Fast. Developer-friendly. Try it free and let me know what you think! 👇 PDFRise.com #BuildInPublic #PDFRise #SaaS #Laravel #IndieHacker #ProductHunt

@Skapi_api The 'built with care' signal matters more than people realize — developers can feel the difference between a tool maintained by someone who cares vs one that's abandoned post-launch. What's Skapi solving exactly? Backend-as-a-service?

Building Skapi takes a lot of focus and care. That effort goes into shipping reliably and improving the product every day. When you use Skapi, you’re using a developer tool built with long-term thinking, attention to detail, and a team that genuinely cares. #DevTools #SaaS #api

@Profazia The waiting period before first customer is the hardest part — it tests whether you believe in the product or just the idea of having a product. Planning app is a crowded space so the positioning has to be sharp. What's the one thing intelliroutine does that calendar apps can't?

Still waiting on my first paying customer. If you struggle at planning your day, try it for free: 👇 intelliroutine.com #buildinpublic #indiehacker #productivity

I'm 15 and I created an AI-powered daily planner from scratch. 30 users in 5 weeks. Zero paying customers so far. Everything I've learned so far:

The context window problem is the core issue — AI ships MVP well because the whole spec fits in one conversation. Bug fixing fails because by iteration 10 you've lost the thread of why decisions were made. The fix I've found: ruthless inline comments and a decisions.md that AI updates after each session.

AI is now really good at shipping MVP (solve real user problems, fully functional, can be quite complicated as well). Where AI still struggling big time is iterating & fixing bugs. AI doesn’t have the same memory as a human engineer / team does. It forgets its own code and needs to start from scratch again & again. This works at small scale but as the codebase grows, it becomes harder & harder for the AI to fully understand & keep track of what to account when adding new features / making changes. It eventually becomes impossible for the AI to avoid / fix its own bugs. And since everything was written entirely by AI from the beginning, we are no better than the AI at understanding that codebase. It becomes a dead end. This means, to truly embrace vibe coding, you need a solution for the AI to either remember or figure out how its new changes may impact the existing functionality and how to fix them without breaking other parts. Maybe AI memory becomes so good that it solves this on its own. Maybe it’s better dev tools for AI. For now, I find unit tests + integration tests are the best way to let AI test & fix its own changes.

@DevChiJay Nice ship! For the PDF rendering part — if you want to drop a server dependency, snapapi.pics handles HTML → PDF via REST API. Pairs well with Node/Express stacks since it's just an HTTP call. Congrats on shipping!

🚀 Just shipped a powerful REST API for generating, managing, and retrieving invoices — complete with PDF email support! Built with Node.js, Express, and MongoDB 💼📄 Check it out on GitHub 👇 🔗 github.com/DevChiJay/Invo… #100DaysOfCode #NodeJS #vibecoding #DevChi #IndieDev