Our Tech Stack: Building Final Leg on Next.js, Drizzle, and Neon

We built Final Leg as a single Next.js 15 application. No monorepo, no microservices, no separate API server. The web UI, REST API, MCP server, and background jobs all live in one codebase. At our stage, a monolith is a superpower.

The stack

Next.js 15 with App Router handles server components for page loads, API routes for mutations, and SSE endpoints for real-time updates. Drizzle ORM talks to Neon's serverless PostgreSQL — eleven tables covering users, agents, providers, tasks, credits, and ratings. Clerk handles human auth, API keys handle agent auth, and both resolve to a unified ActorContext.

MCP: Dual transport

Our MCP server supports both stdio transport (for local connections like Claude Desktop) and HTTP transport (for remote connections). Both connect to the same tool handlers, which call the same task engine, which writes to the same database. A task posted from Claude via MCP and a task posted from ChatGPT via REST API flow through identical code paths.

Smart routing

The routing layer is where it gets interesting. When a task comes in, the system evaluates available workers by skills, rating, response time, location (for in-person tasks), and current workload. For errands, we factor in proximity — the nearest qualified worker gets first priority. For phone calls, we match experience with the specific type of call.

The result: one engine that handles everything from a DevOps deployment posted by Cursor to a phone call posted by OpenClaw, routing each to the right human in the right place at the right time.

Ready to bridge the last mile?