If you have bench marked your applications and setup the off site backup properly. I think its pretty much doable.

Can you please give some more context? Like whats the tech-stack of your Applications? Is it Monolith or Microservice? ETC...

I can choose whatever stack I see fitting. Our current app runs on an old Laravel version and an old Vue version. Its a monolith. Privately I have built microservices too, but this architecture only really makes sense with bigger teams. I have spent about 70% if 2025 learning Elixir and I'd love building some real life things with it.

Hi HN,

I just published a blog post about an idea I've been developing to solve a workflow problem I face as a developer juggling multiple clients.

The short version is that using full VMs for each client is resource-heavy and clunky (no notifications, hardware issues), but it provides great isolation.

My post outlines a concept for a "productivity-focused" OS inspired by Qubes, but built on lightweight LXC system containers. The goal is to get the strong isolation benefits without the performance overhead, using a custom desktop environment to handle things like unified notifications and managed hardware access.

I'd love to get this community's feedback. I'm particularly interested in your thoughts on these questions:

  1. Does this problem resonate with other freelancers, consultants, or multi-project developers?

  2. Is using LXC the right approach, or is there a better technology for this?

  3. What's a must-have feature for you if a system like this existed?

Thanks for taking a look!

Hi!

Awesome thoughts!

I think you should look at qubes-os, it would be nice to have their concept with LXC or maybe with docker/podman to more efficient image storage with shared layers and so on

Apache NIFI.

It should be used more for building Data Pipelines specifically.

I haven't used it in years but when I did, it was an absolute nightmare to work with, especially with respect to version control. There was no good way to version control their "templates", and collaborating was always painful. Not to mention the interface felt like it was from the 90's and dreadfully slow and painful to maneuver. The underlying functionality it permitted was quite good though. A facelift and a better version control scheme would help a lot.

Interesting, will check it out.

Few days ago I was litterally searching same thing and I was thiking same thing how come there is no solution out there with a reasonable free tier.

I just signed up and I am gonna use it going forward almost everywhere.

I would suggest you should create something pay wahterver you can tier. This can help you get some more funds.

Google docs is about to roll out their own version of this within Workspace

Apache NIFI (https://nifi.apache.org/).

It uses the concept of Flow-based programming. Also its so underacknolged but this tool is very flexible. I have used as an Event Bus all the 3rd-Party Integrations.

I was about to reply same before solving 99% of world problem. Please look into why your site is taking this much time to load...

+1 for linux

Nice strategy. I used to be in a large DevOps team and similar startegy was the eventually adopted.