Leaderboard

Let's Talk About Immich If you've been running Immich on HexOS this year, you know it hasn't been smooth sailing exactly. We want to talk about what's happened, why it was so challenging, and how we're working to handle these situations better in the future. What Happened? Earlier this year, Immich deprecated their old storage configuration and required all users to migrate to a new structure. For users running Immich through docker-compose or other manual setups, this meant updating some configuration files and running a few commands. Annoying, but manageable. For some HexOS users, the migration was more involved. Because of how TrueNAS SCALE structures application storage, moving to the new configuration required either reinstalling Immich fresh (the simplest solution) or manually migrating existing data between datasets (a process that involved SSH access, rsync commands, and careful attention to permissions). But if you're choosing between "reinstall the app" or "follow a 15-step guide," neither option feels great when you chose HexOS specifically to avoid that kind of complexity. Why Was This So Hard? When Immich made this change, we had a choice to make. We could have built a comprehensive rsync-based migration tool using the TrueNAS API. It has those capabilities. But that would have meant dropping everything else we were working on to build what amounts to using a cannon to kill a mosquito: a massive, complex solution for what we hope won't be a regularly recurring problem with this particular app. Instead, our community stepped up in a huge way. Users like @forsaken and @G-M0N3Y-2503 created detailed guides (to move or rsync your data). These guides walked through the manual migration process to preserve existing data in Immich. They focused on helping users through the immediate problem, while we continue building the platform we need to handle situations like this properly. That platform is HexOS Local: a locally-hosted management application that will let us perform complex operations without being bottlenecked by the engineering overhead of building one-off solutions through the SCALE API every time an application throws us a curveball. This reduces the technical burden on our team and, more importantly, gives us the flexibility to automate maintenance tasks that previously would have required manual intervention or massive engineering investments. This same platform will serve the Local UI/UX feature we've committed to delivering as part of our 1.0 release. We'll be talking a lot more about HexOS Local in an upcoming blog post, but the key takeaway is this: we're building HexOS to handle whatever the open-source ecosystem throws at it, without having to choose between "drop everything and build a custom tool" or "make users SSH into their servers." What About Right Now? If you're currently running Immich on the old storage configuration and haven't migrated yet, you have options: The simple path: Reinstall Immich fresh with the new configuration. Your photos will need to be re-uploaded, but the setup is clean and straightforward. The preservation path: Follow one of the community migration guides to keep your existing data in place. These guides are more technical and require command-line access, but they work. Our recommendation depends on your situation. If you have a manageable photo library and good backups, the fresh install is probably your best bet. If you have years of photos, carefully organized albums, and user configurations you don't want to recreate, the migration guides are there for you. And if this seems to daunting, email support@hexos.com so we can schedule a time to assist you directly. Moving Forward The Immich situation showed us exactly where we need to invest engineering effort. We can't keep facing the choice between building massive one-off solutions or asking users to break out the terminal. That's not sustainable, and it's not the HexOS we're building. Immich is an incredible project. It's exactly the kind of self-hosted solution we want to make accessible to everyone. The team behind it recently released v2.0, marking their stable release with better upgrade paths going forward. We're committed to making sure that when the next complex maintenance task comes up, whether it's Immich or any other application, we have the infrastructure in place to handle it gracefully. That's the HexOS we're building. Thanks for your patience while we get there.

Hello all! We are excited to announce HexOS Local, powering the new local UI/UX for HexOS and capable of so much more. Read more about it on the Blogpost - Introducing HexOS Local

Forgive me, but I'm really confused by what you're saying, which means there is clearly a disconnect in our marketing language and understanding with customers as well and I want to get to the bottom of that. Let's try some clarification here: Buddy backup is a feature that will allow two HexOS users (customers) to backup to each other's server in an encrypted fashion. There is no reason you cannot be your own buddy with a second license (e.g. you buy a second server license and put a server at a secondary location). If someone bought two licenses during black friday under two separate accounts, each account can backup to each other just the same (and if they want to merge those two accounts, we can handle that for the user). With this sale, however, we are not allowing someone to buy a second license to transfer to another user (as it would open the door to reselling licenses which we don't support). I get that the term "buddy backup" may not clearly identify that you can be your own buddy, but we thought it would be fairly obvious that if you could backup to someone else on a separate account, you could also backup to yourself on the same account. I think we could loosen the "encryption" requirement in the case of backups between two servers owned by the same account, but that's more of a technical detail than marketing. Let me know what's still unclear or how we can do better on the language here. Sometimes we can be a little too close to the trees to see the forest, so if you can help give us a better perspective, we'll work to improve our messaging in the marketing. Thanks!

Buddy backup will definitely work with two licenses under the same account. You will be your own buddy 😉

OMG, I totally see the confusion now. I have edited that post and reworded it to be more clear. TrueNAS has no built-in means to do backups as part of their OS unless you consider rsync cron jobs/replication tasks as "backup". They don't facilitate the connection between servers or even setup the SSH permissions for you (you have to do all of that yourself). This is where our solution takes things a step further. We intend to make the experience much simpler. First you "friend" someone else that is a HexOS user (if you're doing the "buddy" approach). Then you will grant that user "permission" to backup to your system (and set a quota). Then they accept the request and authorize the backup in return (if you're doing that). Then we do the rest (establishing a secure VPN tunnel between systems, creating appropriate SSH users and handling the key exchange, etc.). You'll definitely be able to leverage the buddy backup system between two systems licensed under the same account. That would be silly of us to prohibit or unnecessarily complicate. I get the confusion. Buddy backup is just the marquee feature name for our backup solution between two servers. Every server needs a license. So if you and a buddy want to backup, you both have to have your own licenses under your own accounts. If you have two licenses for two systems under 1 account, you can use the same "buddy backup" system to handle that job as well. Apologies for muddying the water on my initial response. I can see how that had some folks confused, but I hope this clarifies.

It's hard to believe it's already been a year since we launched the HexOS Beta and the early access campaign. What a journey it's been! In today's blog post, we're going to provide a summary of this past year's accomplishments, a run-down of what's left to achieve our 1.0 release, what's coming next, an update on the AnyRaid project, and our HexOS Holiday Sale! Read all about it in our latest blog post: https://docs.hexos.com/blog/2025-11-26.html

Another mid-quarter update featuring: New curated app installations Update to the qBittorrent installation Read more about it on our docsite here at Command Deck Update - November 25, 2025 NOTE: This update was applied automatically. You may need to clear your cache.

To celebrate the holidays and thank our community for their continued support, we're excited to announce our HexOS Holiday Sale, starting today! Existing customers can purchase additional licenses for just $99 each, perfect for expanding your home server setup. New customers can take advantage of our special two-pack bundle for $298, with additional licenses available at the same $99 promotional price. Single licenses remain available at $199 until our 1.0 release in Q1 2026. This holiday pricing for additional licenses and the two-pack bundle is available through December 31st, so don't miss out on this opportunity to join or expand your HexOS experience. Please note: License transfers are not permitted. All licenses are tied to the purchasing account. Buy now from the HexOS Store!

The difference is pretty big, while they do the same thing, they do it very differently. Immich just stores all the images in plain on the file system, all the processing is done on server side, you can connect an external library and if your Immich DB or installation becomes corrupted or breaks and there is no more support for Immich you just take the photos folder and move on. But the admin and everyone who's access to the folder can see all the photos of everyone, so privacy is not that great, but administration is easier and recovery in case of an issue is easy. Ente (FunFact: Ente is German for Duck) is all about privacy. The photos are all encrypted on the server and only the client side can decrypt/see the photos. This also means that the client side needs to do all the processing, but therefore the server can be very low spec (although this doesn't matter in our case, because Hexos needs to run in the first place, so HW specs is not really a concern in any way) and it needs S3 storage and requires more setup an administration. However if your Ente DB becomes corrupted or the Ente app breaks or the Ente dev stops and your app becomes unusable, you lose all your photos, because you cannot access it any other way. But until that happens only your client side device can access the photos and no-one else can.

Just got off a call with a few of the Eshtek guys, they set me straight very quickly. Before I called them, I dove into what others here have done. Here is what fixed the router swap for me: Sign into the TrueNas Scale Web UI. Go to Network: Go to Global Config settings: Change Nameserver1 and IPv4 Default Gateway to the IP address on/of your router. My issue was that I kept changing the NAS IP address to the IP of the NAS, not the router. Essentially, I was signed into my router interface, looked up what the NAS IP address was, and kept changing the Nameserver1 and Default gateway to that IP, when I should have been setting it to the IP of the router. Once that is done, my NAS found the internet again, the HexOS deck found a server and I was set! I had to skip the initial setup in order to prevent wiping the drives, but I was saved. Thanks to Nick and Eric!

Wait, so if I have two licenses under my account I can't put my second server at eg my parents home for a offsite backup and sync via BuddyBackup?

As of today, yes, you can access your server from anywhere using deck.hexos.com. I have a discussion planned with the team to allow you to disable remote access which would be as simple as us verifying the WAN IP of the client device being used to connect to the deck and making sure it matches the server's WAN IP. When HexOS Local arrives, you will be able to even further reduce your cloud dependency, but there are some features like installing apps/VMs, configuring buddy backups, and e-mail notifications that will require a connection to our deck. Thankfully that connection is outbound from your server, which doesn't require you to open any ports on your firewall and expose the system to the wider net. We also do have plans to implement oAuth and 2FA in the future to further enhance security and options.

We know about this problem all-too-well. The VM features will come in layers, but our plan is to try and get ahead of those kinds of problems by detecting hardware changes and automatically adjusting device ID mappings to your VMs before they start. This still needs a lot of R&D work and there are lots of potential gotchas, but I bet we can address a lot of common scenarios like what you've described. It gets more tricky when you have multiple GPUs in a system of the same make/model, as it's hard to know which one is which for assignment to VMs. I'd say that's a problem for after the initial VMs feature release for us to investigate further. Ultimately there will be some limits to what we can do, but we're going to do this as best as is humanly possible.

Correct. The additional licenses is for users that want to setup multiple systems of their own, not for buddy backups. @Todd Miller rightly called this out as confusing. What I meant to say is that you just can't transfer the license to another user. You can use buddy backups (as a feature) between two systems that you own and control (licensed under one account). Sorry for the confusion! Carry on!

Def not cloud only. If your isp/network supports peer to peer, we can coordinate that and then get out of the way. That is what's included in a lifetime license. If we end up having to relay traffic for some users, that will require a subscription as we will have to pay for the relay traffic, but obviously it will still be encrypted.

Pretty disappointed with this limitation. I understand the reason to avoid unscrupulous reselling, but I do think there are better ways of avoiding that without these issues. There are probably a lot of people in a similar situation as me; wanting to get a license for a relative as the family tech guy, but not wanting to have to be the sys admin for everyone. I bought a license at release because I support the mission, with no intention of using it until the features got more flushed out (still on plain TrueNAS). I am in the process of building a NAS for my father, which I intended to set up with a HexOS license so he could use buddy backup and some apps as a relatively nontechnical user. The HexOS interface is simple enough I think he can grasp it. But if I have to be an admin for his NAS anyway I might as well just set up Tailscale and rsync on TrueNAS. I understand it's a sale price and I'll probably end up getting him his own but it just feels like a slap for people that bought in to support and I hate feeling like I'm throwing money away. I'm no business major but it seems like expanding the user base would be prioritized given the possibility of genuinely useful subscription features coming down the pipe. Anyways. Just my $0.02. Still love what you guys are building.

Thanks for confirming and apologies to anyone that was confused. If anyone bought another license at $199 on accident today, send an email to support@hexos.com and we'll get the difference refunded.

No its not over. We are investigating why the correct pricing isn't showing up for users. Stand by.

The backup stuff sounds great, any serious system should have the ability to backup and restore, especially when apps like Immich are being recommended, seeing away to back all this stuff up would make HexOS a serious contender in the networking and diy nas space, maybe even business

at this time your best option would be using the in app backup and restore functions and then reinstalling it if you would like to migrate. But i will be sure to let the team know that users are interested in migrating over to curated versions of the apps.

I would like to see first party support for placing any app behind some of the most popular VPNs (PIA, Nord, Express, Proton, Tailscale, etc), as well as custom VPNs (WireGuard, OpenVPN, etc). For example, you may install “The Lounge” IRC client and have all internet communication pass through a PIA VPN so that your home IP is not exposed while chatting. Traditional methods of doing this involve painful configuration of iptables or other firewall rules. I believe this is an area where HexOS could really simplify things: Install a VPN plugin, authenticate with it, and then simply assign an app to a VPN plugin via the app’s settings if desired. It would be fully accessible from the home network without going through the VPN, but all internet traffic would go through the VPN with a kill switch in case the VPN goes down. Thoughts?

If there are still a plethora of users affected after Local is released, we would consider it. But if not, we would rather spend the time via support helping people up over this fence than engineer an entire solution for a handful of folks. Support@hexos.com is available to you at no cost.

That thought did occur to us, but to be perfectly honest we'd rather anyone not comfortable following the guides or having difficulty to just contact us directly for support. That's what you all paid for and we are gonna provide it. I don't want to start asking our users who aren't comfortable to navigate the TN interface.

I ended up having to reinstall Immich (twice, for some reason, the second seems less likely to be hexos related), so I appreciate you being up-front with acknowledging that it was… not fun. Daunting was probably the right word for it. I usually consider myself tech savvy so being so totally out of my depth was frustrating in a way I’m not used to. A suggestion: some folks might be having trouble completely uninstalling/reinstalling (I did) so a simple guide on how to do that might be helpful, even if it’s just “hey delete this dataset” - I’m sure the advice exists in the forum but there are a lot of things to search through to find it. If I remember right, uninstalling/reinstalling on the hexos deck didn’t fix the underlying issue or delete the underlying data. I’ve seen the pace of updates and the pace of communication improve over the last few months - which makes it easier to assume best intent. I look forward to what’s coming next (and hopefully no other apps break that bad)

We now have one: Custom Install Scripts - HexOS Hub

ZCMK123's post got me up and running. Check it out and see if it helps you.

Not possible. License transfers are not permitted. All licenses are tied to the purchasing account.

Should be fine to leave alone. I think our install script sets that folder to posix

There is no announced timeframe at this time. The benefit is being able to make bigger pools.

Hey, no this will not work as you've described it. With 2 drives Hexos will automatically create a mirrored pool, meaning your data will be stored on both drives at the same time and you will only have the capacity of 1 drive but you can lose 1 drive without losing data. You cannot create a Pool without parity with more then 1 drive. A RaidZ Pool type cannot be changed after it was created, so you will be stuck with your mirrored pool and you cannot expand it. If you then throw in your 4 drives from the old NAS, Hexos will create a new RaidZ1 pool, which has the capacity of the numbers of drives -1 (capacity of 3 drives in your case). You can then copy the data from your mirrored pool to your RaidZ1 pool. If however, your mirrored pool does not have enough capacity, get yourself a 3. drive to create a RaidZ1 from the beginning, copy your data over and afterwards add your drives from your NAS to the pool or create a new pool. (expanding a pool can only be done with 1 drive at a time and takes some time). Also make sure all your drives have the same capacity or else Hexos will not group them together.

there aren't any risks to unclaiming a server. whenever you reclaim it just be sure to use the skip setup button. seems like you have the bug discussed in this post Hopefully the solution there solves your problem

@wvienna @FangerZero can you guys check again and let me know if the discount shows up correctly for you now?

Most apps seperate config and user data. I'd guess the reason for this would be, people primarily care about the user data (Photos). So the config data like user profiles/Album organisation are less important. The idea being, maybe immich turns into a dumpster fire and you want to use something else, at which point you only care about the photos. So that app data, or config data as I called it are historically different, so additional work may be necessary.

Amazing news. I just hope adding HexOS Local will be seamless and won't require a fresh install/rebuild!

no worries Biem, moved you to the right spot So seems like you have a fairly common use case withI he addition of game servers. The requirements for game servers do differ depending on game and the scale (like if you plan to make a sever say 100+ will join) so you may want to look up that part yourself As for the rest you should easily get by with some of the cheaper intel cpus available something like an intel i5 8400 or 8500 should be more than strong enough those intel cpus have integrated gpus so you don't have to spend extra on a graphics card and they support intel quick sync which just means they are great for plex. Make sure any motherboard you get does not have a realtek nic (network interface card), you can usually find out on the motherboard webpage or on the pcpartpicker page for the motherboard. for cases i like recommending the jonsbo n4 since its a fairly compact case that has 6 hdd bays and a relatively good value. The downside with the n4 is that it will only fit smaller sized power supplies and motherboards which may cost more than full size. for you boot drive i suggest getting a cheap and small ssd. any space left over on it after the os is installed cannot be used. I would suggest no less than 16gb of ram for you. now depending on your budget you could get a stronger cpu or more ram.

At this time the recommended way to update the path is to uninstall and reinstall but you shouldn't lose any data if you uncheck remove app settings and data.

Great to see the progress being made compared to the early launch last year, I'm exited to see where it goes with the new upcoming roadmap. While I'll personally will be waiting till a few more curated apps will be available (such as Kometa and Bazarr) it seems at least a good solid foundation will be standing with the 1.0 launch. Keep it up guys!

I tried following the recommended guides - frankly too time consuming/complicated for a non-technical person. Instead I went the uninstall/reinstall route, it's very easy if you can backup/re-upload your content (which takes forever 😑). The below post explains how to reinstall. It requires re-creating users/settings and logging in again on the mobile app.

If you guys are stuck, please email support@hexos.com and we will schedule a time to work with you on this.

It did. We wanted to build in a better solution to address this, but as I stated in the OP, it would have required a massive divergence of focus from our team to build a solution within the UI itself. We ultimately decided putting out this post and offering 1:1 assistance to those affected was the best course of action. We are offering 1:1 support to anyone that needs it. Just email support@hexos.com and we'll schedule a time. I mention in the OP our plans to be able to better address this in the future via HexOS Local.

First, a huge thank you to @lnkd for posting the actual steps to do this. All I did was follow everything they said and take pictures, so really all credit goes to them. Original post here: Prepare TrueNAS for reinstall: 1. Login to TrueNAS web interface – go to deck.hexos.com and click Settings: Then click the TrueNAS icon: 2. Once logged into TrueNAS, go to System > General Settings > Manage Configuration > Download File: 3. Read the note presented when you click Download File: 4. Click Save: 5. If you have encrypted datasets, go to Datasets > select the encrypted dataset > Export Key: 6. Now it is time to shutdown the server. In the top right of the TrueNAS web UI click the power icon and click shutdown: 7. Make your changes to the hardware that you would like – for me I added a 10 GB network card to run off fiber. 8. Prepare the HexOS installation drive by following these steps: https://hub.hexos.com/topic/103-illustrated-installation-guide-start-here/ 9. In your router settings, give the new hardware the same IP as your old one, then restart TrueNAS to grab the correct IP. 10. Once rebooted you can confirm on the server the IP address is correct: 11. Login to the TrueNAS web interface with the username and password you set during install (username should be truenas_admin). 12. Confirm your version on the dashboard – if needed, apply the update to the server: a. To confirm what version you need check the filename of the .tar file you downloaded from your configuration. It will have the version number on the end of it. b. Select the same version from the upgrade screen and confirm you want to switch to that upgrade train. c. Apply the pending updates and the system will reboot. 13. Go to Storage > Import Pool > find your zpool: 14. I have two pools so I will import them both. 15. Go into System > General Settings > Manage Configuration > Upload file: 16. The server will reboot after the configuration is applied. Log back into the TrueNAS server once the reboot is finalized. 17. If, like me, you replaced the network cards you will need to login directly to the server and adjust the IP settings: 18. Setup your new interface with the primary IP in CIDR notation, then you can log back into the TrueNAS server. 19. To setup apps, you need to go to Apps > Configuration > Unset Pool: 20. Restart your TrueNAS server then go back into Apps > Configuration > Choose Pool: 21. Once the pool is set you will see your apps again and be able to start them. 22. Navigate to the HexOS Interface (http://deck.hexos.com), unclaim your old server and claim your new one: 23. I ran into an issue where no matter what password I input it would not take it: 24. Currently troubleshooting that to be able to claim my HexOS server in the deck. All of my apps and storage are up and running so I will report back here when I fix this issue.

I'll just answer myself. It is. I had previosly updated TrueNas to Fangtooth which is not supported and I messed up the boot pool so I wanted to reinstall but was worried about it (I was thinking on just dropping HexOS and use TrueNas directly with the latest version). I was able to reinstall everything following these steps (I had a recent copy of the truenas config): Follow steps 1 to 6 Update TrueNas from the UI to Fangtooth Reimport TrueNas config profit This was easier than I though and I didn't lose any data.

Right side but the toggles should closer to the words like they are on the Left version. half the width of a monitor is too far away

I believe integrating Home Assistant with HexOS could be a game-changer for the operating system, offering functionality that is sorely lacking in almost all other OS platforms today. A Home Assistant integration would allow users to monitor and manage their NAS more effectively. Imagine being able to track critical metrics such as system uptime, array health, disk health checks, and the overall status of your storage systems — all from within Home Assistant. Furthermore, adding control features would significantly enhance the user experience. It would be fantastic if users could automate tasks like rebooting or stopping/starting applications, VMs, or containers directly through Home Assistant. Additionally, automating disk spin-downs during off-peak hours for power savings would be a powerful and eco-friendly feature. The potential of Home Assistant integration is vast, and it's difficult to fully capture all the possibilities in a single topic. However, the core idea is simple: having such an integration, with continuous updates and new features, would be a major advantage for HexOS. While most other operating systems either lack similar functionality or offer only basic, limited capabilities, HexOS could stand out by providing a more comprehensive, user-friendly, and flexible solution.

I would like to see an option of an one click full disk encryption at system setup (or disk/pool or per application setup). Then it should work like in the TrueNAS interface with a warning ⚠️ about the possibility to lose all data if the corresponding password/key is not stored properly and so on... It would be preferable to encrypt all the folders below automatically too, since the title “Full disk encryption ...".

It is a must these days to have TailScale support, especially for secure remote access. It is far too easy to mess up a WireGaurd/OpenVPN Config, if the goal is security and simplicity, Tailscale VPN access should be a high priority.

I’m hoping that Tailscale support is also in the works - 🤞yes?

UPDATE: As of 11/8, we have updated the ISO installer to run on version 25.04.2.6 of TrueNAS SCALE. Existing users should NOT reinstall to get this version. You can update from within the Activity card on the Dashboard (or the Notification). Hello and thank you for joining the HexOS beta program! You are an elite and vital part of this project and your participation is greatly appreciated. This post contains all the information you will need to get started with HexOS and how to communicate with our team during your beta experience. Disclaimer Beta Products, Software, and any related Services are still in development, and therefore, you are advised to safeguard important data, to use caution, and not to rely in any way on the correct functioning or performance of the products, software, or any related services. Beta Products and Services are provided to you “AS IS”, without any warranty whatsoever. Expectations During your participation in the beta, we expect you to do the obvious: use and test the software. But we also expect you to communicate with us when things don’t go right or if you’re having trouble. Please post feedback and let us know about your experiences, good and bad. That being said, please remember that this is beta software and early access. HexOS has a long and healthy roadmap ahead. Quickstart Guide For those that just want to get started, here’s the TLDR: Download the ISO here: https://downloads.hexos.com/TrueNAS-SCALE-25.04.2.6-HexOS.iso or https://hexos-downloads.sfo3.cdn.digitaloceanspaces.com/TrueNAS-SCALE-25.04.2.6-HexOS.iso (SHA256 Checksum: e8ed99a322affe0969b82b866161a9f6acbc1561e3cc7b2efb2bf120ffe2e856) Use a tool such as Balena Etcher to image a USB flash device with the ISO. Boot your server from the flash device and install the OS to preferably an SSD. When given the option, opt to create the admin password in the installer (do not select the option to "Configure using WebUI"). Remove the flash device and reboot your server when the install is complete. From another device (mobile, tablet, desktop) that is on the same LAN as your server, login to https://deck.hexos.com using your HexOS credentials. Follow the instructions to complete your server configuration. NOTE: As of the 24.10.2.2 build of this ISO, configuring the admin password via the webUI option has been removed from the installer. However, if you select to create an admin password, but then attempt to "cancel" that process, the ISO will proceed with an installation with no admin password set. This is a known bug and the TrueNAS team will be addressing this in a future update to the ISO. Just don't cancel out of creating the admin password in the installer ;-). Hardware Requirements Booting HexOS is designed to support a wide variety of x86 hardware (Intel or AMD). The minimum requirements are a 2-core 64-bit CPU, 8GB of memory, and a 16GB or larger SSD boot device. However, depending on your needs for performance and applications, more resources may be required. Storage Pools Pools are made up of storage devices based on size and type (HDDs vs. SSDs). Storage devices in each pool need to be roughly the same size*. The OS boot device cannot be a part of a pool. Expandable pools require a minimum of 3 devices and can be grown one device at a time. Non-expandable pools can be created with 2 devices. Initial pool width should not exceed 8 devices. Maximum expanded pool width should not exceed 12 devices. At least one storage pool must be created to use HexOS. *In the event of slight variations (e.g. 240GB and 256GB), devices can be grouped, but total capacity for the pool will sacrifice the larger device’s excess storage. Build Recommendations HexOS has been designed so that a relatively modern PC can be easily transformed into a very viable home server. This means using standard HDDs/SSDs and using onboard controllers for storage/networking. However, since we’re based on TrueNAS, our hardware support is actually rather vast. For more detailed hardware recommendations for advanced builds, please refer to the TrueNAS SCALE Hardware Guide. Installing in a VM As HexOS is based on TrueNAS SCALE, it can be installed as a virtual machine as well. While the process should be fairly self-explanatory, please see the TrueNAS SCALE documentation for additional instructions on VM installation. Setup and Configuration Once the OS has been installed and rebooted, you will use a web browser on the same network as your server to register your system and complete the setup process. This can be a PC, tablet, or mobile device. Using a capable browser, login to https://deck.hexos.com. Beta 1 Features Our first release is focused on providing a streamlined user experience for setup and configuration and laying the framework for what’s to come. The main features of Beta 1 include: Setup and configuration wizard Configure your home server in minutes with ease. Analyze system health, with warnings for SMR HDDs. Auto-configure storage pools to safeguard against device failures. Securely manage your server remotely via Command Deck. Storage device management Detect error states and conditions and report through the dashboard Highlight individual storage devices and their respective faults Replace devices from storage pools due to failure or preventative maintenance Expand pools as little as one device at a time Folders and users Create and share folders over your local network. Easily manage permissions for secure access. Apps One-click deploy Immich as a personal photo library app. One-click deploy Plex as a home media server. Automatic folder creation for app storage. Dashboard / UI Access key statistics like CPU, memory, network, and storage usage at a glance. Monitor storage health and see alerts for errors or degraded pools. Manage multiple servers from a single, unified interface. Enjoy mobile-responsive design for effortless navigation on any device.

For detailed installation instructions, please refer to this thread: Illustrated Installation Guide - START HERE! =)

Agreed. When creating a VPN connection, have options to route specific apps with this connection, or the whole system, or whole system but exclude specific apps.