Yesterday, Claris CEO Ryan McCann shared one of the most important signals we’ve seen for the future of the FileMaker ecosystem: native movement toward AI-assisted development workflows inside FileMaker itself.
In recent years, parts of the FileMaker community have already been moving in this direction. Developers like Mislav Kos from the team at Soliant Consulting, alongside a handful of other innovators in the ecosystem, have been among the first to seriously explore what AI-assisted FileMaker development could become.
At Devin, we see this moment as much bigger than “AI features.”
We see it as the beginning of a completely new era for FileMaker development.
And importantly: AI-assisted development does not reduce the need for DevOps. It dramatically increases it.
Faster development leads to higher complexity
The traditional bottleneck in software development used to be writing code. As Claris themselves put it in their recent announcement: “Writing code used to be the hard part. It isn’t anymore.”
That shift changes everything.
When developers — or AI agents — can generate larger amounts of functionality in less time, systems evolve faster. Architectures become more dynamic. Experiments happen more frequently. Technical depth increases, and the cost of mistakes rises with it.
In other ecosystems, this has already happened.
AI-assisted development is accelerating software delivery across the industry, but it is also increasing:
- deployment complexity,
- infrastructure requirements,
- technical debt,
- rollback needs,
- testing demands,
- and the importance of traceability.
FileMaker will be no exception.
In fact, because FileMaker solutions often power real operational workflows inside businesses, reliability becomes even more critical when development velocity increases.
The binary challenge becomes more important — not less
One of the unique realities of FileMaker development is the binary .fmp12 format.
As development workflows become increasingly AI-assisted, the importance of robust tooling around that binary format only grows.
Generated changes still need to be:
- tracked,
- analyzed,
- reviewed,
- tested,
- deployed safely,
- and sometimes rolled back quickly.
That is exactly where modern DevOps workflows become essential.
AI can help create functionality faster. But faster creation without deployment discipline, can easily lead to chaos.
The future is not AI instead of DevOps.
The future is AI powered by DevOps.
AI can create technical debt at unprecedented speed
One of the most overlooked realities of AI-assisted development is that AI is extremely good at producing working solutions quickly — but not necessarily sustainable systems.
Without proper tooling and engineering workflows, teams can accumulate technical debt faster than ever before.
This is especially important in FileMaker environments where:
- long-lived business systems evolve over many years,
- multiple developers collaborate across releases,
- and deployments involve production-critical data.
As the ecosystem enters this next phase, developer experience will matter more than ever:
- better visibility into changes,
- stronger deployment confidence,
- improved analysis tooling,
- safer collaboration,
- and workflows that help teams move fast without losing control.
That’s the future we believe the FileMaker ecosystem deserves.
A bigger ecosystem requires better tooling
We also believe Claris’ direction has the potential to significantly expand the FileMaker ecosystem itself.
AI lowers barriers.
It accelerates prototyping.
It enables new kinds of builders.
And it increases what small teams can accomplish.
That is incredibly exciting.
But ecosystem growth also increases the need for professional tooling infrastructure around development lifecycles.
As more ambitious solutions are built, expectations around software quality, resilience, deployment safety, and operational maturity rise alongside them.
This is something the broader software industry learned years ago.
Now the FileMaker ecosystem is entering that same transformation.
We’ve been preparing for this moment
At Devin, this shift is deeply aligned with the direction we’ve already been heading. As we shared earlier this year, we recently entered a new phase as a company — rebuilding core technology and investing heavily into the future of DevOps for the FileMaker ecosystem.
We cannot share much yet about Devin 2.0.
But we can say this:
We believe the FileMaker ecosystem is about to undergo one of the biggest workflow transformations in its history.
And we are building for that future.
A future where AI-assisted development becomes normal.
A future where deployment safety matters more than ever.
A future where modern DevOps tooling becomes foundational infrastructure for serious FileMaker teams.
The next generation of FileMaker development is coming fast.
We’re excited to help build what comes next.
