FileMaker is not a bad product. It is a capable, well-established database management system with decades of real-world use. But for growing businesses evaluating their options in 2026, the review is this: FileMaker asks a lot in return for what it gives you. A mandatory annual subscription that shuts your software off the moment you stop paying, a proprietary data format that makes leaving difficult, a per-user cost structure that compounds as your team grows, and an AI layer that was added on top rather than built in from the start.
Getting the full picture of the issue
FileMaker is still actively developed. Claris shipped FileMaker 2025 in November of that year, and the product is moving toward AI features and renewed licensing rather than lower cost. The platform has a real user base and genuine capabilities.
But staying on it is not a neutral decision. Skin in the game means understanding exactly what you are signing up for before you commit. Under Claris license terms, the software ceases to function if the subscription lapses. Stop the renewal, and the custom applications your business depends on go dark. A perpetual license that stops updating is a security problem you can schedule. A subscription that switches your application off is a business continuity problem with no grace period.
That is a meaningful distinction. And it is worth understanding before you go the whole nine yards on a FileMaker investment.
The costs start to add up
FileMaker Cloud is priced from $21 per user per month at the entry tier, rising to $43 per user per month for larger teams, with hosting costs on top of that. For a team of 20 people, that is a significant recurring line item before anyone has built a single workflow.
And the lock-in goes beyond price. FileMaker stores data in its own proprietary format rather than a standard SQL database. Moving data out means an export and a remap, not a copy. Client and server versions are coupled, meaning upgrading the host can force every workstation to upgrade with it. The longer your team builds inside FileMaker, the larger the eventual rebuild if you ever decide to leave. By the time the bill starts feeling wrong, you are already in too deep to make a quick exit.
FileMaker still requires a specialist
FileMaker was built as a database management system for developers. Building and modifying solutions requires learning FileMaker's scripting language and layout model. Non-technical team members can use what has been built for them, but they cannot build or adapt it themselves without considerable training or outside help.
That creates a dependency that is hard to shake. Every process change, every new field, every adjusted workflow needs to go through someone who knows the platform. For small teams without a dedicated FileMaker developer, that means tickets, waiting, and work that does not move until someone with the right skills picks it up. If your developer leaves, you are left holding the bag.
Want a deeper breakdown? See the full feature comparison
Is Ninox the better option?
With Ninox, your team builds exactly what they need without opening a ticket to IT, anyone can build their system because it’s a low-code platform and you don’t have to write a single line of code (but you can if you want to).
Data lives in relational tables with enforced field types, real-time collaboration, and a single live version everyone works from. Automations trigger on data changes without a line of code. Document generation pulls directly from live records. And because Ninox is AI-native from day one, the AI is not a feature bolted onto an existing architecture. It is woven through the entire building and end-user experience.
It is GDPR-compliant and ISO 27001 certified. And unlike FileMaker, if you ever decide to move on, your data moves with you cleanly.
The road ahead
FileMaker built something real over three decades. The platform works, and for teams already deep in it with a developer on hand, that investment is not nothing.
But for a business evaluating its options today, the picture is clear. A subscription that turns your software off when payment stops, a proprietary format that makes leaving expensive, per-user pricing that scales upward as you grow, and a build-and-modify experience that keeps non-technical team members on the sidelines. Those are not edge cases but the everyday reality of running on FileMaker.
The best way to know if Ninox works for you is to use it. Start building with the free tier (no trial period). Build out a small process in minutes and only move your system if it earns your trust.
You don’t need to put a credit card down or commit to anything. No sales call unless you want one.
