Independent full stack developer based in Buenos Aires. Web sites, e-commerce, FiveM scripts, Discord bots — designed, built and shipped end-to-end. From simple landings to full sales platforms and gaming server tooling.
Every project solved a real bottleneck. Click any card to read the full case study — problem, solution, impact, and stack.
Four areas where I take projects end-to-end. Prices are starting ranges — quoting depends on scope.
Corporate sites, product landings, portfolios, institutional pages. Fast, custom-designed, no template-feel.
Online stores, product configurators, ordering systems with payments, admin panels and transactional email.
Server-side Lua scripts for RP servers — jobs, vehicles, economy, integrations with MySQL and Discord.
Custom Python bots, API integrations, internal webhook servers, automations that save hours every week.
Pick a service and the features you need. This is a floor estimate — we tighten the number on the discovery call.
Saves us both a discovery call. If your project lands here, I'm not your dev.
Four phases from first call to handover. Transparent timeline, weekly check-ins, code in your hands when we ship.
30-min call. We map the problem, the flows, who uses what, and what success looks like. I write back with my read.
Wireframes, proposed stack, milestones and a final price. You see exactly what you're paying for before signing anything.
I build end-to-end with weekly check-ins. Every milestone deploys to staging — you watch it grow in real time.
Training session, written docs, codebase + every credential transferred. Plus a 30-day support window for anything that surfaces.
I'm Santiago, independent full stack developer based in Buenos Aires. I work alone, pick clients carefully, and only take on projects where the engineering actually matters.
I work across custom web, e-commerce, FiveM scripts and Discord automations — software that replaces manual chaos with systems that run in the background. I diagnose the bottleneck, design the solution, build it end-to-end and hand it over working.
Stack-wise I lean on vanilla web tech plus cloud backends (Supabase, Cloudflare, Postgres, Edge Functions, async Python). No heavy frameworks unless the case demands it. No templates. No no-code that cracks on the first edge case.
I pick the stack per project, not the other way around. Vanilla web tech plus a serious backend solves 80% of business problems better than any heavy framework will.
A slice of what I keep public on GitHub. Most client work stays private — these are the things I can show.
Not demos or side projects. Every entry is a system running right now, in production, for a client who paid to have it built.
End-to-end build: multi-material configurator with size/colour variants, admin CRUD panel, quoting flow with payment validation, four transactional HTML emails, RLS policies, file storage for logos and receipts, real-time sync, 14 Playwright E2E tests.
Online store for limited drops. Editorial product page, checkout, admin orders panel, transactional emails, Chilean legal pages, schema.org SEO. Deployed on Cloudflare Workers — free-tier infra, zero lock-in, perfect performance.
Public web hub for a server with hundreds of active players. Rules by faction (police, EMS, mafia, mechanic), online store integrated with Discord bot, admin panel. Onboarding moved from scattered Google Docs to a proper site.
Enterprise Python async bot. 16 specialised cogs, MySQL pool, webhook server for the web store, ticket system with transcripts, application-flow whitelist, live stats embed, automated DB backups with rotation, zero-downtime cog reload.
If yours isn't here, hit the form below and ask.
Real reviews from real projects, moderated before going public.
A 30-minute call is enough to figure out if it's solvable, how, and what it costs. Send the form or hit any direct channel — both work.
I'll ping you the moment a slot opens.
End-to-end ordering platform for a personalisation workshop in Santiago.
AlfaImagen had been running every order through WhatsApp for years. Messages came in at 11 PM, on weekends, in the middle of dinner. A single quote took 10–15 back-and-forth messages to nail down: how many shirts, what colour, where the logo goes, what size, where it ships. Corporate orders — 100 polo shirts for a company — could eat two hours of discovery before they even had a price to send back.
Then there was the customer who opened Instagram at 11 PM with a clear idea in their head. They couldn't find a way to leave the order. They'd come back tomorrow and remember something else, or not come back at all.
I rebuilt the entire intake from scratch. Customers now configure the order on the site — material with size and colour variants, logo upload, embroidery placement, full Chilean shipping fields (RUT, comuna, region, postcode). By the time the order lands in the workshop, it's ready to quote.
The owner taps one button in the admin panel and the customer gets WhatsApp + email with the price. They accept, pay (cash or transfer with receipt upload), and the workshop confirms — all from the same panel. Four automated emails fire at the right moments. Products, prices and photos are edited from the panel, no code touched.
Online store for a Chilean streetwear brand running limited drops.
New streetwear brand with handmade products — limited drops, each piece unique. No online sales infrastructure at all. They needed to launch drops, manage one-of-one stock, and take payments without paying Shopify's monthly fees and per-sale cuts, and without getting locked into a platform they don't own.
I built an edge-deployed store on Cloudflare Workers. Editorial product page with gallery and brand storytelling, checkout, admin panel for orders and stock, transactional emails for every state, full Chilean legal pages (consumer law, returns, warranty), SEO with schema.org/Product for rich snippets in Google search.
Cloudflare's free tier covers the infra → $0/month while we stay within generous limits. The codebase is the client's — not the platform's. They can host it anywhere if anything changes.
Public hub plus store for a FiveM roleplay community.
A gaming community of hundreds of active players running entirely from Discord. Server rules lived in Google Docs that nobody kept updated. The internal store ran out of DM threads. Whitelist applicants asked the same questions every single day. There was no proper front door — onboarding was slow and chaotic.
I built a public hub that pulls everything into one place: navigable rules per faction (police, EMS, mafia, mechanic, Mosley), online store with products, admin panel, Discord integration via OAuth and webhooks. Editorial gold-noir styling with Playfair + Bebas to hold the server's brand identity together.
Net result: the community went from operating inside Discord to having an actual public face. Onboarding got around 10× faster. Staff stopped explaining the same five things over and over.
Discord ↔ FiveM ops system for a gaming community.
/whitelist add applied · 1 player added to the server.Staff was doing everything by hand: approving whitelist, opening and closing tickets, issuing sanctions, checking server stats, backing up the database. It took hours every day. People made mistakes. Different staff did it differently. There was no way to scale to a bigger community without burning everyone out.
I built an enterprise-grade Python bot, 100% async. 16 specialised cogs covering bans, economy, QBCore player lookup, hours worked, tickets, whitelist, vehicles, mafias, live stats, backups, automod, admin tools.
Serious architecture under the hood: connection pool over MySQL with aiomysql, HTTP client to the FiveM API with Bearer auth and retries, an internal webhook server that receives orders from the web store, zero-downtime cog hot-reload, daily-rotated file logging, a DEV mode that boots without MySQL or FiveM attached.