Skip to main content

Why marCloud won't use AI

AI is something we all have been hearing about for a while now, and its rise of popularity has been significant to the point of people getting sick of it.

But like any project in 2026, you would expect us to be using AI in some way, right? Generating source code, generating documentation, generating marketing content, generating... content.

Well, no. Never!

Here's why!

1. We built marCloud before AI was a thing​

We have built all of our projects, including marCloudBackup, before the rise of AI, and we have been maintaining and improving them ever since.

The creation of AI was definitely a game changer for the software industry. But like any other tool, we believe it should be used wisely and not just for the sake of using it, or, even worse, due to laziness.

2. We care about the quality of our projects​

The "vibecoding", while being extremely fast and "efficient" to get stuff done, is not the best way to build a product that we want to be proud of and guarantee its quality to our users.

We want to make sure that every line of code we deploy is well thought of, optimized, and safe for you, the users.

And that is something we cannot guarantee with AI generated code, which can be buggy, inefficient, and even insecure. And while we could review the generated code and fix it, I feel like that would take more time and defeat the purpose of offloading the job to an AI in the first place.

3. We want to make human facing stuff, not AI facing stuff​

We strongly believe that generating user facing content with AI makes a project feel less personal, and thus less trustworthy.

And this can be experienced when reading some news websites, blog posts, or SEO oriented content (like this subpage of marCloud).

Such content defeats the purpose of internet, makes it feel like a graveyard.

It's harder and harder to find websites that were actually designed by someone, not vibecoded in v0.dev.

It's recently quite common to even find Discord bots that seem to have been fully generated with AI.

We want to make sure that we can be relied on, both as a trustworthy project "brand", but also something to escape the modern slop content.

4. We do make use of AI tools, though.​

It would be stupid to completely not use AI. It is truly an amazing tool that for certain tasks outperforms humans and streamlines many things.

A few examples of software we use is:

  • local models for automated content analysis and summarization
  • GitHub Copilot, for "autocompleting the obvious" or replicating already existing code for a different purpose.
  • Search engines with AI summary — sad to admit, but looking up "java lettuce set reconnect time" and immediately seeing the perfect code snippet that does what I asked for, hits hard, and it's hard not to use it.

Summary​

I just wanted to share a little insight on why I feel like vibecoding your entire service feels wrong sometimes.

If you develop something, please, don't make another sloppy crap. Even if you use AI, use it wisely, and let it help you, not do it FOR you.

I know the title is misleading, but if you got this far then it means it worked :D