Is FileMaker dead? An honest answer from a developer building in it since 1990.

The short version.

Claris still ships FileMaker releases. Customers still renew. Real businesses still run on it every day. What's changed is the surrounding infrastructure: the developer pool is smaller than it was five years ago, job postings for FileMaker roles have thinned out, and the platform's growth story has become quieter. That combination doesn't kill the software — but it changes what owning it costs and how easily you can find help.

What "dead" would actually look like.

Dead means Claris announces end-of-life, security patches stop, hosting providers pull support, and existing systems stop working reliably within a defined window. None of that is happening. What is happening is a slow contraction on the edges — fewer new developers entering the field, fewer greenfield projects being started on the platform, and more attention on how to modernize what already exists.

FileMaker is not dead. It's aging in a specific direction.

If you own a FileMaker system.

Your system is probably fine. What you need is a plan. The specific risks are known and manageable: your developer might retire, so find a steward before they do. An OS or FileMaker Server upgrade might break something, so test before you deploy in production. A plugin vendor might discontinue their product, so know your dependencies. A renewal quote might climb faster than you like, so know your negotiation options. None of these are new problems. They're the normal cost of running proprietary software over decades, and they're solvable one at a time with the right person on the phone.

Your system is probably fine. What you need is a plan.

If you're deciding whether to start something new on FileMaker.

The math is different for a greenfield project than for maintaining an existing one. The advantages that made FileMaker attractive for building fast — the integrated environment, the single vendor, the visual layout tools — still exist, and for the right project shape they still work. What has changed is the surrounding ecosystem and the hiring pool for future help. If the project is small enough that one developer can carry it end-to-end for its whole lifespan, FileMaker still works. If the project needs to scale or outlast a single builder, the modern web stack has caught up in ways that make FileMaker's traditional advantages less unique than they were.

If you're building a career.

This is where the honest answer gets uncomfortable. Job listings for FileMaker developers have thinned out. New entrants to the field are rare. The remaining work concentrates around maintenance and modernization of existing systems, not greenfield builds. A career built purely on FileMaker in 2026 is possible but narrower than it was ten years ago. Most working FileMaker developers I know now build outside the platform as well — Python, SQL, JavaScript, cloud infrastructure — because the market rewards that flexibility and because it's how modernization work actually gets done.

Why most published answers are biased in predictable directions.

When you search this question, the answers cluster into two camps. Established FileMaker consultancies say the platform is thriving because their revenue depends on it. Replacement software vendors say it's dying because theirs depends on that story. Both are giving you data-shaped versions of their own business model. Neither is dishonest, exactly — they're just answering from where they stand. The unconflicted version has to come from somewhere in the middle: from someone who works both in and out of the platform, and who makes money regardless of what you decide.

What an honest read looks like.

FileMaker is alive and shipping. The developer pool is smaller. The market for greenfield systems is smaller than it was. The market for maintaining and modernizing existing systems is intact and, in some ways, growing — because the business logic living inside 15-year-old FileMaker files is genuinely valuable and doesn't get replaced cheaply. If you own one of those systems, the right posture isn't panic and it isn't complacency. It's a five-year plan you actually check on.

What to do next.

If you own a working FileMaker system, get a developer who will still be there in five years, get the system documented, and know what your realistic options are — extend, hold, or migrate — before you're forced to choose during an emergency. That's what the free triage call is for. Thirty minutes. No pitch. You'll leave knowing where you actually stand.