In industry comparisons, the question is often framed as "low-code or custom?". It is a false debate. A custom application is an application designed for your company, your processes and the way you work, as opposed to standard off-the-shelf software. Whether it is built with FileMaker or developed as a classic web application (PHP, MySQL, JavaScript…), it is still custom. So the real question is: for your project, which tool is best?
And contrary to a common belief, the answer has nothing to do with features.
Features do not separate the two approaches
Business rules, calculations, automation, access rights, data exchange with other software through APIs: anything a web application can do, a well-designed FileMaker application can do too. In both cases, the quality of the result depends above all on the design and on the developer, not on the tool.
Data volume is not a criterion either. FileMaker is built on a genuine relational database engine: a single file can reach 8 TB and hold up to one million tables (Claris Community). These are limits that a business management application never comes close to.
What really sets the two approaches apart lies elsewhere: in the number of people who will use the application, and in the way the data needs to be presented to them.
The real criterion: how many users, and who they are
FileMaker is rightly known for teamwork. It is the ideal tool to get a team collaborating around its data: a department, an SME, a production site. Among our clients, the vast majority of FileMaker applications are used by fewer than 20 people, and the tool remains very comfortable up to around a hundred users.
Beyond that, a web application generally becomes the most relevant choice, and the reason is first and foremost economic. With FileMaker, every person who accesses the application needs their own user licence (Claris, contrat de licence). Public prices listed in November 2026 range from €19 to €24 per user per month for FileMaker Server (La Fabrique du Net). In practice, depending on the number of users and the type of licence (individual or site licence), the figure is closer to €15 per user per month. Above 100 users, pricing is on quotation and comes to around €11.
As an indication:
- for a team of 15 people, licences come to about €3,000 a year;
- for 200 people, the cost reaches about €27,000 a year. At that level, a site licence brings it back down to around €17,000 a year.
A web application, on the other hand, carries no per-user licence cost: you pay for its development and hosting, whether 10 or 1,000 people log in.
The same reasoning applies to users outside the company. If your application has to be open to your customers, your suppliers or the general public, with many, occasional or anonymous users, the web is the natural choice.
Visual presentation: the web's advantage
This is the second real point of difference. A web application offers almost complete freedom over presentation: an elaborate visual identity, interactive dashboards and charts, interfaces designed for the general public, display adapted to every screen. The JavaScript libraries available are countless.
FileMaker offers efficient interfaces that are quick to build and perfectly suited to everyday business use, but within a more constrained visual framework. For a team that enters, consults and manages its activity, this is rarely a problem. For an application that has to win over customers or showcase your brand, the web has the edge.
Development time and budget: FileMaker's strength
Where FileMaker clearly takes the lead is speed of delivery: it is a rapid application development (RAD) tool. A project estimated at six months in traditional development can, on a low-code platform, be delivered in six to eight weeks (La Fabrique du Net). Changes follow the same pace: a new field, a new screen or an adjusted business rule can often be done in a few hours. These figures are actual development time: as everyone knows, a project in reality stretches over a longer period, between approvals, testing and team availability.
On the budget side, even though a FileMaker developer may cost more per day than a web developer, whether freelance or in an agency, you should come out ahead thanks to the development time saved.
The full calculation therefore weighs faster development that costs less overall on one side, against annual licences that grow with the number of users on the other. For a small team, the balance tips very clearly in FileMaker's favour. For several hundred users, it is reversed.
Why not both?
The choice is not necessarily either/or. A common approach is to keep FileMaker for the internal team, who manage the data day to day, and to offer a web portal to external users (customers, partners, field technicians). The two communicate through the FileMaker Data API: everyone gets the best-suited tool, on one and the same database.
Key takeaways
FileMaker and a web application can deliver the same features: it is the design that makes a good application, not the tool. To choose, ask yourself these questions instead:
- How many people will use the application? A team of a few people up to around a hundred: FileMaker is ideal. Several hundred: the web application becomes more cost-effective.
- Who are they? Identified employees: FileMaker. Customers, partners or the general public: the web.
- How much does visual presentation matter to you? An efficient working tool: FileMaker. A polished showcase for the outside world: the web.
- What timeline and budget? To move fast and evolve the tool often, FileMaker stays one step ahead.

