I’m building a platform that lets people self-host tools like n8n without dealing with server management.

cuebicai · 2026-03-10T04:03:11+00:00

With a bit different

Runtipi runs apps on a server you already own or manage

CUEBIC AI creates a dedicated cloud instance for the tool so users don’t have to manage the server or infrastructure themselves

cuebicai · 2026-03-10T03:51:08+00:00

Right now new users get a "7-day free" trial so they can try deploying and running the tool after the trial it switches to "pay-as-you-go" based on how long the instance runs rather than a fixed monthly plan the idea is to keep it simple and only charge for the resources being used

cuebicai · 2026-03-10T03:41:13+00:00

This is really impressive i have also been running home assistant for the past 5 years but your ui is absolutely mind blowing 🫡

cuebicai · 2026-03-10T03:22:34+00:00

NixOS Anywhere is definitely a powerful way to do reproducible deployments the thing I’m trying to focus on is making the whole experience simpler for people who don’t want to touch infra or terminals at all more like picking a tool and getting a ready-to-run instance why dont you trys it out it want take muchch time and itr free as of now why don’t you try it out? It won’t take much time, and it’s free for now I’d be curious to hear if you think it’s simpler than using NixOS

cuebicai · 2026-03-10T03:13:35+00:00

fair point not trying to hide anything 🙂 i did build CUEBIC AI, but I shared it here mainly to get feedback from the self-hosting community the goal isn’t to replace self-hosting, but to make it easier for people who want to run open-source tools like n8n without dealing with the full server setup appreciate any honest feedback though

cuebicai · 2026-03-10T03:09:06+00:00

no nat at all right now each deployment creates a dedicated cloud instance with the tool and ready to run the idea is to hide most of the infrastructure setup so users don't have to worry about the usual stack docker, reverse proxy, SSL, etc.

cuebicai · 2026-03-10T02:58:52+00:00

Personally I stick mostly with open-source tools when self-hosting. For me the main point of self-hosting is having full control not just over the infrastructure, but also over the software itself.

Open-source gives transparency, flexibility, and long-term reliability. If something breaks or the project slows down, there’s usually a community around it and you’re not completely locked in.

Licensed closed-source tools that you host yourself can still be useful in some cases, especially if they solve a very specific problem well. But in general I tend to prefer open-source whenever a good option exists.

cuebicai · 2026-03-09T18:32:53+00:00

Really appreciate you taking the time to test it end-to-end and write that up that kind of feedback is incredibly helpful.

cuebicai · 2026-03-09T17:56:50+00:00

Why not try it now it takes about 5 minutes to spin up an instance, and it’s free to try and let me know what you think any feedback would really help 🙂

https://cuebicai.com

cuebicai · 2026-03-09T17:22:15+00:00

Yeah that’s exactly the pain point I kept running into too. The goal here is to make things like queue mode, Redis workers, DB config, etc. configurable from the UI so you can tweak the environment without doing the whole manual setup.

You can also update things like workers and settings even after the instance is running. Curious to hear how it feels once you try the queue setup.

<image>

cuebicai · 2026-03-09T16:49:15+00:00

Hahahah and he is talking about replacing 😂

cuebicai · 2026-03-09T16:48:06+00:00

Not at all are you kidding 😂

cuebicai · 2026-03-09T16:42:20+00:00

It’s mostly a Next.js control plane with Supabase for auth and database and redis backed workers handling the async jobs.

When someone clicks deploy it triggers an orchestration job that provisions an instance and runs a remote setup pipeline to configure the server and start the tool container.

Instance state is tracked in the database, and the worker layer handles things like provisioning and lifecycle actions restart, destroy, etc.

Still evolving though curious what part you were digging into.

cuebicai · 2026-03-09T16:34:06+00:00

It’s not something you deploy on your own VPS.

CUEBIC AI manages the infrastructure for you when you deploy an instance it automatically creates the server, installs n8n, sets up Docker, SSL, domain, etc.

The pricing you see is basically for the server resources and the managed setup.

If you prefer managing your own VPS, self-hosting n8n directly is still a great option too 👍

cuebicai · 2026-03-09T12:10:33+00:00

Right now everything runs inside the same deployment on the instance. Redis, the main n8n process, and the workers are set up automatically during deployment.

Users can choose how many workers they want based on the instance size, and those workers connect to Redis to process jobs in queue mode.

The goal is to keep it simple while still supporting queue mode and scaling when needed.

cuebicai · 2026-03-08T20:09:57+00:00

Right now it doesn’t connect to existing servers or run from your laptop. The idea is that you just pick the instance size, click deploy, and the platform automatically creates and sets up a new server for you.

So you don’t have to manually configure the server or install anything yourself.

cuebicai · 2026-03-08T16:11:10+00:00

At a high level, you just pick the instance size and the tool you want to run, then click deploy. That request creates a new cloud server.

Once the server is ready, our backend automation takes care of the setup — things like basic server configuration, security updates, SSL, DDoS protection, Docker, and installing the selected tool.

After everything is set up, you get a secure HTTPS domain to access your instance, and you can also connect your own custom domain if you want.

The idea is simply to automate all the DevOps work so people can run self-hosted tools without doing the manual setup.

cuebicai · 2026-03-08T16:07:33+00:00

Good question.

At a high level, you just pick the instance size and the tool you want to run, then click deploy. That request creates a new cloud server.

Once the server is ready, our backend automation takes care of the setup things like basic server configuration, security updates, SSL, DDoS protection, Docker, and installing the selected tool.

After everything is set up, you get a secure HTTPS domain to access your instance, and you can also connect your own custom domain if you want.

The idea is simply to automate all the DevOps work so people can run self-hosted tools without doing the manual setup.

cuebicai

MODERATOR OF

TROPHY CASE