/about
Built for the conversation,not the model wars.
Synapse is a product story, not a team page: what broke about talking to AI, the wager we made, and the principles that keep it honest.
/story
/timeline
How it came to be.
01 · the problem
Twenty tabs, zero memory.
Every frontier model got its own tab, its own bill, and its own amnesia. The best answer lived one paste-and-re-explain away — every single time.
02 · the wager
The thread is the product.
We bet that people don't want a model — they want a conversation that keeps going. So we built routing, billing, and memory around a single thread instead of a single provider.
03 · where it landed
One meter. One memory. Every model.
Synapse today: 20+ models behind one composer, credits reserved before a token moves, and context that folds forward into every new conversation.
01
Model choice should be obvious
You should always know why one route is fast, one is premium, and one is better for long-form or code-heavy work. No black-box routing.
02
Conversation quality should compound
A good assistant isn't only clever on turn one. It keeps context, remembers decisions, and gets sharper the longer you work with it.
03
Billing should never surprise you
Credits are reserved before a request runs and refunded when the turn commits under budget. The meter is visible, not buried in an invoice.
04
Trust should be visible
Privacy, memory controls, and operational behavior belong on the public surface — not only in legal documents and account settings.
/surfaces
One of three connected surfaces.
NARA Chat
you are hereThe conversation surface — multi-model threads with routing, memory, and generative UI where it earns its place.
NARA Image
adjacentA bucket-backed image studio that sits adjacent to the conversation, not in front of it.
NARA Auth
the boundaryOne identity across the whole NARA surface area. Credentials never touch the chat app itself.
/stack
Next.js
Application shell and public routing.
TypeScript
Typed product and frontend systems.
Convex
Realtime state, mutations, and app data.
Tailwind
Design system implementation.
React
Composable interaction model.
Judge it by a conversation.
The fastest way to understand Synapse is a five-minute thread. Or write to the people who build it — same channels, same inbox.
direct channels