Crafty Framework

Consistency Across the Entire System

In traditional FileMaker systems, each button or script can behave differently depending on who wrote it and when. Crafty introduces a unified action pipeline, ensuring all user actions follow the same flow: validation, logging, security checks, and execution. This eliminates "mystery scripts", inconsistent behaviours, and unexpected side effects. The result is a system that is easier to maintain, easier to extend, and far less fragile.

Real Visibility Into What's Happening

Crafty's system-wide audit logging captures more than just data changes — it records finds, exports, layout navigation, script calls, permission denials, approvals, and more. This transforms FileMaker from a black box into an observable platform. When something breaks, slows down, or behaves oddly, the audit log provides immediate answers, reducing downtime and removing guesswork. Teams gain operational clarity and confidence.

Built-In Safeguards That Prevent Silent Failures

FileMaker's native privilege sets silently stop actions when a user lacks access. Crafty intercepts these events, explains the reason, logs the attempt, and can optionally trigger alerts or approval pathways. This prevents user confusion, eliminates invisible permission issues, and provides accountability. Every "no" becomes a meaningful, traceable event rather than a frustrating dead-end.

A Scalable Script & Action Architecture

Crafty introduces a clean scripting architecture using routers, handlers, and builders. This separates intent (what the user wants) from execution (how the system does it). As solutions grow, this pattern prevents script sprawl, reduces duplication, and makes large systems maintainable. New developers onboard faster, changes are safer to make, and bugs are easier to trace.

Approvals and Control Where They Matter Most

Many businesses require approval flows for financial changes, sensitive updates, or workflow checkpoints. Crafty includes a flexible approval layer that can enforce approvals based on table, layout, role, or action type. Instead of bolted-on or duplicated scripts, approvals are part of the core architecture. This adds operational control without slowing down normal work or complicating the user experience.

Future-Proofing for Integrations, APIs, Ai and Growth

Modern FileMaker systems increasingly interact with APIs, webhooks, micro services, Ai agents, external databases, and automated server-side workflows. Crafty is designed for this reality: every action flows through a central layer that can integrate external calls, enforce rules, and log outcomes. Whether adding new features, new users, or new integrations, the framework absorbs complexity so the solution doesn't collapse under its own weight.