Sovereign AI Overseer

Zero-Trust WP Security: WebAuthn + Gemini AI Sentinel

2 followers

Zero-Trust WP Security: WebAuthn + Gemini AI Sentinel

2 followers

Stop bleeding margins to "forgot password" tickets and botnets. Sovereign AI Overseer replaces WP passwords with native WebAuthn (Face ID/Touch ID) and Zero-Knowledge recovery. It includes an autonomous Gemini 1.5 Pro AI Sentinel deployed on your GCP (BYOI) to ban threats in real-time. 0$ idle server cost.

Payment Required

Launch tags:WordPress•Developer Tools•Security

Launch Team / Built With

Viktor.comAn AI coworker that actually does the work

Promoted

Maker

📌

Hi Product Hunt! Antonio here. After 25+ years as a Systems Architect, I got tired of watching agencies bleed profit margins to "forgot password" tickets and brute-force botnets on WordPress. Passwords are a legacy vulnerability. So, I architected Sovereign AI Overseer. It completely deprecates the password field, replacing it with native WebAuthn (Face ID, Touch ID, Security Keys) backed by a Zero-Knowledge 12-word recovery phrase. But I didn't stop at authentication. I added an autonomous Gemini 1.5 Pro AI Sentinel. Using a BYOI (Bring Your Own Infrastructure) model, agencies deploy a serverless container to their own Google Cloud Run. The AI reads HTTP headers and autonomously bans threats via a 403 firewall. You keep 100% of the margins, pay $0.00 in idle server costs, and guarantee total data sovereignty to your clients. I originally architected this for the Google Build with Gemini XPRIZE. Now it's ready for production. I'd love to hear your feedback on the architecture!

Report

2mo ago

Forum Threads

p/sovereign-ai-overseer

•

2mo ago

Why I killed the WordPress password field for good (and let Gemini AI handle the botnets) 🚀

Hi everyone! Tomorrow I m launching Sovereign AI Overseer, but I wanted to start a discussion today about a massive vulnerability we all just accept as "normal": Passwords.

If you run an agency or manage client sites, you know that "forgot password" tickets and brute-force botnets eat up your profit margins and server resources. Rate-limiting is just a band-aid.

I decided to deprecate the password field completely.

In my new architecture, I replaced it with native WebAuthn (Face ID / Touch ID). For active threats, I deployed a serverless Google Gemini 1.5 Pro AI Sentinel via a BYOI (Bring Your Own Infrastructure) model on Cloud Run to autonomously ban IPs in real-time.

View all