Flolet

Web-based database console

Visit Website
August 2, 2022 Why Flolet?

I have another SaaS project — Brick.

I have hired somebody to help us with customer support. Let's call him Ivan, because his name is Ivan.

Ivan needs access to the production database — to delete users, to upgrade users' subscriptions, to merge accounts, to etc.

So far the workflow has been:

  • I write a long SQL query to delete a user.
  • I send this query to Ivan.
  • Ivan enters it in DBeaver.
  • Actually wait, DBeaver has broken for whatever reason.
  • Ok, now it works though I don't know why.
  • Five days later Ivan is asked to delete another user but the query doesn't work anymore because we added a foreign key constraint in the schema.

I don't like this.

  1. I want a dumb, easy tool that doesn't break.
  2. I don't want anyone to have to install anything.
  3. I want a single collaborative notebook storing all the DB queries and their history. I want to be able to tell Ivan "yeah look at this query from yesterday that I ran".

Flolet is this tool. It works in the browser. It keeps track of all queries, who ran them, when, what results did they get. It lets me say "the task was to DELETE USER X, here are the queries I ran for it", and refer to it months later.

2 Comments

  1. 2

    I see that you are just supporting postgres right now, you can use this tool to support multiple databases at once https://github.com/xo/usql . It's syntax is similar to psql and my guess is you are using psql underneath if this is the case than you can replace it with usql and get support for multiple databases.

    1. 1

      Oh, nice. I use a native driver (node-postgres) underneath, but I might use usql to support all other DBs and replace it with native drivers piece by piece.

About

The good thing about reinventing the wheel is that you can get a round one.