Novaterra

Find your way in

What Novaterra is The seven pillars, the constitution, and why the desktop is the product.

Getting started Requirements, install, environment variables, and your first arrival.

The Living Desktop Widgets, themes, signals and the omnibar — your sanctuary.

Your Twin Memory, profile, and the connections that feed them: files, mail, history.

Muse The conversational face of your Twin, and how it thinks.

The Studio Briefs become task graphs; agent teams turn them into real outputs.

Self-hosting One install is one person's node. How to run it on your own machine, and keep it running.

Architecture One node per person, the primitives, the sandbox, and how two nodes talk.

API reference Every entity, REST route and WebSocket event, generated from the contracts package.

Run your own node

A Novaterra install is one person’s operating system: one owner, enforced in the database by the beings_single_owner index. There are installers for Windows and for Linux, the keys stay on the machine, and a node that wants to can find other nodes and talk to them. These are the pages for that.

Self-hosting Local development, the code sandbox, and every real deployment path in the repo.

Finding other nodes The directory is a lookup, not an authority — how a node publishes where it is, and how to run without a directory at all.

Node profiles and Seeds The four profiles — seed, leaf, home, hall — what each one runs, and what it has to borrow.

Moving your node Export a node's identity, carry it to another machine, and keep the same addresses.

Local-first inference Run any tier on your own GPU instead of OpenRouter — the exact env vars, and what still leaves the machine.

Keeping it running Supervision, WAL checkpointing, and backups you have actually restored.

Scaling and redundancy Four tiers from a laptop to multi-host, and how to tell whether you have really outgrown one machine.

Vercel + Cloudflare production Static hosts on Vercel, the API at home, joined by a Cloudflare Tunnel.

Identity and the mesh A being's address is a public key — how two nodes exchange a message neither has to trust the other to verify.

The seven pillars

Novaterra is one product built from seven parts, and each one is real code you can run:

1. Living Desktop — a full-screen, theme-driven living background with glass widgets that surface the right thing at the right moment.
2. Twin — your digital twin: memory, profile, files, mail, history. It learns and acts on your behalf.
3. Muse — your best friend and assistant, the voice of the Twin.
4. Studio — generates anything: text, documents, images, code, full React + Node sites, 3D scenes.
5. Agent Teams — crews of agents carrying skills, planning and executing the Studio’s work.
6. Marketplace — trade generators, skills, agents and work.
7. Souls — every being here, human or AI, has a personality, values, a voice and a mood.

Everything in these docs describes software in this repository. The API reference is generated straight from packages/contracts, so it can never drift from the code that runs.