09 / Social commerce
Marketty
A social-commerce ecosystem — posts, threads, groups and a marketplace on one identity. I built the API and the launch site, and wrote the technical overview for investors.
- Role
- Technical lead
- Status
- Startup
- Period
- 2025 — 2026
- Type
- Social commerce
- identity across every surface
- 1
- entity types share one interactions module
- N
A / Architecture
Modular API behind a multi-surface product
One Fastify-backed NestJS API serves the Flutter app and the website, with identity, content, interactions and media as separate modules.
00 Clients
- Flutter app
- Website · Next.js 16
- Waitlist admin
01 Edge
- Fastify
- Global JWT guard
02 API modules
- Identity · OTP + Google
- Posts · threads · groups
- Interactions
- Feeds
- Media pipeline
03 Data
- PostgreSQL
- Object storage
- Waitlist store
Engineering notes
- 01
Big media, small requests
Chunked multipart uploads straight to S3, then a sharp and FFmpeg pipeline that produces web-ready images and video.
- 02
Interactions as a primitive
Reactions, nested comments, reposts and saves are one generic module that attaches to any entity — posts today, products tomorrow.
- 03
Feeds and identity
Newsfeed aggregation, email OTP and Google sign-in behind a global JWT guard, snowflake ids throughout.
- 04
A launch site with a back office
Next.js 16 landing page built close to the design, a Supabase-backed waitlist and a protected admin with search and CSV export.
B / Infrastructure & delivery
How it ships, scales and stays up.
- Storage
- AWS S3 with chunked multipart uploads for large media.
- Media
- sharp to WebP and FFmpeg for video, producing web-ready assets.
- Identity
- Email OTP and Google sign-in, jose JWTs behind a global guard; snowflake ids.
- Messaging
- Firebase Cloud Messaging and templated email.
- Website
- Next.js 16 on Vercel with scheduled jobs, a Supabase-backed waitlist and protected admin.