Ask your FileMaker data anything.
Your team asks Claude about orders, customers and stock in plain English, and gets answers from your live FileMaker data. It runs on your own server, starts read-only, and you choose every field it can see.
Measured on our own production FileMaker files.
An invented business. Every name and figure is made up.
One connection.
Three wins.
The people who use the data, the people who look after it, and the partners who build it for clients each get something different.
Answers in seconds, without waiting for a report or a new layout.
- Ask in plain English. No layouts, finds or exports.
- Answers come from live data, not last week's spreadsheet.
- Works in Claude, the assistant your team may already use.
- Sensitive fields stay private, because you choose what Claude sees.
What your team can ask
- SalesWhich trade customers haven't ordered since June?
- FinanceWho has overdue invoices, and how much do they owe?
- OperationsWhich products will run out before the next delivery?
- ManagementHow did March sales compare with February?
Give your users AI without writing a single tool definition.
- Reads your real schema: types, keys, relationships, comments, row counts.
- Collapses duplicate table occurrences and hides scaffolding fields.
- Tables from the data file, scripts from the interface file, one endpoint.
- Read the schema again after a change and every choice you made is kept.
- A clean ERD that shows how your tables are connected, one table at a time.
Off your plate
- Tool definitionsGenerated from your schema, never written by hand
- Table occurrencesResolved for you: 231 became 75 real tables
- Security modelYour privilege sets stay in charge: FileMaker's own security still decides access
- Data copiesLive reads, with no copy kept by Ailimu
- Navigating tablesA clickable ERD: hop between linked tables
Bring AI to every client solution you build and support.
- One install per server, several files, each with its own address and token.
- A setup wizard you can walk a client through in one meeting.
- Read-only defaults and an activity log that clients' IT can sign off.
- Works with self-hosted FileMaker Server and hosting providers.
What clients are asking you
- Using AI"Can we use AI with our FileMaker system?"
- Data safety"Is our data safe if we do?"
- Staff access"Can staff ask questions without new layouts?"
- Audit"Who can see what, and is it logged?"
What it is, what it does, why it matters.
Every feature serves one of three promises: answers you can trust, control you can prove, and a setup measured in minutes. Open any line for how it works.
Answers you can trust
Claude works from your real structure, not a guess.
Schema readerNobody writes tool definitions. Live in minutes, not after a project.
Reads types, keys, relationships, comments and row counts, and turns the tables you choose into clear tools.
Table occurrence resolverClaude stops guessing which table is real.
Collapses copies of the same table into one set of tools and flags scaffolding and never-filled fields.
Live readsAnswers are current, and Ailimu keeps no copy.
Every question reads FileMaker at that moment. Ailimu syncs, mirrors or indexes none of it.
Scripts as toolsReuse business logic you already trust.
Lets Claude run scripts you have reviewed, with a sentence telling it when to use each one.
Control you can prove
Every safeguard is on before anyone asks a question.
Read-only by defaultSafe to roll out on day one.
No update or script tool exists until you switch read-only off and mark fields writable.
Field-by-field exposureShare what people need, keep salaries and notes private.
You choose which fields Claude can return or search. The rest are in no tool at all.
Your privilege setsNo new security model to audit.
Ailimu signs in as a restricted account you create, so FileMaker enforces its own rules.
Activity log and personal keysA clear audit trail, and access you can remove one person at a time.
Logs every write and script call; each person can have their own key.
Minutes, not a project
One container, one wizard, one click for your users.
Setup wizardSee exactly what Claude will get first.
Suggests a starting set and lets you try each tool against live data before you publish.
One-click Claude Desktop extensionUsers connect themselves. No IT ticket.
Builds an extension per connection with its address and token filled in. One command for Claude Code.
One container, many filesOne thing to run, however many solutions you connect.
Serves several FileMaker files from one install, each with its own address and token.
FileMaker and PostgreSQLOne tool and one set of rules across both systems.
The same wizard, read-only default and field-by-field control work on PostgreSQL databases too.
From file to first answer in four steps.
All in your browser. You see exactly what Claude will get before anyone uses it.
Point it at your server. Ailimu reads the rest.
Choose FileMaker or PostgreSQL, enter the host and file, and read the schema. Tables can come from one file and scripts from another.
See how your tables connect, one table at a time.
FileMaker has no screen that draws your relationships for the whole file. Ailimu's ERD shows one table with its neighbours, so a large file stays readable.
- Click to hop. Tables that point at it sit on the left, tables it points at on the right. Click one to move there.
- Find anything. Search for a table or a field, and jump from any field to its place in the diagram.
- Honest about guesses. Solid lines are declared by the database, dashed lines are guessed from field names.
- Take it with you. Download the diagram as SVG.
FileMaker first. PostgreSQL too.
Running PostgreSQL beside FileMaker, or moving a solution onto it? Connect it the same way: the same wizard, the same read-only default and the same field-by-field control.
Every connection carries a badge saying which database it is, so a list holding both stays clear for your team.
orders · 18,430 rows · comment: "Confirmed and shipped customer orders"
Exact, not guessed
Tables, column types, primary and foreign keys, comments and row counts come straight from PostgreSQL's own catalog. The relationship diagram draws the keys the database declares.
The database has the last word
Every value is sent as a bound value, never written into a query. An account that may not update a column cannot change it, whatever the wizard says.
Functions, like scripts
Stored functions are offered the way FileMaker scripts are: exposed one by one, and off while read-only is on.
One gateway between your data and the AI.
Ailimu reads your database live and hands Claude only the rows a tool returns, limited to the fields you expose. Run it wherever your database lives: your own network, a cloud VM or a VPS.
Everything you control sits in one zone: your admin, your database and Ailimu. The AI agent sits outside it, and only two things cross the line: tool calls in, and the rows a tool returns out.
If your data may never reach a third-party model, no connector of this kind is right for you. Read the full answer in the guide.
Your clients are asking about AI. Give them a safe answer.
Built by a team running large FileMaker deployments, Ailimu is made to be installed, explained and supported by the people who build FileMaker solutions.
Deploy across clients
Several files on one server, each with its own address and token. Read the schema again after your changes and every setting is kept.
Easy to sign off
Read-only by default, privilege sets still apply, nothing copied out, every write logged. The questions clients' IT will ask already have answers.
Built on your work
Field comments become tool descriptions and your scripts become tools. The better your solution, the better Claude answers.
Built by people who run FileMaker at scale.
We run large FileMaker deployments with hundreds of tables and scripts. When our own users asked for AI, nothing read a real FileMaker file well, so we built Ailimu and ran it on our production files first.
Every answer reads your database live and Ailimu stores none of it. Rows a tool returns are sent to Claude.
Read, search and write. Write stays off until you turn read-only off.
FileMaker and PostgreSQL, through the same wizard and safety model.
Serve many files from one install, each with its own address and token.
What people ask first.
What does Ailimu do?
It connects Claude to your FileMaker data. It reads your schema, turns the tables, fields and scripts you choose into tools, and Claude calls those tools to answer questions from live data.
What is MCP?
The Model Context Protocol is the open standard AI assistants use to call outside tools and data. Claude supports it, as do a growing number of other AI clients, so one Ailimu connection can serve any of them.
Does my data leave my network?
Only the rows a tool returns, when Claude asks, limited to the fields you marked readable. Passwords, unexposed fields and the database itself stay on your server. Nothing is synced or copied.
Can Claude change my data?
Not unless you allow it. Read-only is on by default. Writes need read-only off and a field marked writable, and every write is logged.
Which FileMaker setups are supported?
FileMaker Server with OData for tables and the Data API for scripts, self-hosted or with a hosting provider. Claris FileMaker Cloud is not supported yet. PostgreSQL is supported too.
Which AI tools work with it?
Claude Desktop with a one-click extension, Claude Code, and any client that connects to a remote MCP server over HTTP.
Is it free?
Yes. Ailimu is free while we build towards version 1.0.
I am a Claris partner. Can I install it for clients?
Yes. One container can serve several files, each with its own address and token. Register your interest in the partner section and we will be in touch at 1.0.
Learn how it works.
Ten minutes to your first answer.
Run one container, tick the data Claude may see, and ask your first question.