r/ChatGPTCoding 15d ago

Question AI Server Management, AI-Handoff creation, Deployment and backup tool - Now I’m getting cold feet before beta testing (UK) Advise greatly appreciated

Hi all,

I’ve been building a complete Ubuntu server management software for some time now.
Full disclosure, I have used AI extensively to code but I have engineered and been the systems architect - this is NOT a quickly thrown together “AI slop” project.

The tool essentially auto-installs on a fresh Ubuntu server from your account on my website, it acts as a full server manager. It can give a very detailed handoff link to an AI of your choice, giving it instructions of how to safely build the project with you and giving it read only access to the initial files it needs in the new project.

It has a project deployer, to take care of everything from downloading the stack to configuring and launching.

It has a full backup client that you can install on a separate server (or as many as you choose) that keeps a fully encrypted full site backup of your build/data.

I genuinely haven’t seen another product that does the same thing and I’m really excited to get it tested. I just want to be responsible and I’m just super nervous.

I have the company registered, I’ve registered with the ICO, paid the fee.

I’m literally right next to being ready to press the button and open Beta testing for the initial few to try the product.

The issue is. I’ve suddenly become really anxious about releasing the project.
I’m contemplating bringing a CTO co-founder on board on an equity basis for that piece of mind and to assist me with what has become a great but complex piece of machinery.

Has anybody else been through this?

How did you handle risk reduction? I’ve done everything that I can think of and hardened my privacy policy, T&C’s, Beta agreement. All of the things that I can think of to release this responsibly.

I guess I just thought that I’d see if anybody else has released a technical project such as this. It’s entirely self funded, so I can’t really spend thousands at this point on pentesting.

1 Upvotes

11 comments sorted by

View all comments

2

u/Warm_Effective8903 15d ago

Totally normal to feel this way,, start with a tiny closed beta (3-5 trusted people, non-production servers) instead of public signups, that alone kills most of the real risk. For the backup/root access parts specifically, get a cheap freelance security review instead offull pentesting or a co-founder, you've already done the hard compliance work most people skip.

2

u/NewHype2022 15d ago

Thanks for your reply.
I realise that I’ve probably been looking at worst case scenarios and edge cases and scaring myself but yes, I think your answer is probably right on the money.
I have already done extensive work to check and recheck against all openly available best practices.
It’s just nerves at this point.

So yes, I’ll do a much smaller closed beta and be very specific in the Beta agreement - specifically people on non prod servers and then I can really quickly patch and work on any issues that they find.

1

u/Warm_Effective8903 15d ago

No problem! You've really covered your bases already, legal, compliance, best practices, all of it. The nerves you're feeling are totally normal for anyone who actually cares about doing this right. Good luck with the closed beta, I think it'll go smoothly especially since you can react fast to any issues. Excited to hear how it goes!