Claris has warned the FileMaker community about active attacks targeting exposed servers. Just days before Milan FileMaker Week, it’s a reminder of why surviving the future requires more than learning the next big technology.
We’re about to spend an entire week in Milan discussing the future of FileMaker. Artificial intelligence, agentic development, modern architectures, integrations, new interfaces and the changing role of developers. We’ve invited speakers from across the international community to challenge assumptions, question established practices and explore what comes next for the applications businesses depend on.
And then, just days before the conference, Claris reminds us of something considerably less futuristic: someone may already be trying to break into your FileMaker Server.
Not with some extraordinary new AI technology. Not necessarily by exploiting a previously unknown vulnerability in FileMaker. But by doing something painfully familiar: trying passwords against systems exposed to the internet.
It’s almost too perfect an introduction to our conference theme.
Surviving the Future.
Because before we discuss how FileMaker applications will evolve over the next ten years, perhaps we should ask whether the systems we’re running today are ready to survive the next ten days.
What’s happening to FileMaker Server?
Recent security communications from Claris have warned the community about active password-spraying attacks targeting publicly accessible FileMaker Server installations. Attackers are attempting common or weak passwords against exposed authentication endpoints, potentially including the Admin Console, Data API, OData, WebDirect and XML interfaces.
This is an important distinction: the reported password-spraying activity does not, by itself, establish that FileMaker Server has a newly discovered security vulnerability. It highlights the risks associated with internet-facing services, insufficient access restrictions and weak authentication practices. The communications also address critical vulnerabilities affecting certain PHP deployments, which represent a separate issue and need to be assessed according to the technologies actually in use.
Claris has announced a dedicated Community Live security session on October 29, with Todd Geist and Wim Decorte, to discuss the situation and recommended protective measures. If you manage a FileMaker environment, it’s worth attending.
But there’s a bigger question behind this warning, and it’s one that goes well beyond the current attacks.
Who is actually responsible for the long-term survival of the FileMaker systems businesses rely on?
Your FileMaker application works. Is that enough?
Many FileMaker solutions started as relatively simple applications. Over time, they became the operational backbone of entire companies. More users, more data, more integrations, more remote access, more business processes. What began as a departmental tool may now be responsible for orders, production, inventory, customer relationships or financial operations.
The application still works. The business depends on it. And everyone assumes that somebody, somewhere, is taking care of the infrastructure.
But when was the last time anyone reviewed the complete architecture? Which services are exposed? Which accounts still have access? Which integrations depend on credentials created years ago? What happens if the server becomes unavailable? Can the company actually restore its data and resume operations?
These questions are not particularly exciting. They don’t make spectacular conference demos, and they certainly don’t generate the same enthusiasm as watching an AI agent build an application.
Yet they determine whether the software we’ve built remains an asset or gradually becomes a liability.
The immediate recommendations are familiar, but worth repeating.
A quick FileMaker Server survival checklist
- Review public exposure. Identify which FileMaker Server services are accessible from the internet, restrict access where possible and disable unnecessary endpoints.
- Audit accounts and credentials. Remove unused accounts, eliminate unnecessary guest access and replace weak or reused passwords.
- Protect administrative access. Restrict access to the Admin Console and evaluate appropriate network controls, VPNs, firewalls and rate limiting.
- Review integrations and privileges. Verify which users and applications genuinely require Data API, OData, WebDirect or other external access.
- Verify backups and recovery. Maintain protected backups outside the affected environment and test whether your recovery procedures actually work.
- Review the official security guidance. Check Claris communications and the October 29 Community Live session for recommendations relevant to your deployment.
None of this is revolutionary. That’s precisely the point. The future of business software isn’t secured by adopting new technologies while ignoring the foundations on which everything else depends.
This is why we’re bringing the FileMaker community to Milan
When we started building the program for Milan FileMaker Week 2026, we made a deliberate choice: we didn’t want another conference organized around a collection of disconnected technical demonstrations.
We wanted to tell a story about the future of FileMaker and, more importantly, about the people and businesses that depend on it.
That’s why FMExchange, November 5–6, follows a single track. One conversation, developed over two days, in which every session contributes to a larger question: what does it really take to survive the future?
And the recent security warning makes that question even more relevant.
We begin on Thursday, November 5, with “FileMaker is in your business. So now what?” It’s the starting point for everything that follows. FileMaker is already there, often deeply embedded in critical operations. The question is no longer simply what we can build with it, but what responsibilities come with maintaining and evolving those systems.
From there, Nicola Mattina challenges the economics of software development with “What Will We Sell Now That AI Writes the Code?”, while Douglas Wallis from Claris takes us inside the emerging world of agentic development. Romain Dunand examines what implementing AI in FileMaker actually costs, moving the discussion from technological excitement to architecture, privacy and business value.
Then comes a session whose title suddenly feels particularly appropriate.
YOUR FILEMAKER APP WILL DIE. PLAN ACCORDINGLY.
On November 5, John Renfrew will challenge us to reconsider how we design applications that are expected to last. His session explores architectural decisions, APIs, webhooks, OData and the separation of data from interfaces and business logic.
It’s not a session about the current security alert. It’s about something more fundamental: recognizing that applications evolve, technologies change and dependencies become risks when we fail to plan for them.
Albert Harum-Alvarez will continue that uncomfortable conversation with “The ONLY Good Reason NOT to Rebuild Your App from Scratch.” Because rebuilding everything isn’t automatically the right answer either. Sometimes the most valuable technical decision is understanding what deserves to survive, what needs to change and what should finally be retired.
These are conversations that matter to experienced developers, but they matter just as much to the companies relying on the applications those developers maintain.
The workload is coming. Is your infrastructure ready?
Friday, November 6, brings the discussion even closer to the operational realities behind business-critical FileMaker systems.
We start with a Surviving the Future roundtable, bringing together Douglas Wallis, John Renfrew and Giulio Villani, moderated by Nicola Mattina. Different perspectives, one central challenge: how do we make the right decisions today for systems that must continue delivering value tomorrow?
Immediately afterward, Andrea Francica takes the stage with “The Workload Is Coming (for your FileMaker Server).”
As applications become more connected and increasingly incorporate AI-driven processes, server-side workloads are changing. Background operations, worker servers, queues and asynchronous processing are becoming important architectural considerations.
Adding new capabilities to an existing application is one thing. Making sure the infrastructure can handle them reliably is another.
And reliability isn’t only about performance. It’s about understanding the system as a whole, from the architecture of its processes to the way it is operated and maintained.
Later that morning, we’ll take the discussion into even more uncomfortable territory with “FILEMAKER MUST DIE”: real stories of companies that decided FileMaker had to go.
Not hypothetical scenarios. Not arguments about which development platform is fashionable. Actual business decisions, with consequences for the people, processes and systems involved.
Because sometimes a FileMaker application survives for decades. Sometimes it needs to evolve. And sometimes the business decides it has reached the end of the road.
Understanding why is far more useful than pretending the question doesn’t exist.
And yes, we’re still going to talk about the future
Of course, surviving the future doesn’t mean spending two days discussing everything that might go wrong.
Quite the opposite.
We’re bringing together people who are actively exploring what comes next. Sergio Santoro will take us inside Halia, a real medical AI application built with FileMaker. Jeroen Aarts will demonstrate how to set up a self-hosted MCP server using n8n and FileMaker, while Caroline Crémieux-Charpentier will explore what happens when a FileMaker database starts answering back. Nicolas Franco will take us beyond traditional searches with an examination of semantic search.
We’ll also have AI Labs, practical demonstrations and conversations about what these technologies mean when they move beyond experiments and become part of real business applications.
And on Saturday, November 7, FMItalia.dev continues the week with a dedicated Italian-language program focused on the technologies, development practices and practical challenges facing FileMaker professionals.
The objective isn’t to convince everyone that AI will solve every problem, that every application needs rebuilding or that the future belongs to a particular technology.
It’s to help developers and businesses make better decisions about the systems they build, operate and depend on.
The future isn’t next
We chose Surviving the Future because the future of FileMaker isn’t just a product roadmap. It’s the future of the businesses using FileMaker, the developers maintaining it and the systems that have quietly become essential to everyday operations.
The latest security warnings are a timely reminder of that responsibility. They deserve immediate attention, independently of any conference.
But they also illustrate exactly why we need broader conversations about architecture, technical debt, infrastructure, modernization and the real value of software.
That’s what we’ve built Milan FileMaker Week to explore.
Not another collection of talks. Not another opportunity to admire technology for its own sake.
One track. One conversation. Two days.
And a room full of people who understand that the future of FileMaker is about much more than FileMaker.
Join us in Milan, November 5–6 for FMExchange, or November 7 for FMItalia.dev.
Because the future isn’t next. It’s already running on your server.
MILAN FILEMAKER WEEK 2026
Surviving the Future
November 3–7, 2026 · Milan, Italy
FMExchange: November 5–6 · International conference
FMItalia.dev: November 7 · Italian conference
Explore the full program and register here.

