Self-hosting
Eggent Enterprise
Eggent Enterprise is all of Eggent on your own servers. People's workspaces, the company console, the model gateway, file sync and a Telegram bot inside your infrastructure. What we install, what you need and how it differs from the free install.
Eggent Enterprise is the stack that runs Eggent Cloud, installed in your infrastructure. Everything described in Eggent Business and on the page Working in a company works the same way, but files, chats and the agents' memory are stored on your servers.
What we install
- Workspaces. Each person gets a workspace with an agent: files, chats, memory, schedules, skills. An idle workspace goes to sleep and uses no memory, and wakes on the first request with nothing lost.
- The control panel. Creating workspaces, sign-in, the company console and administration.
- The model gateway. Workspaces reach models through it: the provider keys live in the gateway, and a workspace only gets its own pass to it. Spend is counted per person and per team, with monthly limits.
- File sync. People's folders sync with their computers (File sync).
- A Telegram bot. Your own: people create workspaces through it, talk to their agent and get the company's notices.
- Domains and certificates. Workspaces live on subdomains of your domain, and certificates are issued automatically.
Data
- Files, chats, history and the agents' memory are stored on your servers.
- What leaves is the requests to the models you connected, and whatever the agent does on the internet for a task, such as searching or opening a site. If the model runs with you too, people's data does not leave your perimeter.
- The Eggent core is open source under the MIT licence (github.com/eggent-ai/eggent), so the agent's code can be read before it is installed. The control panel and the gateway are installed from our images.
Models
- Through the gateway, on an OpenAI or OpenRouter key. Everyone then has one list of models, and spend is counted per person and per team.
- In a workspace, on any provider's key: OpenAI, Anthropic, Google, OpenRouter, DeepSeek, or a model of your own behind an OpenAI-compatible API, on your own server if you like (Your own provider).
How it differs from the free install
| Free install | Enterprise | |
|---|---|---|
| What it is | One workspace: one agent with its projects | A workspace for each person, and a company |
| Installation | One command, done yourself (Installation) | We install it |
| Models | Your key or your own model | A gateway that counts spend, plus your own key in any workspace |
| Company | — | People, teams, limits, folders, messages, shared files, approvals |
| Sleeping workspaces, file sync, Telegram bot | — | Included |
| Updates | Yourself (Maintenance) | Us, under the contract |
| Price | Free, MIT licence | Under contract |
What you need
- A Linux server with Docker, your own or in your cloud. Everything runs in containers.
- A domain and DNS records: the panel's address and a wildcard record for the workspaces (
*.your-domain). Certificates are issued automatically. - Open ports: 80 and 443 for the sites, 22000 for file sync.
- For scale: on our own server, 6 cores and 12 GB of memory keep about 30 workspaces running at once while the rest sleep.
- Model keys, or a model of your own.
How we start
- A conversation. How many people, where it should run, which models and internal systems it needs.
- Installation. We install the stack on your server, connect the domain and add the first people.
- Connections. Your models, your Telegram bot, your internal systems over MCP or the API.
- Looking after it. Updates and support under the contract.
Not there yet
- Sign-in through a corporate SSO.
- A combined log of actions in the interface.