FileMaker Development at Machine Speed
Built by the team that ran Onroute.io on FileMaker for a decade — 1,235 scripts, 154 tables. Debug cross-script issues in seconds. Generate pasteable script steps from plain English. Document an entire solution in an afternoon.
DDR Intelligence
Your entire solution structure — parsed and indexed. Our AI reads DDR XML exports like a senior developer, mapping every table, script, relationship, privilege set, and custom function into a queryable knowledge base.
Cross-Script Debugging
Trace execution paths across sub-scripts, PSOS calls, and triggered scripts in seconds. The toolkit identifies race conditions, privilege escalations, and logic gaps that manual review would miss entirely.
Script Generation
Describe what you need in plain English, get paste-ready fmxmlsnippet output. The AI generates script steps that respect your existing patterns — field names, variable conventions, error handling style — not generic boilerplate.
Live Database Connection
Connect directly to your FileMaker database via the Data API. Query records, test script logic against real data, and validate fixes before deploying — all within the AI-assisted workflow.
Solution Documentation
Generate comprehensive documentation for your entire solution in hours, not weeks. Every script annotated, every relationship mapped, every privilege set audited — in a format your team can actually use.
FAQ
Common questions about AI-powered FileMaker development
What FileMaker versions does the AI toolkit support?
The toolkit works with DDR exports from FileMaker Pro 12 and later. If your solution can produce an XML DDR export, we can parse and analyse it — regardless of which FileMaker version you're running in production.
What is an fmxmlsnippet?
An fmxmlsnippet is a portable XML format that represents FileMaker script steps, custom functions, or layout objects. You can paste snippets directly into FileMaker Pro's Script Workspace — the AI generates these so output is immediately usable without manual translation.
Do you need access to our database for AI-powered development?
No. The core toolkit works entirely from DDR exports — static XML files that contain no record data. Live database connection via the Data API is optional and only used when you want to test queries or validate logic against real data.
How does cross-script debugging actually work?
We parse the entire script catalogue from the DDR, then build a dependency graph: which scripts call which, which fields trigger which calculations, which layouts attach which triggers. When a bug surfaces in script A, the toolkit walks the call graph backwards from the failure point and surfaces every script that could have set up the failure — usually identifying the root-cause script in under a minute, regardless of how deeply it's buried.
Will AI-generated scripts match our existing code style?
Yes — the toolkit reads your existing scripts before generating new ones, so output matches your field-naming conventions, variable patterns ($, $$, ~), error-handling style, and comment density. We've found this is the difference between AI output you can paste into production and AI output you spend an hour reformatting.
See it work on your solution
Send us a DDR export and we'll show you what the AI finds in the first 30 minutes.