How we build. We build until it works.

The engineering we actually ship: agent swarms, AI voice agents, full-stack web, a 58-rule AEO engine, and 3D in the browser.

01What we build with

01Multi-agent orchestration

Agent swarmsTypeScriptNotionLinear

We build and run agentic systems. This very page was built by a swarm of coding agents working in parallel against the live repo. We wrote our own voice-controlled orchestration server in TypeScript that spawns coding agents against real repositories, classifies intent, and wires into Notion, Linear, Vercel, and GitHub. Agents doing the boring parts means we ship more, faster. Ninebrains is that way of working, open-sourced.

See it: Ninebrains

02AI voice and telephony

VapiTelnyxRealtime voicePSTN

Production AI voice agents that answer real phone calls. We pair an LLM brain with realtime voice on Vapi and live PSTN phone numbers on Telnyx, so a caller talks to an agent that books, qualifies, and answers. We build these as scoped sprints.

03Full-stack web and product

Next.jsReactTailwindSupabaseVercel

End-to-end product engineering. Next.js on Vercel for the front, Supabase (Postgres, Auth, encrypted Storage) for the back, Tailwind for the look. Sites that load fast, convert, and come AEO-ready out of the box. Our client sites are built the same way.

See it: Client work

04AI search and AEO engineering

58-rule engineMCP serversGSCGA4

We built a 58-rule scoring engine that grades a site on how AI answer engines see it: entities, schema, citable answers, structured data. It runs MCP servers and pulls live Google Search Console and GA4 data. It is the engine behind our maintenance work, and it is open source.

See it: AEO Toolkit

053D and WebGL

WebGLGLSLReact Three Fiber

Real 3D in the browser with hand-written WebGL, custom GLSL shaders and React Three Fiber. The point-cloud sphere on our homepage is ours, and so is the 3D backlink-graph visualization inside the AEO Toolkit. Interactive, fast, and not a stock template.

06Open source, in the open

Open coreApache-2.06 npm packagesChrome extension

We ship our work where anyone can read it. Ninebrains and runs-on.dev are open source. The AEO Toolkit is open core: its scoring engine (six Apache-2.0 packages on npm), the Chrome extension and the Claude skills are public, while the hosted console and MCP servers are proprietary. Shipped code beats slideware, so we show the code.

See it: GitHub

02Things we shipped

Not slideware. Live products you can open right now.

The AEO Toolkit console's audit tool on a light concrete ground: a Website URL field with a Run audit button, above the four things a run returns, being an overall score and letter grade, a category breakdown, prioritized severity-ranked fixes, and generated robots.txt, llms.txt and sitemap files.

AEO Toolkit, hosted audit: 44 checks

03How we work

01Build until it worksThat is the whole method. Ship something real, put it in front of actual use, and keep cutting until it does the job. No theater, no endless planning docs.
02Ship, then cutWe get a working version out fast, then sand off what does not earn its place. Speed first, polish second, dead weight never.
03Use our own products firstEvery tool we sell, we run on ourselves before we ask anyone else to. The AEO engine scores our own sites. If it is not good enough for us, it does not go out.

Put it to work

Want this pointed at your problem? We take on outside work two ways: monthly AI search maintenance and fixed-scope build sprints. New to AI search? Start with the guides or read why your business is not showing up in AI search.

See services and pricing