Ascend, the product Meshi grew out of, ran on three stacks: Python workers on Temporal for background workflows, a Python service for the AI agent, and a Next.js web app on Supabase.
Meshi runs on one. The web app is SvelteKit, the API is Hono, database access goes through Kysely on Postgres, and background work runs as Inngest functions. All of it is TypeScript, in one Deno workspace.
Built for AI coding agents
We build Meshi with many AI coding agents working in parallel, so we chose the stack for them.
In one language, an agent can take a feature from the database query through the API to the page in a single pass. One typecheck covers every layer, so a change that breaks something in another layer shows up right away.
Less configuration
Deno has formatting, linting, testing and TypeScript built in. Our first four packages need about five config files, one per package. The same setup on Node would have needed about fifteen. Fewer files means fewer settings for agents to keep consistent.
We write the database schema by hand in SQL, and Kysely generates read-only types from it. There is no schema file for an agent to edit and no command that pushes changes back to the database, so the SQL stays the single source of truth.
Inngest for background work
Our workflows are event pipelines: an event arrives, we do the work, we write the result. Inngest fits that shape and has a Deno SDK. Each step of a function retries on its own, so a retried model call picks up at that step and keeps the work before it.
In April we ported our Temporal workflows to about 40 Inngest functions.
Moving the event app
Next we are bringing the Ascend web app's backend into Meshi: about 45 API routes and 25 server actions become Hono routes, and Supabase queries become Kysely queries.
Organizers and attendees should not notice the move. Sign-in, redirects, screens and edge cases stay the same, and saved card designs keep their format.