Rainy MaTE

For a while, I kept building Rainy MaTE in private.

Part of it was wanting the product to be stronger. Part of it was honestly fear — that founder loop of thinking one more week, one more improvement, one more feature, and then maybe it’ll be ready.

This time I decided to stop doing that.

I finally launched Rainy MaTE publicly on Product Hunt.

What started smaller evolved into something much more ambitious: a local-first AI system built around autonomy, memory, tools, specialist coordination, and controlled execution.

A big frustration for me with many AI products is that they’re good at replying, but weak at actually operating. They lose context, struggle across longer sessions, and often feel like chat interfaces with extra steps.

That’s the gap I’m trying to close with Rainy MaTE.

Whatever happens with the launch, putting it out publicly already changed something important: it forced me to stop polishing in private and start getting real feedback.

Now the focus is traction, distribution, and learning fast.

If you’re building in AI, local-first software, devtools, or anything around autonomy, I’d genuinely love your thoughts.

Launched here on Product Hunt: https://www.producthunt.com/products/rainy-mate

I hit "SaaS fatigue." I realized I was paying monthly subscriptions for AI "wrappers" that were essentially just chatting with GPT-4, but with the downside of uploading my private files to their cloud.

The Solution: I spent the last few months building Rainy MaTE. It's a local-first AI workspace built with Rust & Tauri that lives on your machine, not in the cloud.

The Stack:

• Core: Rust (for file ops & stability) + Tauri (v2).

• Frontend: React 19 + HeroUI.

• Brain: BYOK (Bring Your Own Keys). Supports Gemini 3, OpenAI (o3/GPT-4), and Groq (Llama 3) and powered by Rainy API.

Features:

1. Stop Renting: You pay $0/mo to me. You only pay the API providers for what you actually use.

2. The "Airlock": A permission system I built so the AI can't delete or modify files without your explicit approval.

3. Stateless Bridge: I wanted to control my PC from Discord/Telegram while away, but I didn't want a cloud server storing my data. I built a stateless relay that forwards encrypted commands to the local desktop node. Zero data retention in the cloud.

Why Open Source? Because an AI that has access to your file system must be auditable. You shouldn't trust a closed-source black box with your hard drive.

Looking for feedback on:

• The "Airlock" permission flow (is it too annoying?).

• The Rust implementation of the file operations.

🔗 Repo: Rainy MaTE 🌊 Site: Rainy MaTE

Thanks for checking it out!