Oscar Quintero - ArkandSoft

Oscar Quintero - ArkandSoft

ArkandSoft CEO, Building my first SaaS

About

A graphic/web designer that decided to move on and learn more about AI and finally creates somethig meaningful for everybody.

Badges

Gone streaking 10
Gone streaking 10
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Maker History

  • Auditly
    AuditlyFind the security holes in your site before attackers do
    Nov 2026
  • 🎉
    Joined Product HuntSeptember 20th, 2026

Forums

Auditly - Find the security holes in your site before attackers do

Auditly checks your site the way an attacker would: exposed .env and .git files, API keys in your JavaScript, open Supabase tables, weak headers, vulnerable libraries. Verify your domain, get a PDF with the urgent issues on top and the fix next to each one.
•

2mo ago

Vibe coders: how do you handle security for apps that touch bank/tax data?

I've been building a SaaS with Lovable + Supabase that handles pretty sensitive stuff bank data via Open Banking, tax-related info. It's still in beta with very few users, but I want to get security right before opening it up more.

I know the basics (HTTPS, not exposing API keys in the frontend), but I'm not confident I've covered what actually matters for something handling financial/tax data.

For anyone who's dealt with this:

What would you consider the absolute minimum before letting real users connect their bank accounts to something you built solo?

•

2mo ago

I vibe-coded my first real project — here's what actually happened

I've been a full-stack dev for 4+ years (React, Next.js, Node, NestJS), so I went into vibe coding thinking it'd just be "coding but faster." It wasn't quite that.

I run an independent practice building for small agencies and fashion/retail brands, and I started leaning on AI tools (Cursor, Claude Code) to move faster on client work. The first 60-70% was genuinely magical scaffolding, boilerplate, even decent architecture suggestions came together way quicker than writing it by hand.

Where it got messy was the last stretch auth edge cases, a deployment config the AI kept "fixing" back to broken, and a couple of times it confidently rewrote logic I hadn't asked it to touch. Being a dev already, I could catch it and course-correct, but I kept thinking about how differently this would've gone for someone non-technical.

Curious what this community's experience has been:

View more