The short version.

Claris still ships a FileMaker release every year; FileMaker 2026 came out in June 2026. Customers still renew. Real businesses still run on it every day. What's changed is everything around it: 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 brand-new systems being started on it, and more attention on how to modernize what already exists.

Why "cooked" is the better word.

Cooked means terminal, with a few good years left. The software works, the releases keep coming, and existing systems keep running. But the pool of people who can work on it shrinks every year, and fewer new systems get built on it. The end is far enough off to plan for, and near enough that you should.

Not dead. Cooked. Use the good years to make a plan.

What Claris said in 2026.

Claris released FileMaker 2026 in June 2026 and laid out where it's heading: AI tools aimed at the developers who build and maintain FileMaker systems, plus two optional server add-ons sold separately. It's also discontinuing Claris Studio on March 15, 2027, to concentrate on FileMaker itself. That's a vendor pulling back to its core and serving the customers it already has. Nothing in it changes what to do with a system that works: get it documented, keep it backed up, and keep a plan you control.

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 on a copy before you put it on the live system. A plugin vendor might discontinue their product, so know which plug-ins you rely on. 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 software one company owns, 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 brand-new system than for keeping one you have. What made FileMaker quick to build in, everything in one program from one vendor with screens you draw by hand, still holds, and for the right project it still works. What has changed is everything around it and how easy it is to hire help later. If one developer can carry the project start to finish for its whole life, FileMaker still works. If it needs to grow or outlast one builder, ordinary web tools have caught up, and FileMaker's old advantages count for less than they did.

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 today 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 telling you the story their business needs to be true. Neither is dishonest, exactly — they're just answering from where they stand. The straight 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 brand-new systems is smaller than it was. The market for maintaining and modernizing existing systems is intact and, in some ways, growing — because the business rules living inside 15-year-old FileMaker files are genuinely valuable and doesn't get replaced cheaply. If you own one of those systems, the right move is neither panic nor sitting still. It's a five-year plan you actually check on.

What to do next.

If you own a working FileMaker system, get it documented well enough that any competent developer can pick it up, 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 sales pitch. You'll come away knowing whether to hold, extend, or plan an exit.