Relay

• 

  Relay Architecture

Inspiration:

As a solo founder already building an AI SaaS platform, I kept noticing the same pattern across teams: support questions, meeting prep, and reporting all pull people into different tools, and none of those tools talk to each other. I wanted to see what a single, intelligent entry point could look like instead — one place where any request gets understood and routed to exactly the right specialist, automatically.

What it does

Relay is an orchestrator that takes in any business request and routes it to the right specialist agent behind the scenes — a support agent for customer questions, a meeting prep agent that understands each department's context and prepares tailored briefs so teams walk into meetings already organized, and a report agent for department-scoped reporting. Access is role-based across customers, team members, and admins, enforced at the database level with row-level security, so each person only ever sees what they're permitted to.

How I built it

The entire application — authentication, role and department structure, database schema, row-level security, and every workflow — was built end-to-end in Codex, across a single continuous build session.

Challenges

The biggest one was budget. The orchestrator and each specialist agent were designed to run on GPT-5.6 for classification and generation, but I wasn't able to fund live API calls for this submission. Rather than fake it, I chose to be upfront: the full routing and agent logic is built and ready to run, but this demo shows the application and design, not a live model connection.

Accomplishments

I'm proud that the core product — the auth system, the permission boundaries, and the full workflow across three distinct use cases — works cleanly today, and that the orchestration layer is fully designed and coded even though it isn't live yet.

What I learned

Building the permission and role architecture taught me a lot about designing systems that need to serve very different audiences safely from one entry point, without leaking data across boundaries.

What's next

Fund the API layer, connect the orchestrator and agents live, and test Relay with real teams to see how much manual coordination it actually removes from their week.

Built With

• codex
• gpt-5.6
• level
• next.js
• openai
• postgresql
• react
• row
• security
• supabase
• tailwind
• typescript
• vercel