Early access: Ailimu is free while we build to 1.0. We'd love your feedback. Find out more
Ailimu

Give your team AI access to FileMaker, safely

Letting people ask an AI assistant about your FileMaker data is useful the day you switch it on. The questions worth asking first are about control: what can the assistant see, what can it change, and how would you know. Here is how Ailimu answers each of them.

Start read-only

Every connection starts read-only. While it is on, the assistant is given no tool that changes records and no tool that runs scripts, whatever else is selected. Turn it off only for a connection where you have decided writing is worth it.

Choose every field

For each table you expose, you decide field by field:

Container fields are never sent. Fields you do not expose cannot be asked for, because they are not in any tool.

Let FileMaker's own security decide

Ailimu signs in as a FileMaker account you create for it. Give that account a privilege set that can only reach what you are willing to expose. Whatever Ailimu's settings say, anything the account cannot see stays out of reach. This is the control your FileMaker developers already know how to review.

Keep the password on your server

The FileMaker account's password is read from the server's environment. It is never written to Ailimu's settings, never sent to a browser, and never sent to the AI model. Claude reaches Ailimu with a separate token per connection, which you can replace without touching FileMaker.

Know what leaves your network

Ailimu runs inside your network and copies nothing. When the assistant answers a question it does read data: the rows a tool returns, limited to the fields you chose, are sent to the model at that moment. That is true of any assistant that answers questions from data. Everything else stays on your server. If your data may not reach a third-party model at all, decide that before installing anything. The full breakdown is in the manual.

Name the people who configure it

The people who set Ailimu up sign in with their own accounts: owners manage people, editors set up and publish connections, viewers can look but not change anything. Remove someone and they are signed out everywhere at once.

See everything that happened

Activity in the wizard records every change the assistant made and every script it ran, on every connection, and every change people made to the setup. Search it by date, keyword, connection and person, and export it as CSV. You can also record the assistant's searches on a connection, which uses more disk space, so it is off until you turn it on.

A sensible rollout

  1. Create a restricted FileMaker account for Ailimu.
  2. Expose a few tables people actually ask about, read-only.
  3. Let a small group use it, and watch Activity.
  4. Widen the tables, or allow writes on one connection, only once you are comfortable with what you see.

Next