I'm Zaur, a solo developer in Cologne. Under synexa labs I build small, focused apps, each one starting from a single concrete problem.
4 are live, 2 are in development. Here's the lineup:
A Stripe webhook bug that looks like an attack:
Your framework parses the body before you verify the signature. The bytes change, the check fails, genuine events get rejected.
Verify the raw body first. In a Next.js route handler: req.text(), not req.json().
@mynameis_quyen Building it because the existing apps were bloated or paywalled is a good starting point. How are you pricing CardioFit, one-time or subscription?
@naveen_saradhi_ Agreed. A manual version of the service is often the best validation, because people pay for the outcome, not the app. Do you charge from the very first customer?
@Travis_Jamison Profit-first suits most solo founders anyway. If you're not raising, a product only has to be useful to its customers and pay for itself.
@Iam_HITESH__ You can ship it in a weekend, then spend the next one on Stripe edge cases: webhooks arriving twice, failed renewals, deleted accounts still being billed. Still a great stack.
@Re_dev96 Trust is the slow part. Real usage, a clear refund policy and a visible human behind the product tend to help more than another feature. What's Origily for?
@attilatokolics More posting usually doesn't fix this, more specific conversations do. Pick one place where event organizers already hang out and talk to ten of them directly. Who is eventonite for, organizers or attendees?
@jmrphy SSO across your own sites is doable. The harder part is what those platforms quietly handle: failed payments, refunds, tax, email deliverability. Worth listing what each tool actually does for you before replacing it.
@ayoub_el77927 Stripe directly if you're fine handling VAT yourself, a merchant of record like Paddle or Lemon Squeezy if you'd rather pay a higher fee and skip the tax work. Most of the choice comes down to that trade.
@koxy_Dev Good topic. One detail people miss with Stripe: verify against the raw request body, not the parsed JSON, or the check fails even for genuine events. Re-fetching the object from the API before fulfilling adds a second layer.
@sxnVLR 60% of the way to beta is a good place to be. The last stretch is usually payments, emails and edge cases, so it's worth getting a few people in before it feels finished.
@abhinayguptha Same idea, yes. The first screenshot does the job a hero section does on a website: one promise, and everything else can wait for the second look.
A build-in-public lesson that isn't about code:
Every extra app splits your attention. Every extra link on a landing page splits your visitors.
Same rule both times. One product, one page, one clear next step.
@escarletdesign That's useful feedback, thanks. The 2% is the main reason to switch, so it shouldn't take digging to find. Was anything else on the page unclear?
Thinking of moving your digital products off Gumroad or Lemon Squeezy?
WorkSell: 2% per sale, no monthly plan, Stripe fees on top, money lands in your own Stripe.
https://t.co/ELjnLo2VVn
Synexa Labs is a one-person software studio in Cologne.
Right now: WorkSell for digital product sellers, Synexa Kit for SaaS builders.
Everything lives here:
https://t.co/OfJgxF82wS