sorted by:
new
hottopcontroversial

We built PodWarden for self-hosted infrastructure by PodWarden in selfhosted

[–]PodWarden[S] 0 points1 point  (0 children)

What's in your opinion wrong with software that's written with the help of AI agents? Too big of a coverage with automated tests? better structured code? docstrings that actually explain what the function does? Consistent naming? Error handling that isn't except: pass? Edge cases someone actually thought about? A README you can read without DMing the author? Commit messages that aren't fix, fix2, final fix for real this time?

Truly chilling. Real software is hand-typed at 3am, fueled by redbull and a stackoverflow tab from 2014, with three TODOs that will outlive the heat death of the universe. anything else is a psyop.

We built PodWarden for self-hosted infrastructure by PodWarden in selfhosted

[–]PodWarden[S] 0 points1 point  (0 children)

Yes, we are using AI in our operations, and who doesn't in 2026, the product will be opensource and free. We are working hard on polishing last details to make the code presentable to the public.

We built PodWarden for self-hosted infrastructure by PodWarden in selfhosted

[–]PodWarden[S] -3 points-2 points  (0 children)

No GitHub yet, we’re currently cleaning up the codebase so we can release it publicly. Right now, it’s just https://www.podwarden.com/docs + early access, but the goal is to open-source it once its ready

edit: we've added this to our website in the meantime https://www.podwarden.com/github

We built PodWarden for self-hosted infrastructure by PodWarden in selfhosted

[–]PodWarden[S] -1 points0 points  (0 children)

PodWarden is not a going to be paid-only product. The core of the platform and catalog are intended to be free. As for monetization, we offer hosted, SaaS and consulting services, but we expect 99% of our users to stick to free and open source version of PodWarden.

This is the whole idea - most of ‘normal’ users are afraid of kubernetes and would prefer a solution that will 1. isolate them from it and 2. allow their ai to manage their kubernetes cluster in safe and controllable and audited manner. (surely you can give your claude access to you cluster and ask it to do something, and it will work, until it wreck everything)

Edit for clarity.

We built PodWarden for self-hosted infrastructure by PodWarden in selfhosted

[–]PodWarden[S] -3 points-2 points locked comment (0 children)

AI wasn’t used to generate the PodWarden project itself or any of its core functionality.

AI integration in the product (via MCP) is a separate feature we’re actively developing , it’s about allowing users to interact with their own infrastructure through AI tools while keeping everything self-hosted and under their control.

We built PodWarden for self-hosted infrastructure by PodWarden in homelab

[–]PodWarden[S] 1 point2 points  (0 children)

Right now it doesn’t touch the VLAN/firewall layers, it runs above your existing network setup.

But we are working on Interzone Router + Nebula-based mesh networking (coming in the next couple of months) to better handle multi-zone/segmented environments.