Skip to content
Domia
Open the console demo (opens in a new tab)How it works
Use cases
Run it
Console
About
Contact
enes

Run it

Same software on every node. You choose the role.

Install the node, apply a template or build the configuration from scratch, and it becomes a standalone Domia, a full hub or a thin client.

See the four stepsRead the getting-started guide (opens in a new tab)
Two Domias at a table, one handing a configuration to the other

Install it and get your first turn

Four steps to a Domia that answers out loud.

Before you start

  • A computer you own. Domia adapts to your hardware.
  • A microphone and a speaker, or a satellite in the room
  • Some free space for the voice and language models
  • The getting-started guide walks you through the rest

  1. Install the node

    Download Domia from GitHub and run its setup. It prepares everything it needs, including the voice models and a local language model.

  2. Apply a template, or start from scratch

    The node boots neutral. Apply a template from the console, which is a separate install, or build the configuration field by field. The role stays, and your own setup can be saved as a template.

  3. Plug in a microphone, or bind a satellite

    A microphone and speaker on the node work as soon as the template is applied. For a room, discover a Home Assistant Voice PE, a Wyoming satellite, a browser room or your own board from the console and bind it to an identity. The satellite listens for the wake word; the node does the rest.

  4. Say the wake word

    "Computer" by default, then ask for something. Follow-up mode keeps the microphone open after a reply, so you can keep talking without waking it again.

Pick the role for your machine

Every node installs the same way; the template you apply decides what runs on board.

What kind of machine do you have?

On a capable machine, this runs on board:

Runs here

  • Wake word
  • Audio in and out
  • Speech to text
  • Routing
  • Language model
  • Text to speech
  • Memory

Runs on another node

Nothing, it all runs here.

One machine does everything for one home, from the wake word to the spoken reply, with memory on board.

Choose this if the machine can run a small language model by itself and you want one Domia.

One Domia

This is the standalone template.

Defaults target accessible hardware. Better hardware gets a better experience for free.

Connect your skills

Built-in tools work from the first turn. Home Assistant, Music Assistant and any other MCP server start working once you connect them in the console, and each one can be switched off per identity.

  • Home Assistant
    You need Home Assistant with its MCP server integration turned on and an access token. Add both in the console.
  • Music Assistant
    You need a Music Assistant server on your network. Add its MCP address in the console; playback and volume then take the fast path, and searches go through the model.
  • Your MCP server
    Any MCP server the node can reach. Add its address in the console and its tools become skills.

It moves with you

Nothing about a Domia is tied to the machine it started on.

  • Mind transfer
    Export a Domia's character, mood, memories, knowledge, routines, satellites and skills as one bundle, credentials stripped, and import it on another node, merging or replacing.
  • Templates, or from scratch
    Apply, compare and re-apply templates for any node, build a configuration from scratch, or save your own setup as a template. Applying a template restarts the node; most later edits reload live.

Start with the getting-started guide

The install, the templates and the first turn, step by step.

Open the getting-started guide (opens in a new tab)Try the console demo (opens in a new tab)