Blog

Notes from the build.

How Wend is built, one decision at a time: where the graph lives, what the AI is allowed to write, and what we chose against.

We open-sourced the engine behind Wend

wend-core is public under AGPLv3: the graph schema, the propose-and-confirm commit path, recall, connection paths and the secret box.

Earlier posts

Clay (clay.earth) was acquired by Automattic and is now Mesh. What changed, what did not, and your options if you want to move your contacts.

By Ava Yu

Every AI call Wend makes writes an audit row naming the model that served it, the tokens, the cost and the latency, visible to the user.

By Ansh Vasani

How we ran two-region Supabase for EU residency, and why we moved to a single US region under Standard Contractual Clauses instead.

By Ansh Vasani

When a new fact contradicts one already in your graph, Wend flags it instead of overwriting. Here is how conflicts are surfaced and resolved.

By Ansh Vasani

Why Wend's graph lives in plain Postgres tables instead of Neo4j, what we gave up, and the queries that turned out to be easier anyway.

By Ansh Vasani

next/font/google downloads woff2 files at build time and serves them from your own origin. What that means for privacy and page speed.

By Ansh Vasani

Wend

Every fact has a source, and you approved it.

Access is invite only right now.