Five internal systems · One operator
Internal systems. Built end to end.
Not flat cards or screenshots. Each section below is one of the systems I run day to day, embedded live. Start with the Control Room — the hub I built to track and manage everything else.
Start the tourControl Room
Designed & built · 2026
A single command surface for every project I run. The Control Room is the face for the Polymarket dashboard and the three production tools below — bot status, deploys, content ops, and market intelligence all reachable from one place.
Why I was running five separate apps across different ports and tabs. The Control Room is what unified them — one matrix-style login, one launcher, real-time service status, and a consistent design language across the suite.
- Flask
- Vanilla JS
- WebSocket status
- Matrix auth
- systemd
Polymarket Trading Dashboard
Designed & built · 2026
Live operations console for five Polymarket trading bots — FVG, ARB, PTB, SM_ARB, and MM. Real-time PnL, positions, claimable redemptions, per-bot logs, latency probes, and one-click start/stop/deploy across the fleet. Every bot pipes fires, fills, claims and losses into a dedicated Telegram channel for instant push notifications.
Why Bots run on a remote VPS with SSH-only access. The dashboard pulls live status, polls the Polymarket Data API for completed-roundtrip PnL, and gives me a single pane to control everything without ever opening a terminal — and Telegram keeps my phone in sync the moment anything fires.
- Flask
- Polymarket Data API
- Chart.js
- SSH bridge
- Stale-while-revalidate cache
Content Hub
Designed & built · 2026
Full social media operating system — calendar planning, campaign structures, odds-led content ideas, AI drafting flows, reply tooling, and Telegram-ready workflows.
Why Marketing for a sports-betting product is content-velocity work. The Hub gives me a calendar, a draft surface, an odds-aware idea generator, and a reply pipeline — all in one app rather than five Notion pages.
- Flask
- Vanilla JS
- AI drafting API
- News + holidays feeds
Odds Terminal
Designed & built · 2026
Live odds movement, matchup analysis, futures snapshots, Polymarket cross-checks, and game-intel cards. A Bloomberg-style read on the sports-betting market — paired with a Telegram agent that automates the work of watching it: a 24/7 scanner that fires tweet-ready drafts with full news context the moment a signal hits.
Why I needed a terminal to see odds spreads, movement over time, and where money was actually being placed — all on one screen. Once that worked, I bolted on a Telegram agent to scan it 24/7 for divergence and volume signals, paired with a context agent that hands back tweet-ready copy the second the odds move.
- Flask
- Polymarket API
- Sportsbook feeds
- WebSocket updates
App Mockup
Designed & built · 2026
Arena scoreboard for live games — clean, dense, animated. The visual layer of the betting product, designed to feel like a real venue display.
Why An exploration of how the product should look when shown to a user, not an operator. Tight typography, live score animation, sport-aware accent colors.
- Vanilla JS
- CSS animations
- Live score feed
End of tour
Want to talk about how I'd build for you?
Same Codex/Claude Code workflow, same end-to-end ownership, applied to whatever you're building.