Self-host Egma - Egma

Quick steps

From the Egma source checkout, start the platform:
egma self-host up
Open the URL printed by the command and sign in.
In Settings → Provider API keys, add the model provider keys your instance will use.

Connect your agent repository to this instance:

egma login --url https://your-egma-instance.example.com
egma init --url https://your-egma-instance.example.com

For a LiveKit worker, set EGMA_URL to the same reachable URL and EGMA_API_KEY to a project-scoped key from Egma.

Environment and secrets

Copy the example environment file in the Egma platform checkout:

cp .env.example .env
chmod 600 .env

Use the files and environments for these values:

Location	Put these values here
Platform checkout `.env`	Public URLs, email settings, provider keys and deployment settings that you choose.
`.egma-platform/platform.env`	Internal secrets generated by `egma self-host up`. Do not edit this file.
Agent repository `egma/config.yaml`	The instance URL, project, agent and connection IDs. Do not put secrets here.
LiveKit worker environment	`EGMA_URL` and a project-scoped `EGMA_API_KEY`.

Keep both environment files out of Git. Store production secrets in your deployment’s secret store. Preserve .egma-platform/platform.env with your database backups because Egma needs its encryption key to read stored credentials. Run egma self-host up again after you change the platform .env file.