Lesson 584 of 2116
Vercel, Supabase, and Resend as a Hermes Control Plane
Map a production-friendly control plane where Vercel receives requests, Supabase stores state, Resend sends mail, and a local relay handles private machine work.
Lesson map
What this lesson covers
Learning path
The main moves in order
- 1What the local Hermes build teaches
- 2control plane
- 3Vercel
- 4Supabase
Concept cluster
Terms to connect while reading
Section 1
What the local Hermes build teaches
This build lab focuses on the web control plane around a local or hybrid Hermes-style agent. The goal is not to copy a private machine setup. The goal is to learn the architecture pattern well enough to build a small, classroom-safe version.
A web control plane should handle UI, auth, webhooks, job queues, audit logs, and notifications while private desktop actions remain behind a local relay.
Compare the options
| Hermes pattern | Student build | Risk to handle |
|---|---|---|
| Name the boundary | an architecture diagram with Vercel, Supabase, Resend, local relay, and agent workers | putting service-role keys in the browser or expecting a serverless function to act like a permanent desktop controller |
| Keep the interface small | Start with one happy path and one failure path | Avoid a demo that only works when everything is perfect |
| Make the system observable | Log decisions, status, and errors in plain language | Do not log private data or secrets |
Build the small version
- 1Draw or write an architecture diagram with Vercel, Supabase, Resend, local relay, and agent workers.
- 2Mark which parts are user-facing, which parts are internal, and which parts require approval.
- 3Choose one low-risk workflow and implement only that workflow first.
- 4Add one failure case before adding a second feature.
- 5Write a short operator note: what the agent may do, what it must ask about, and what it must never do.
A classroom-safe skeleton inspired by the local Hermes architecture scan.
control plane flow:
browser -> Vercel API
Vercel API -> Supabase job_queue
local relay -> polls authorized jobs
relay -> executes approved local task
relay -> writes audit result
Vercel cron -> sends summary via ResendKey terms in this lesson
The big idea: control plane is not decoration. It is part of the product architecture students need before an agent becomes safe enough to use with real people.
End-of-lesson quiz
Check what stuck
15 questions · Score saves to your progress.
Tutor
Curious about “Vercel, Supabase, and Resend as a Hermes Control Plane”?
Ask anything about this lesson. I’ll answer using just what you’re reading — short, friendly, grounded.
Progress saved locally in this browser. Sign in to sync across devices.
Related lessons
Keep going
Creators · 50 min
Evaluating Agent Performance: SWE-bench, WebArena, GAIA
Numbers on leaderboards are seductive and often wrong. Learn the big benchmarks, their leaderboard positions, their recently-exposed cheats, and how to run your own evals.
Creators · 52 min
Red-Teaming Agents: Injection, Escalation, Exfil
An agent is a new attack surface. Prompt injection, privilege escalation, data exfiltration — these are no longer theoretical. Learn the attacks and the defenses.
Creators · 75 min
Capstone: Build and Ship a Real Agent
Everything comes together. Design, code, test, secure, and ship a production-quality agent with open-source code you can fork today.