I design, build, and run a multi-tenant SaaS on my own: backend, frontend, bot, infrastructure, payments, and security. Most of my time goes into scaling Askar Apps and growing Ruby Verse, the first store built on it. When I'm not shipping product I do offensive security work, mostly web application pentests and .NET reverse engineering.
const gabriel = {
name: "Gabriel Bertolassi Barretta",
role: "Founder & Full-Stack Engineer",
company: "Askar Apps",
focus: ["Distributed Systems", "SaaS Architecture", "Payment Infrastructure", "AppSec & Reverse Engineering"],
stack: ["TypeScript", "Node.js", "Next.js", "Discord.js", "MongoDB", "Redis", "BullMQ"],
currently: "Scaling Askar Apps: dashboard, bot, and Askar Pay",
location: "Brazil 🇧🇷",
};A multi-tenant SaaS for Discord-based Roblox commerce. Store owners run, customize, and scale their Discord shop from a single dashboard, with real-time sync, a native PIX wallet (Askar Pay), and a full affiliate system.
Architecture
- Backend: Express + TypeScript + Mongoose + Redis + Socket.IO + BullMQ + Zod
- Frontend: Next.js + React + TypeScript + Styled-Components + React Query
- Bot: Discord.js + Mongoose + Express +
@napi-rs/canvas - Infra: SquareCloud, MongoDB (multi-tenant), Redis, Blob storage
- Payments: Askar Pay, the platform's native PIX wallet (balance, KYC, withdrawals, commissions)
Highlights
| Multi-tenant | Central registry plus N isolated guild databases with LRU connection pooling |
| RBAC | 16 granular permissions with fail-fast validation |
| Askar Pay | Native PIX wallet: balance, KYC, withdrawals, fee handling, reconciliation |
| Affiliate System | Chain-of-responsibility attribution (coupon › role › invite), GROSS/NET commissions |
| Real-time | Socket.IO presence, access sync, live panel updates via Change Streams |
| Resilience | AsyncLock → CircuitBreaker → Retry with jitter → timeout |
| Tested | 1,500+ automated tests across backend, frontend, and bot |
| Audited | Multiple security audits, all findings resolved |
Offensive security on the side: web apps, REST and GraphQL APIs, .NET reverse engineering, license and auth bypass, and full white-box engagements. Reports follow a wave-based methodology with PoCs, attack chains, and anti-findings.
- Web application pentesting: OWASP Top 10 applied, auth flows, payment and business-logic bypass, IDOR, XSS (stored/reflected/DOM), CSRF, CORS/CSP, rate limiting, WebSocket security
- API security: REST and GraphQL endpoint enumeration, JWT analysis (alg confusion, secret brute, replay), NoSQL/SQL injection, mass assignment, broken access control
- .NET reverse engineering:
dnlibstatic analysis,Harmonyruntime patching, single-file bundle unpack, ConfuserEx/Themida bypass, anti-debug and anti-VM evasion - License and auth bypass: KeyAuth crack methodology, Ed25519 native-patch, JWT forge, session storage analysis, full NoAuth builds
- Supply chain audit: auto-update mechanism analysis, signature verification gaps, dependency injection vectors
| Target | Type | Outcome |
|---|---|---|
| FPS aim-assist SaaS | White-box web + binary, 4 waves | 171 findings (17 CRIT · 49 HIGH · 52 MED · 33 LOW · 20 INFO), senior-audit reviewed 9/10 |
| .NET 8 license portal | Web + binary, NoAuth target | Full crack via 13-method IL patch + 34 findings (4 CRIT incl. supply-chain backdoor) |
| Roblox marketplace SaaS | Web black-box launch audit | 2 reproducible findings (DoS via malformed payload + affiliate-fee abuse) |
| Multi-tenant commerce portal | Auth flow + IDOR test | Login enumeration vectors + cross-tenant access PoC |
| Discord-commerce SaaS (Askar) | Internal multi-wave white-box | 10+ waves, ~150 anti-findings, 0 open CRIT/HIGH/MED |
Every engagement runs the same wave structure:
- Recon: stack mapping, endpoint enumeration via
OPTIONS, source and binary extraction - Auth + license: flow audit, token analysis, brute force where viable
- Business logic: core feature audit (cheat logic, payments, RBAC, and so on)
- Infra + compliance: backend analysis, LGPD/GDPR audit, supply chain
- Retest + attack chains: end-to-end exploitation PoCs after fixes ship
Deliverable: RELATORIO.pdf with an executive summary, the full findings catalog (CRIT down to INFO), anti-findings (defenses that held), attack chains, and recommended fixes.
Worked with me before, even on a short engagement? A short public note (a LinkedIn comment, a Discord testimonial, a GitHub thank-you) goes a long way, and I take on new audits. Contacts are below.





