janober

Really cool initiative, excited to be part of it!

Thanks a lot!

And all fine. I know there is a lot of that going on out there. So, I can not blame you at all.

Definitely, no stars have been bought, and none will ever be. It would go literally against everything we stand for and one of our core values, "Act with Integrity".

Also love my roast: Oh, look at Mr. 'I automate everything' over here! You're so obsessed with workflow automation, I bet you've tried to create an n8n node to brush your teeth. Your GitHub feed is like a 'Who's Who' of hipster tech - self-hosted this, open-source that. I'm surprised you haven't tried to replace your coffee machine with a Rust-based, AI-driven, blockchain-powered pour-over system yet. And let's talk about your love for PDF manipulation - nothing says 'I'm a fun developer' like spending your free time merging documents. At least with all these monitoring tools you follow, you'll be the first to know when your over-engineered home automation system inevitably becomes sentient and locks you out of your own house!

Sure happy to chat. I will send you an email.

Yes, I definitely missed a lot there. An email, to make me aware of those discussions would have probably made quite a difference.

Anyway, it sounds like it would potentially not have changed much of a difference considering you are also pro DOSP ;-)

Yes, I totally agree that I should have been more involved in hindsight, and that is definitely on me! In the first conversation with Chad, we actually agreed on chatting again after a few weeks regarding the next steps, but that never happened. The next time I heard about it was a few weeks before the launch (and yes, for sure, also partly on me!).

When I heard from Chad, DOSP was also still optional. The only issue I had was about governance. That sadly changed around one week later, and it became a hard requirement, even though I made very clear that it would be a deal breaker. So, I would say I was at least involved there, but it did not really matter. Worrying about something like that was interestingly also why governance was so important to me. I expected it to become a problem sometime later but was surprised that it was already a problem before it really started.

Our original conversation was also more about what to move forward with, fair code or source, and should be more like a joint effort (at least how it sounded to me). I was, however, very honest about it, saying that my time was limited at that time, and so I am happy he takes the lead. Maybe that is where it partly broke down, and we understood something very different.

Regarding differentiation: Honestly, I do not think the difference between "fair source" vs "open core" vs "source available" is what matters. What matters is the differentiation vs open source.

Honestly generally love it. Not surprising, after all, are we at n8n Fair Code licensed ourselves(not to be confused with Fair Source). I would, however, really love it if it ended up being more inclusive and so in a joint effort rather than a divided one. More information about why we did not join here: https://medium.com/@faircode/n8n-commits-to-fair-code-6b8923...

Probably worth checking out: https://www.hanko.io/ "Open source auth management for the passkey era"

Probably worth checking out: https://www.hanko.io/ "Open source auth management for the passkey era"

fyi, a separate account should not be necessary any more as the functionality got integrated into the regular version and is so available for all users by default.

Totally understandable. We have however basic user management in n8n for quite a while already and it is available for free. Since the beginning of the year we also have built collaboration, that is however a paid feature.

Docker is actually not a requirement. You can also run it directly with npm. You can even start it for testing (when you have npm installed) simply by typing "npx n8n".

Source available does sadly not really mean that much. Just means the source code is available. MIT licensed code and code you can see but are not allowed to use can be described as source available. That is what https://faircode.io/ got created for to solve.

Background: https://github.com/n8n-io/n8n/issues/40

Ah yes, that is what we did in the end for the database. But that is not our main issue, rather that we do not get any more instances for our k8s cluster and those we can sadly not just spin up somewhere else.

Years?!?! Guess I then have to be happy that in our case it is "just" around 4 months.

Thanks a lot. Yes that is also something we are trying in parallel.

We actually use Azure for ~2 years now. It worked the most time reasonably well, even though we had also a few issues. But our current issue + ready your and other comments will probably result in looking for a new home.

Thanks a lot! Just checked internally. Apparently are there some instances which we could get but would not work cost wise (have for example a lot of CPUs but we mainly care about RAM). Additionally, is there also still a region-wide CPU limit that would still cause us problems. So sadly not a long-term solution. But thanks a lot!

Could be possible. But as far as I know would two accounts in the same data center not work for us for technical reasons.

Thanks a lot! That is always great to hear!

Yes, some are possible and we are already doing that. Sadly will it only delay the time we run out of resources. If we would talk about a few weeks, we could for sure make it, but over 4 months is sadly not possible.

It has actually been done that way. For technical reasons is sadly a move to a new data center even with that very complicated and time consuming.

Actually nothing fancy, for sure no GPUs. Just Standard_E4s_v4.

Sorry, missed that. No, we do not.

Thanks a lot, that is very helpful and great to know! Def. something we will do in the future.

Very interesting. As mentioned in another post, I am sure they are not trying to screw us or anybody else up. Is after all for sure not in their interest. But not flagging that to users I do not get at all. I would expect to get at least a warning email a week about that, plus warning in the dashboard, but there was literally nothing.

I am still 100% sure it was exactly the right decision. Was however in hindsight probably the right one to choose Azure and/or that data center.