FileMaker WebDirect vs modern web stack - 2026 reality check

Most weeks a buyer asks us a version of the same question: "Can we just put our FileMaker solution on the web?" The honest answer is yes - but the version of "the web" you get from FileMaker WebDirect is different to the version you get from a React or Next.js app sitting on top of the FileMaker Data API. They solve different problems, they cost different amounts of money, and the choice between them decides how your solution feels for the next five years. This is our 2026 reality check on both, with a bias-check up front: we ship WebDirect deployments, and we ship custom web stacks - usually for the same client, in the same project, against the same FileMaker file.

What WebDirect actually is

WebDirect is FileMaker Server's browser delivery layer. You build a FileMaker layout in FileMaker Pro, publish the file to FileMaker Server (or FileMaker Cloud), and authenticated users hit it in their browser without installing FileMaker Pro. The browser renders something close to the layout you designed, and the script engine, calculations and security model are the same as the desktop client. It is genuinely the fastest way to put a FileMaker solution in front of users who do not have FileMaker Pro licences.

Two things to be honest about. First, it is not server-side rendered - the browser opens a session, pulls down the layout, and runs an interactive client-server loop. That is fine for authenticated internal apps, terrible for public pages that need to load fast and be indexable. Second, it has not fundamentally changed in architecture in years - Claris ships steady incremental improvements but it is still the same shape it was in 2020. That stability is a feature for buyers; it is also the reason it cannot mimic a modern SPA.

What "modern web stack" actually means

When we say modern web stack on top of FileMaker, we mean a separate front-end - typically React, Next.js, Vue, or for marketing sites Webflow - deployed to its own host (Vercel, Netlify, AWS, Cloudflare, or a UK provider), talking to FileMaker Server through the REST Data API or OData. FileMaker becomes the database and script engine; the web stack becomes the user-facing layer. The two halves are versioned, deployed and scaled independently.

This is what you build when you need design fidelity, server-side rendering for SEO, sub-second page loads, or a UX that matches what a customer would expect from any other 2026 web product. It is also where the cost lives - you now have a real front-end project with its own auth, hosting, CI/CD and maintenance bill.

Head-to-head comparison

When WebDirect is the right call

• The audience is internal - staff, contractors, partners with a login.
• Concurrent users are in the tens, not the thousands.
• The interface is heavy CRUD and process work, not marketing-grade design.
• You already have a FileMaker solution and adding a web tier should not double the project cost.
• You want to inherit the FileMaker security model rather than rebuild it in a separate stack.
• The team that maintains it is the same team that maintains the FileMaker file.

For most UK SMEs we work with - operations dashboards, scheduling, light CRM, inspection reporting, finance back-office - WebDirect is the right call and pays back in months that a custom stack would not.

When a modern web stack is the right call

• The audience is customers, prospects, or the public - not internal users.
• Pages need to be indexable by Google and load on a poor mobile connection in under two seconds.
• You need design fidelity to your brand, not "FileMaker-styled".
• Concurrent usage is in the hundreds or thousands, or spikes unpredictably.
• The interface needs interactions WebDirect simply cannot do well - live search, complex animations, offline-first PWA behaviour, embedded mapping or canvas tools.
• You want to pay for hosting per request, not per Claris seat.

Customer portals, lead capture, e-commerce front-ends, public membership systems, anything that has to look and feel like a 2026 web product - this is where a modern web stack earns its budget.

The hybrid pattern we actually deploy

For mature FileMaker organisations, we rarely build one or the other. The shape that works is:

• FileMaker Pro / Go: for the power users and field staff who need the full client.
• WebDirect: for the wider internal user base who just need a browser tab into the same solution - finance, ops, scheduling, admin.
• Modern web stack (React / Next.js / Webflow): for anything customer-facing or public, sitting on top of the FileMaker Data API.

The FileMaker file is the system of record across all three. The web stack uses tokenised Data API calls (often through a small middleware layer for rate-limiting and shape transformation), and the WebDirect users live inside the FileMaker security model. Customers never know there is a FileMaker back-end - they just see your brand.

Cost reality (UK 2026)

Honest numbers from current Neptune Digital quotes:

• WebDirect layout pass on an existing FileMaker solution: typically £4k–£15k extra on the build to make existing layouts behave on the web.
• Custom internal portal (auth, basic CRUD, branded UI) on top of the Data API: typically £20k–£45k.
• Customer-facing portal (proper design, SEO, payments, document upload, full responsive): typically £45k–£120k.
• Hosting: WebDirect inherits FileMaker Server / Cloud cost. A custom web stack adds typically £20–£150/month for hosting depending on traffic and provider.
• Ongoing maintenance: WebDirect adds little; a custom web stack adds typically £400–£2,000/month under a normal support agreement.

For comparable buyer context, see our UK FileMaker development cost guide.

Buyer's checklist

• Who is the user - employee, partner, customer, or public?
• Does the page need to be indexable by Google? If yes, WebDirect is out.
• What is the realistic concurrent user count in 18 months, not today?
• Does the design need to match a marketing brand, or is "clean and functional" acceptable?
• Are you happy paying per Claris seat for these users, or do you need anonymous / token access?
• Who maintains it - the same FileMaker partner, or a separate web team?
• Is there an existing FileMaker file that should be the system of record, or are you greenfield?

Answer those seven honestly and the right architecture usually picks itself.

See also - Is FileMaker still worth using in 2026?, FileMaker Go vs native iOS, and Best FileMaker Developers in the UK.