
Authex: Autonomous DMARC Enforcement
Automatically configure email authentication to prevent spoofing and improve inbox delivery.
@okamigenshin · X
Try Authex, for securing your domain and email autonomously.
The full gallery
Tech stack
21 projects

Automatically configure email authentication to prevent spoofing and improve inbox delivery.
@okamigenshin · X
Try Authex, for securing your domain and email autonomously.

Grade a domain's email protection: check SPF, DKIM, DMARC, and MX records in your browser.
@domainfyrbrand · X

Runs AI agents on your repos to automatically improve code and ship merge-ready pull requests.
@javimosch · X

Access open-source AI models developed in China through a privacy-focused API service.
@Jenny5143197635 · X

Scan websites for accessibility and privacy compliance issues using AI.
@tobio_ojebiyi · X

Check AI agent outputs and actions against your policies before execution; get allow, block, rewrite, or escalate decisions.
u/danielbaker06072001 · Reddit
Most AI agent SaaS is just bad security with a nice dashboard Give a new employee access to Stripe, GitHub, Slack, and your CRM on day one, and you’d call it reckless. Give the same access to an AI agent, and we call it “autonomous.” That isn’t innovation. It’s skipping basic security because the demo looks cool. Full disclosure: I’m building TrustLoopGuard around this problem, so I’m obviously biased. While testing one MCP connection, I realized I had decided what the agent could a

Trace, replay, and verify AI agent decisions with signed audit trails.
u/Funky_Chicken_22 · Reddit
OSS to SaaS positioning problem: when the user persona and the buyer persona are completely disjoint Founder here. Sharing a positioning problem I think a lot of OSS-to-SaaS founders hit and don't talk about publicly. Context: I have been running an OSS project (world-model-mcp) with ~2,500 monthly PyPI installs. Two weeks ago I opened up the hosted companion, Etch, at etch.systems. Launched publicly on Product Hunt at 12:00 PDT yesterday. The positioning problem: OSS user persona: in

Autonomous agents that detect and prevent compounding business risks.
@UNgethe · X

Generate EU AI Act compliance documentation for your AI systems.
@Moha__niang · X

Prevent context loss and AI agent amnesia. StateSync provides real-time state persistence and agent handoffs over MCP.
@StateSync_ · X

Track and automate closing accounts and notifying companies after someone dies.
u/r0b074p0c4lyp53 · Reddit
Next-of-kin account settlement tool Hey all, first time poster, be gentle. After watching my mom deal with the nightmare of closing accounts and notifying companies after my dad died, I started wondering why there isn't a better way to do this. So I built Afterglow.rest. You add the accounts that need handling — IRS, credit bureaus, utilities, subscriptions, whatever — and we research the actual notification process for each one (using AI to do that legwork, since every company has a diff

Adds a human approval step to AI agents, scripts, and CI/CD pipelines with durable inbox and signed callbacks.
u/king4queen · Reddit
Human Approval (HITL) for AI and autonomous system. I kept running into the same annoying problem with scripts and automations: Everything works fine until the software needs a human. Then suddenly I’m building the same stuff again: send a Slack/email notification save some pending state wait without losing the workflow show enough context to make a decision approve/reject/answer something somehow send that answer back handle retries, timeouts and duplicates So I start