jonp

We have no editorial input or control over the LTT videos. We don't pay for sponsorship or anything like that either. The fact that it came out this weekend was pure happenschance. We are looking into the SMB issue and will see what we can do from our side to address. Tbh, what we have planned for the rest of the year is going to have an even bigger impact than the 1.0 release in my mind. With respect to price, an announcement about our scheduling pricing changes will be coming soon.

@mill3000 let's take a look at his issue this week.

All we can say at this point is we are slowing rolling out local to new users. Over 400 so far have been migrated.

I did say BY end of April ;-). Truth is we have been pretty much right there aside from a few issues, but the big one was the availability of HexOS Local. But we decided yesterday that we can still call this 1.0 and roll out Local to everyone over time. The local project has to be rolled out more slowly as we have SSL cert issuance limits right now.

https://docs.hexos.com/blog/2026-04-02.html

https://docs.hexos.com/blog/2026-04-02.html

I appreciate the understanding. I'm actually in the process of approving the post right now. Had a full day packed so it had to wait until tonight.

I'm out of town right now but let me just state that I totally get the folks that are upset. Honestly, writing blogs is pretty stressful for me as we constantly are working on moving targets and I stress over communicating about things that are still in flux and getting the words right. Tbh, I stress over comms in general. It's nerve wrecking. It's why I am earmarking funds this year to bring someone in to handle this for us. I just didn't want to spend any money on non dev/support resources until we got to 1.0. Again, I get it and I am not gonna make any excuses for it, so if you want to be mad, please direct that anger at me, not my team. They are busting their butts to get this thing polished and rolled out.

This one is entirely on me. I am traveling today but I will be working on getting this blog post up tomorrow (April 2nd). I'm also planning to hire someone to take over marketing/comms this year as a full time position.

Working on a blog post with an update. We had to push back to April due to some issues with our health system that we've been tracking down since February. The plan is to both begin the rollout of HexOS Local and complete the health system upgrades and then release 1.0 by end of April. I was hoping to get a blog up today with all of this information, but it just didn't come together fast enough.

At this point, just using HexOS to create folders, users, install apps, etc. just like normal. Use it both locally and remotely. That's really it. At this point, the main thing we're testing is that it works correctly, navigating you to the local interface when on LAN, and giving you remote access via the deck when away. If you can break your system (non-critical data only), there are a few specific cases we would like to see users test like destroying the pool used by apps (Docker) manually via TrueNAS, then renavigate to deck.hexos.com to see if you can remediate the issue. Obviously not asking anyone with real data on their systems to do this, but for those that have test setups, just beat the heck out it and see what breaks. We test internally pretty rigorously, but there's always edge cases that we can miss and this is the chance to find those as best we can.

Should be no risk to data loss at all. The biggest risk is getting disconnected from our deck for server administration. That's why we want users to be able to talk to us via discord so that we can quickly remediate those types of problems if they occur. The big switch here initially is going to be authentication. We're moving to key cloak and we set up a more robust infrastructure to enable us to migrate users between production and development environments very easily. While we've done a ton of internal testing on this, we just want to be extra cautious before doing a mass migration of thousands of users all at once. Technically this is still pre 1.0, but the only things that really remain for us are hexos local and some improvements to our health monitoring systems.

We are extremely close to releasing HexOS Local, our solution for accessing/managing your HexOS servers through a locally installed application on your server. Before we roll this out to all current users, we are looking for a handful that are able/willing to help us test the migration process. The requirements are pretty simple: 1) Users that agree to enroll in this early access test will have ALL of their servers migrated (we cannot apply the test to just a single server, so if you have multiple, it's all or nothing). 2) Users must have a discord account as those accepted will be invited to our new discord server for the purposes of bug reporting and support needs. If you are interested in helping us test this, please drop a DM to @mill3000 with the subject "HexOS Local Early Access" and be sure to include your Discord username in the message. Any questions, post them here! Thanks everyone!!

First, let me start by saying I actually really appreciate this question and I hope my answer gives you faith in our long-term sustainability, exactly as you mention in the title of this thread. The lifetime license model is appropriate for a very particular type of customer with very specific priorities: Bring your own hardware Doesn't want an ongoing subscription Will mostly support themselves It was the appropriate model to launch with as well because it allowed us to inject a larger cash infusion at the start. However, we see multiple additional revenue streams available to us in the future: Subscription-based licensing. A lower price of entry for customers that aren't ready to make the lifetime commitment. Support. A more premium support model that can help you on a 1:1 basis when you have issues with your server. Cloud-based Services. Things like cloud backups (as an alternative or in addition to buddy backup). There are other cloud-assisted services such as reverse-proxy/relay that may warrant a subscription as well. Hardware products We will never force anyone to buy a specific hardware product to use HexOS, but we may offer some for those that don't want to build their own in the future. We actually have a few other ideas for additional offerings as well that would add additional revenue streams to Eshtek, but those are a little premature to discuss at this point. Bottom line: we don't just have a product plan, we have a full business plan for the future of this company and it has been designed to ensure a few key things: We don't run out of cash. We don't have to take on outside investors. We can remain true to our mission and vision. I hope this answers your question and gives you more confidence in our plans for the future. And if you have any other questions, don't hesitate to ask!

For us to dig deeper, I'd like you to report back with your hardware configuration as well as confirm what version of the OS you are running (25.10.1 or earlier?). There were some issues with the TrueNAS SCALE network reporting graphs in earlier releases. We'd also like to see a packet cap or something more than just a domain to prove what you're claiming here. Maybe wireshark monitor? Did you configure anything within TrueNAS SCALE's UI itself at any point or did you just utilize the HexOS dashboard for all your needs? Lots of things could account for the disk activity itself (such as background tasks or maintenance operations like the scrub that happens by default once a month) but the network activity is not us. StorJ is the used by TrueCloud if you configure your server to use it for backups (not something we support via HexOS today at all). Furthermore, the storj connection and the websocat connections are independent of each other. Websocat is used to make an outbound connection from a HexOS server to our Command Deck as outlined in one of our earlier blog posts here: https://docs.hexos.com/blog/2024-07-30.html. That's it. We do not and cannot transfer your data via that connection. The entirety of that connection is to give us API access to manage your system via our interface at deck.hexos.com. This ties back to something in TrueNAS and not anything with HexOS. Once you've unclaimed your system, we no longer have any access to do anything with your system. Generally speaking, it was quite an alarmist post and makes some pretty aggressive claims about data being "exfiltrated", that we were "misleading" about our product, and that you haven't seen any "meaningful updates." This was stated in our very first blog post that I previously linked but you won't by reliant on deck.hexos.com for long: https://docs.hexos.com/blog/2025-11-25.html. Furthermore, having a management interface hosted via cloud doesn't go against self-hosting as a concept. All of your data and applications are still running local on your LAN, which gives you the value of self-hosting. Management interactions for most customers are limited to initial setup of storage, folders, users, and applications. Once running, users mostly just interact with the applications and data, which run entirely local. Ultimately we want to know if this is a real bug/issue that ties back to TrueNAS SCALE so we can escalate to the right people or if this is simply a misunderstanding or misconfiguration. In reviewing multiple test systems we have configured and going back over a month in the network reporting, we see no significant network activity that matches anything close to what you are reporting.