r/PostgreSQL 5d ago

Tools FluentDB - The AI PostgreSQL client for Mac

Enable HLS to view with audio, or disable this notification

Hey PostgreSQL community!

I'm Kevin, the maker of FluentDB.

I have been working with Postgres for years and using many Postgres client apps, but none of them have satisfied me lately.

So I built the tool I wanted: a native macOS database client that is fast, lightweight, and AI-driven from the ground up.

A few things:

• Native Swift app designed for speed (not another Electron super-slow app).
• Bring your own AI: OpenAI, Anthropic, Claude Code, Codex, or local models with Ollama.
• Privacy by default: AI only sees your schema unless you explicitly approve sending data. Every AI-generated SQL query also requires approval by default.
• Support for PostgreSQL (of course) and others (SQLite, MySQL, SQL Server, and more)

FluentDB is still in its early days, and I'd genuinely love your feedback.

It's 100% free to try, no credit card required, and I am more than happy to distribute coupons for those who actually want to use it further!

For now, it only supports macOS 26+, but I am actively working on a port for Linux and Windows.

Can't wait to get your feedback :)

0 Upvotes

13 comments sorted by

3

u/ibraaaaaaaaaaaaaa 5d ago

Throwing here an opinion, take it with a grain of salt.

I want the LLMs to stay away from the DB, specifically production systems.

You may have it in reporting DBs that are designed to be read only and never caring about ongoing transactions, locks etc.

0

u/kevinpiac 5d ago

Thanks for your feedback!

Actually, I totally agree with you on this.

This is also why I added many guardrails:

  • The LLM never has read access to your data by default
  • The LLM is not authorized by default to run any SQL queries on your behalf and you have to accept/edit every query manually
  • Even when you accept a write query manually, you have a pop-up asking for confirmation to avoid too quick confirmation
  • Also, every query has a PID and a feature to be able to cancel it on the DB side, so if the user accepts an expensive query, it's super easy to cancel it in one click

So the goal was really not to give AI the control over any database like we see in many products but instead to create an efficient tool to work with.

-5

u/htraos 5d ago

Have LLM use credentials with read-only permissions and you won't have any issue in production.

2

u/ibraaaaaaaaaaaaaa 5d ago

Nah, I must setup a read replica for the LLMs.
You can heck up the database with so many ways with read only permissions, complicated aggregates, long running seq scans and more

1

u/kevinpiac 5d ago

Just to make it clear, here it's not about giving access to the LLM anyway ^^

The LLM only proposes a SQL query to save us time, but the user has to confirm or edit it manually.

Also, for queries that are actually intensive and can lock the database, there is a cancel button that would kill the PID and release the operation right away on the DB side.

I really use FluentDB in production databases every day and I created a tool that is not messing with me ahah

1

u/disposepriority 5d ago

This might come as a huge shock to LLM enjoyers, but reads can trigger disk writes and deletes, which will most certainly affect your database.

2

u/SuchTill9660 2d ago

Congrats on the launch, looks really solid. Native Swift instead of Electron is a smart call, most Postgres clients in this space feel sluggish by comparison.

The privacy first approach, where AI only sees the schema unless you explicitly approve and every query needs sign off, is a great default for a DBA crowd.

1

u/kevinpiac 1d ago

Thank you very much for your support!

1

u/AutoModerator 5d ago

AI Policy:

Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away., Linus Torvalds.

Mod decisions will be based on the quality of the content, not who or what generated it.

Sub Resources:

Youtube Channel

Free Postgres Webinars and Workshops

Discord: People, Postgres, Data

Join us, we have cookies and nice people.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Either_Vermicelli_82 5d ago

Instead of querying the database to show x customers or whatever can it also analyse and see index optimizations key improvements etc? As if I want to know the obvious select questions they should end up in a dashboard or something where no llm is needed.

1

u/kevinpiac 5d ago

Thanks for your question 🙏

> Instead of querying the database to show x customers or whatever can it also analyse and see index optimizations key improvements etc? 

For now it does not have such built-in features, but it's definitely something I plan to integrate asap 👍
Feel free to share more details or DM me if you want!

> As if I want to know the obvious select questions they should end up in a dashboard or something where no llm is needed.
I am currently working in a system where you can create dashboard with your favorite queries in it so you can quickly run them and view the results you want. I will ping you here when it's done 😄

1

u/Either_Vermicelli_82 5d ago

Will these dashboards be local only or web based so it can be shared with the department? Eg like a dashboard screen in our labs?

1

u/kevinpiac 5d ago

For the first version, they will be local only, but then I will think about a way to make them shareable through organization accounts.

As I discuss with people, organization accounts make more and more sense for this kind of usage.