Architecture

How Wavn is built.

An honest look at the architecture behind the workspace — and why its designed the way it is.

Most AI tools are a thin layer over a single model. Wavn is built differently — as a thinking layer above multiple engines, with privacy and human judgment designed into the foundation rather than added later. This page explains how.

Multi-engine routing

Wavn doesn't depend on one model. Each request is routed to the engine best suited for the job, and any engine can be replaced if a better option appears.

# a request flows through Wavn, not directly to one model your request Wavn router # picks the right engine for the task Claude # writing & reasoning Gemini # long-context analysis Mistral # fast, efficient ops Perplexity # research with sources Cohere # memory & retrieval response # returned to your canvas

Privacy by architecture

Privacy isn't a setting — it's structural. Your content is never used to train models, accounts are isolated from one another, and only the data needed to answer a request is sent to the relevant engine. Provider keys live server-side; they're never exposed to the browser.

Tenant isolation
Each account's data is logically separated and enforced at the database layer.
No training on your data
Your work is never repurposed to train any model.
Minimal data movement
Only what's needed for a request leaves your canvas.
Server-side secrets
Keys are stored in managed secret storage, rotated on a schedule.

The decision layer

On top of the engines sits the part that makes Wavn what it is: a structure for turning thinking into decisions. Content can be marked as a decision, an action item, or an open question, and collects into a live record — so the reasoning behind a conclusion is never lost.

Resilience & independence

Because no single engine is irreplaceable, Wavn can swap one out without changing the experience. That's not just a technical convenience — it's the core principle: no single model, and no single company, controls your thinking environment.

A note on depth: this is an overview, not a full technical specification. As Wavn matures we'll publish deeper architecture documentation, including data-flow diagrams and security details for procurement review.