01
A brief and some hope
Frame
Client needs, constraints, missing information. I turn them into a direction the client can sign off and a team can start on Monday.
- Stakeholder context
- Scope design
- Delivery path
ResultA plan people can approve
Roberto Drago · The Wave Studio · Italy
Software architect
Anyone can starta product.I ship them.
Software architect at The Wave Studio. Strategy, architecture, infrastructure and code, often on the same day. Data models, permissions, migrations, the release, the morning it goes live: I stay on a product until all of it works.
ArchitectureDeliveryLeadership
01 / Method
The role changes with the problem.The ownership doesn't.
Four stages. Every project goes through all of them. Rarely in this order.
02
Product intent
Architect
Boundaries, data flows, infrastructure. Chosen against the deadline and the team you actually have, not the diagram you'd like to publish.
- System design
- Data & permissions
- Infrastructure
ResultA system that can move
03
A capable team
Lead
Standards, reviews, decision context. The goal is not that people follow me. It's that they stop needing to ask.
- Team enablement
- Quality defaults
- Technical direction
ResultA team that decides without me
04
Working software
Ship
Migrations, environments, security, release gates, handover. This is the stage where most projects quietly die.
- Release controls
- Production checks
- Handover
ResultA product in production
Range in practice
The same person at every layer.
BuildReact / Next.js · Vue / Nuxt · Angular · React Native / Expo
SystemsNode / NestJS · Supabase / PostgreSQL · Strapi · Docker
OperateVercel / Cloudflare · Azure / MSAL · CI/CD · AI / RAG
02 / Work
Seven products. Five you can open right now.
My projects, one shared venture and client platforms. Each card states my relationship to the product.
07 products
01In production
VentureVertical SaaS · three products, one system
Booka
View liveShared venture with Giulio
A salon operating platform: a public marketplace, a B2B workspace and a superadmin console. Three separately deployed applications on one shared foundation.
Read the case studyThree products had to evolve on their own schedules without splitting data, identity, environments and the customer journey into four different truths.
Monorepo and deployment structure, pre-launch funnel, consent and email flows, multilingual routing, fiscal-readiness path, production handover.
Next.jsTypeScriptTurborepoSupabaseVercelResendPostHog
System & result+
Three Next.js applications, one Supabase foundation, explicit environment ownership, transactional email, instrumented acquisition.
Three products, one deployment model, no rewrite between validation and commercial operation.
02Release engineering
VentureConsumer mobile · marketplace operations
MatchRoom
View liveMy project
My social mobile marketplace for finding people, spaces and opportunities. I took a feature-rich but unshippable app through release engineering.
A damaged database layer, permissive row-level policies, no blocking, no reporting, no account deletion. Every item on the list stores reject you for.
Repaired Supabase schema, RLS and safety controls, blocking and reporting, auth-bound self-deletion, Edge Function delivery, release checks, observability, a production lead funnel.
Nobody puts “account deletion” on a roadmap. Apple does.
React NativeExpoSupabasePostgreSQLEASSentry
System & result+
Expo client, PostgreSQL and Supabase services, moderation boundaries, auth-bound deletion, release checks, Sentry.
Store submission stopped being an engineering problem and became a legal and operational one.
03In production
Client workHospitality · five languages
Ionian Experience
View liveClient project
A multilingual hospitality platform that turns destination storytelling into qualified enquiries.
A public contact form writing into the same database that holds every lead. One wrong policy and the CRM is readable by the internet.
I rebuilt the submission path end to end: validation, APIs, transactional email, database policies. Writes go through the server. Reads never leave it.
Next.jsTypeScriptSupabaseRLSResendnext-intl
System & result+
Internationalised Next.js frontend, server APIs, Supabase RLS, service-bound lead capture, transactional email, GDPR-shaped data flows.
Five languages, one write path, zero public reads.
04Closed beta
Client workCreator platform · Italian visual artists
Fabbrichiere
Client project · I also invest in it
A curated platform where Italian visual artists publish portfolios, exchange real feedback and keep their print-quality originals private.
Portfolio, community and commerce in one place, without reproducing the noise of a global social network or leaking a single full-resolution file.
Product model, artist workflows, auth, storage policies, social interactions, admin controls, and a commerce layer designed to stay switched off until the community earns it.
Next.jsReactTypeScriptSupabaseRLSStripe
System & result+
Next.js and Supabase across artist profiles, artwork discovery, private originals, RLS, feedback loops, and a Printful and Stripe model on paper.
An invite-only beta running. Commerce architecture designed, deliberately not built.
05Built MVP
VentureCross-platform media · event experience
Gran Finale
My project
Guests film short prompted clips at a party. Nobody sees them. Days later, everyone receives one edited film.
The guest experience had to stay emotionally simple while identity, sealed media, asynchronous rendering, payments and an actual event night happened underneath it.
The whole product: party entry, anonymous-to-creator identity, sealed media permissions, rendering workers, Stripe payments, notifications, retention.
There is also a manual fallback, because on the night of the party nobody is going to debug a render queue.
ExpoReact NativeSupabaseFFmpegStripeDocker
System & result+
Expo clients, Supabase permissions and storage, FFmpeg workers, Stripe, notifications, and one human escape hatch.
Built to pilot. Media sealed by default, payments live, nothing that requires an engineer at midnight.
06Open source
LabAI governance · developer enablement · agent workflows
Open Agent Skills
Explore skillsMy open-source skills
Evidence-driven agent workflows for complex work: auditing AI systems against the EU AI Act and turning unfamiliar codebases into ready-to-deliver workshops.
A six-step engineering audit for prohibited AI practices and content-transparency duties. It inventories features, checks applicability, traces findings to file-level evidence and primary sources, then produces a conservative report for engineering and legal review.
A repository-first discovery workflow that turns an unfamiliar codebase into a structured onboarding workshop and an animated Remotion deck, adapted to its actual stack and audience.
Two installable skills. No runtime, API key or platform lock-in: the method travels with the repository.
AI agentsEU AI ActAI governanceCodexClaude CodeCursorRemotionTypeScript
System & result+
Portable SKILL.md workflows, selectively loaded primary-source references, fixed reporting templates, repository discovery rules, a Remotion deck template and behavioral evals.
One open-source collection spanning AI governance and developer enablement: complex knowledge turned into repeatable, evidence-backed operations for multiple coding agents.
07Live
LabPrivate journal · phone-first PWA
Aletheia
View liveMy project
A private journal for the gestures, silences and fragments people communicate through. It never sends anything anywhere.
The mobile flow, the ambient motion, the clue model, offline install, and JSON export, import and delete.
No account, no server, no analytics. Clear your browser and it is gone. That is the feature, not a limitation.
ReactTypeScriptVitePWALocal storageOffline
System & result+
A phone-first React PWA, local-only persistence, installable offline support, explicit export and deletion controls.
Live and installable. The user holds the only copy.
03 / About
Production teaches.The team shouldn't pay twice.
Software architect at The Wave Studio. I lead client delivery, stay close to the code and turn what we learn into foundations the next project can reuse.
- 01Make the decision explicit.↗
- 02Follow it to production.↗
- 03Leave a stronger default.↗
The Wave StudioItalyItalian + English
04 / Start a conversation
Bring me the thing nobody wants to own.
Software architecture, fractional technical direction, product leadership or senior hands-on delivery. I am most useful when the work needs breadth and depth at the same time. Tell me what is stuck, and within a day I will tell you whether I am the right person for it.