Flagship · AI workflow operations
live productionAI Workflow Studio — from workflow idea to observable production run
I built a standalone operations console for creating and finding agentic workflows, starting authenticated runs, and following each execution stage live. It turns the portfolio’s AI story into a working product surface rather than a static prototype.
AI Workflow Studio
Execution inspector / production
Production path · portfolio → studio → backend → Supabase
Production system path
- 1Portfolio
Introduces the case study and routes visitors to the live product.
- 2Workflow Studio
Renders workflows, metrics, run controls, and the live execution inspector.
- 3Go backend
Owns admin sessions, mutations, SSE, rate limits, and audit behavior.
- 4Supabase
Persists workflows, executions, and execution stages through the backend.
Workflow lifecycle
SSE
Security boundaries
Session
Shipped outcomes
Shipped
The problem
Agent workflows become difficult to operate when definitions, execution state, approvals, cost, and failures live in separate tools. A useful studio needed a clear workflow inventory and a trustworthy, execution-specific timeline without placing backend credentials in the browser.
The solution
A responsive Next.js control plane backed by the portfolio Go API. Public overview data remains resilient, while protected run controls use an admin session. Persisted stages arrive through a same-origin SSE proxy with validation, reconnect, and a safe fallback.
Workflow lifecycle
- Searchable workflow inventory with status filters and persisted execution history.
- Execution-specific stage timeline streamed over SSE, with reconnect and fallback states.
- Operational signals for run volume, success, latency, and recorded cost.
Security boundaries
- Authenticated run mutations are proxied by a session-backed BFF that forwards only the named admin cookie.
- Backend mutation rate limiting and persistent audit records protect and trace studio actions.
- The browser uses same-origin routes; backend credentials and internal origins stay server-side.
Shipped outcomes
- Live at studio.panyakorn.com as a separate, responsive production application.
- CI runs tests, lint, build, and deployment-script validation before publishing an immutable SHA-tagged image.
- Health-gated VPS deployment automatically restores the previous image on failure and supports manual SHA rollback.
Next.js 16 · React 19 · TypeScript · Go · Supabase · SSE · Docker · GitHub Actions
View backend source ↗custom-ai-skills and n8n/workers are planned integration points for reusable agent tools and long-running jobs; this case study does not present them as part of the currently shipped Studio runtime.
