Envoryx on Unraid or hosted? Both have their place.

Envoryx manages development and staging environments as projects, with a web interface, their own addresses and SSH. What the software does and what hosted operation looks like is on our page Envoryx hosting.

“On Unraid” means Envoryx runs as a Docker container on your own Unraid server. It is given the server’s Docker socket and creates separate containers for each project. The Envoryx documentation calls Unraid the primary target but also says nothing depends on it. Any Linux server with Docker will do.

On Unraid you find Envoryx in the Community Apps. The project itself describes the setup, with the Docker template or manually under “Docker → Add Container”: DEPLOYMENT.md, section Unraid. According to the documentation you need Unraid 6.12 or newer. The Envoryx project is responsible for that installation, not Envbay.

This is what the project’s documentation describes. It is no drawback, but work you should plan for.

• Names and DNS: Projects are reached under names such as shop.test. For that you add a wildcard entry once in your network’s DNS server, for example in AdGuard Home, Pi-hole, dnsmasq or Unbound. If your router cannot do that, you keep a hosts file on every device.
• HTTPS: Envoryx issues certificates through a local certificate authority. You install it as trusted on every device. With a domain of your own, Envoryx can instead obtain a public wildcard certificate from Let’s Encrypt through your DNS provider’s API. Nothing has to be reachable from the internet for that.
• Storage location: Envoryx’s database (/config) belongs on a local file system, not on NFS or SMB. On Unraid the documentation recommends your pool’s path instead of /mnt/user.
• Backups: Project backups are stored in the appdata folder by default, optionally on a share of their own on the array. You set up copies off site yourself (S3, SFTP or WebDAV). The documentation advises including /config, /projects and the backups in your own backup routine.
• Updates: On Unraid you update through “Docker → Check for Updates → Apply”. Database migrations only go forward. Before the first migration of a new version Envoryx writes an instance backup.
• Secret key: Envoryx encrypts stored secrets with a key. Keep a copy outside Envoryx. Instance backups do not contain it. To show it, Envoryx asks for your password from version 0.46.0. When moving to another instance, you enter it while restoring.

• Production. Envbay is built for development and staging, is in beta and makes no availability promise.
• Ollama and local models. Free and Starter exclude the services Ollama and OpenSearch. For Team and Agency we make no promise about them for now, and a graphics card (GPU) is part of no plan. For local models, a server of your own with a suitable graphics card is the better choice.
• Full control over the server. You get Envoryx with its web interface, SSH into the project containers, SFTP and the API. There is no shell on the host and no access to the Docker socket.
• A lot of storage. Storage is limited per plan (see the table below) and HDD-based with a RAM cache.
• Data that must stay in your own house. Our servers are in the EU, not with you.
• Outgoing mail. The mail ports 25, 465 and 587 are blocked for outgoing traffic. You catch test mail with Mailpit.

Memory and cores apply to the whole instance, all projects share them. The SSH gateway for your IDE is included in every plan. Support response targets are on the pricing page.

• Questions about Envoryx itself (operation, features, bugs in the software, setup on Unraid) are answered by the project: documentation at envoryx.dev, bugs and requests as an issue on GitHub.
• Questions about a hosted instance (operations, billing, backups, availability, your account) are answered by Envbay: support@envbay.com or a ticket at my.envbay.com. The split is also in the manual under Help.