Now in private beta

Fathom any FileMaker solution.

Understand your whole solution, build correctly within it, and ship it to the web safely. All by asking in plain English.

Your client's solution is their IP. In alpha: a macOS app, with data (and even the AI) fully on your machine.

You inherit a solution you didn't build. Thousands of fields, hundreds of scripts, and no map.

FM Fathom ingests the full XML export of a FileMaker solution (every table, field, script, layout, and account) and turns it into something you can explore, question, and trust.

01

Understand

A navigable catalog of everything in your solution: multi-file systems modeled as one. Trace any dependency to its root, and see how it really behaves in production with real server-log evidence.

02

Build

Compose scripts, calculations, and fields as paste-ready snippets, grounded in your actual schema, not templates. Because it understands your whole solution, it helps you build correctly within it.

03

Ship safely

Know what's safe to expose before you expose it. Data API and OData readiness with the full access chain reconciled, security and script audits, and unused-element cleanup.

All three, by asking in plain English.
ASK

Talk to your solution. Don't just browse it.

Your AI assistant connects through 24 read-only MCP tools. Ask real questions and get answers grounded in your actual solution, never a guess.

Or skip the setup: a built-in assistant ships in the app. Bring your own key (Anthropic, OpenAI, or OpenRouter).

Upload your server logs and the same questions gain production evidence: what actually runs, how often, and what it costs.

Reads your solution. Never writes it.

claude · connected to FM Fathom
What is impacted if I rename the field Invoices::client_id?
It's referenced in 14 places, including two ExecuteSQL calls that address it by name. A rename would leave those pointing at nothing:
Invoice Totals (recalc) line 24 ExecuteSQL Monthly Rollup line 11 ExecuteSQL + 12 direct references (safe to rename)
Which of my scripts update client invoices?
Three scripts write to the Invoices table:
Post Monthly Charges creates each month's invoice records Apply Late Fees adds fees to overdue invoices Recalc Invoice Totals recomputes totals after line edits
What was slow in production last week?
From your server logs: the nightly reporting rebuild averaged 42 minutes, three times its usual, and one unstored find on Work Orders drove most of Tuesday's slowdown.
Is this table safe to expose over OData? Where is this layout object used?
SEE IT IN ACTION

Findings become a kanban board.

Every audit finding (a field, a script, a layout) is a card your team can assign, discuss, and move to done.

TO DO
Field: Email missing validation
Customers
Script: unused for 6 months
Legacy Import
IN PROGRESS
Script: CalcTax (review)
Invoices
Layout: Orders (audit)
Orders
DONE
Table: Customers (cleaned)
Customers
Account: no password set
Security
SEE IT IN ACTION

Relationships, from any table out.

Pick any table occurrence and explore what it connects to, one hop or three. A tangled multi-file solution finally reads as a map instead of a maze.

Hops 12 6 TOs · 5 edges
Customers FOCAL Orders Invoices Payments Line Items Products Late Fees
SEE IT IN ACTION · REAL DATA

Call chains, traced end to end.

A real script from a real solution: "Hamburger Navigation," from a live FileMaker file we work in every day. Every button that fires it, every script it calls, all traced automatically.

BUTTON Hamburger BUTTON Q Detail - Rental Applications BUTTON Q Detail - Rental Apps TEST NEW BUTTON Q Detail - Web BUTTON Settings iPhone Hamburger Navigation 43 STEPS Close Window [SAFE] Go To Correct Dashboard Log Out

Things no other FileMaker tool does.

Production truth, not just structure

FM Fathom reads your FileMaker Server logs: incidents, expensive calls, schedule health with a zoomable timeline. Every other tool stops at the schema. We can tell you what actually happened in production last Tuesday.

Web-readiness, answered

Before you expose a table over the Data API or OData, FM Fathom reconciles the full privilege chain and tells you exactly what a given account can see and do. No other tool addresses building on FileMaker over the web at all.

Findings become work, not PDFs

Assign an audit finding to a teammate, discuss it in place, and move it across a review board to done. The incumbents are solo-desk tools; FM Fathom is built for the whole team: hosted, zero install.

See the layout, not just a list

Every layout renders as a visual map of its objects. When you're hunting one object, FM Fathom shows you where it sits on the layout, instead of leaving you to scan a tree of names.

UNDERSTANDING, BY DEPTH

The deeper you go, the more it understands.

Every question has a depth. Start with a census, end at the full chain of consequences; the tools go all the way down.

0 fathoms

The census

How many tables, fields, scripts, and layouts? What's biggest, what's busiest, what looks off? The lay of the land in one glance.

10 fathoms

Where is this used?

Pick one field and see everything that touches it: scripts, layouts, calculations, relationships, down to the exact step that references it.

20 fathoms

What does this button actually do?

Start from one layout object and follow it all the way down: the script it fires, the scripts that script calls, and everything they impact. The whole chain, charted.

BUILDING IN THE OPEN

We ship regularly.

See the full roadmap
in alphamacOS app: the whole engine on your desktop, data never leaves
usable nowVersion comparison: side-by-side diffs of any two versions of a solution
coming soonSlack connection: mentions land where your team already talks
Fathom it.
The full experience is coming together.