Thravos — Participation Marketplace

The mandate

At Thravos, I own the technical execution of the Participation Marketplace — a platform designed to scale elastically to global demand while maintaining institutional-grade security. My remit spans architecture, team leadership, cloud strategy, and translating product vision into an executable engineering roadmap.

Bridge product vision and engineering reality. Ship an architecture the Series A/B round can be defended on.

Where I focus

A/B Round readiness Architected for Series A/B scale

2 Clouds AWS + GCP, mission-appropriate split

↑ Deploy velocity CI/CD + Agile rituals

↓ Burn rate Cloud optimization

Architectural oversight

Designed and audited distributed system architectures for Series A/B readiness, focused on high-availability and security. Decisions favor durability over cleverness — Thravos is money-adjacent, so failure modes have to be boring, well-understood, and observable.

Team leadership

Mentored and scaled cross-functional engineering teams — introduced Agile rituals and CI/CD pipelines that measurably raised deployment velocity. The team ships more, arguing less, with a shared vocabulary for architecture reviews.

Cloud strategy

Ran full-scale cloud migrations and infrastructure optimizations across AWS and GCP — reducing burn rate while improving system latency and uptime. Cost is a first-class engineering metric; every quarter we revisit the largest line items and ask why.

Product ↔ engineering bridge

Translated stakeholder requirements into concrete engineering roadmaps — the kind product managers can commit to and engineers can estimate against.

Surfaces of the platform

API + admin — core backend and operator console.
mobile-app — participant mobile experience.
new-website / athlete-landing / Agent-website — marketing and onboarding surfaces.
presale-dashboard + presale-api — presale round infrastructure.
ThravosSmartContracts — on-chain participation and settlement contracts.
avatar-microservice — image-optimization pipeline on AWS (SQS → ECS), auto-deployed via CodeBuild.
cron — scheduled jobs powering payouts and reconciliation.

What comes next

Series B readiness, deeper on-chain settlement primitives, and hardening the participant experience on mobile. If you’re building at a similar stage, let’s talk.