Clasho creator campaign platform

For Clasho, through WebThree · Since November 2025

Clasho runs campaigns where creators post about a brand on social media and earn rewards for the reach they bring. I have worked on it full stack since November 2025: the creator app, the API and database, the admin tools and the releases.

My part
Full stack: React front end, Node API, PostgreSQL schema and migrations, admin tools and deploys.
Stack
TypeScript, React, Vite, Node, Express, tRPC, PostgreSQL, Drizzle, Vitest, Storybook
Hosting
Heroku, Netlify, AWS S3 and CloudFront
The Clasho home page on desktop: the campaign headline, its sub-line and a Start Earning button.
Clasho’s home page.

Campaigns

A visitor lands on the live campaign and can join from the first screen. Behind it is a campaign editor I built for the team: missions, guidelines, prize pools and tags, and a duplicate action that copies a campaign with its media on S3.

Admin tools

Review queues for creators’ posts, settlement reports, email broadcasts to campaign lists, and an append-only audit log of every admin write.

The Clasho join screen: an email field or a Connect with X button, with the terms line underneath.
The join screen.

Sign-in

Creators sign in with email, X or Google, or with TikTok and Instagram. I moved sign-in from a hand-built X OAuth flow onto Privy, added TikTok and Instagram through Phyllo, and store their access tokens encrypted.

A partner deposit campaign

Creators make a small deposit with a partner and upload proof. The API traces each deposit on-chain and triages the proof for review, and admins pay approved rewards in one batched Ethereum transaction. It went to production through a guarded launcher, with a database backup first.

Scoring and claims

Posts are re-scored from X data, with a backoff that reads older posts less often to cut API calls. Winners claim rewards on-chain, and the API refuses any claim that points at a contract other than the campaign’s own.

Releases

Pull requests merge into main and deploy on their own: the API to Heroku, the front end to Netlify. CI gates each merge on the deterministic tests, and assets are served from S3 through CloudFront.