When to deliver your FileMaker solution through WebDirect, when to build a separate web stack on top of the FileMaker Data API, and the hybrid pattern most serious UK deployments end up running.
Updated May 2026 · 10 min read · By Neptune Digital
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.
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.
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.
| Dimension | FileMaker WebDirect | Modern web stack on FileMaker Data API |
|---|---|---|
| Build cost (typical UK 2026) | Included with FileMaker build | £20k–£120k+ on top of FileMaker |
| Ongoing maintenance | Same as FileMaker solution | Separate front-end maintenance line |
| Design fidelity | FileMaker-layout look & feel | Pixel-perfect to your brand |
| Concurrent users (practical) | ~50–100 per server | Thousands (front-end scales independently) |
| Public-facing / SEO | No - not indexable | Yes - SSR / static where needed |
| Mobile UX | Workable on tablet, weak on phone | Native-grade responsive UX |
| Offline / poor connection | No | Possible (PWA, optimistic UI) |
| Auth / SSO | Native FileMaker + SAML/OAuth | Built separately (Auth0, Entra, etc.) |
| Licensing model | Named-user Claris licence required | Anonymous or token-based - no Claris seat per user |
| Time to first version | Days | Weeks to months |
| Best fit | Internal authenticated users | Customers, public, high-volume, brand-led |
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.
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.
For mature FileMaker organisations, we rarely build one or the other. The shape that works is:
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.
Honest numbers from current Neptune Digital quotes:
For comparable buyer context, see our UK FileMaker development cost guide.
Answer those seven honestly and the right architecture usually picks itself.
See also - Claris Studio Discontinued (March 2027), Is FileMaker still worth using in 2026?, FileMaker Go vs native iOS, and Best FileMaker Developers in the UK.
No, but it is narrower than Claris's marketing suggests. WebDirect is still actively shipped, supported and improved with every FileMaker Server release, and we run multi-year UK production deployments on it. What it is not is a replacement for a modern web stack - it does not deliver SEO-friendly public pages, single-page-app performance, or the UX standards your customers expect from a 2026 web product. It is an internal-tool delivery layer, and judged on that scope it works.
Claris's official guidance lands around 100 concurrent WebDirect users per FileMaker Server (FileMaker Cloud sits at similar limits depending on tier), and that is broadly what we see in the field for well-built solutions. The hard ceiling is rarely a number - it is layout complexity, script length per user action, and how many unstored calculations sit between the user and their next click. A lean solution will serve 100 cleanly; a heavy one will struggle at 40. If you genuinely need 500+ concurrent web users, WebDirect is the wrong tool and a modern web stack on top of the FileMaker Data API is the right one.
Technically yes, practically no. WebDirect renders into an authenticated browser session, has no server-side rendering, and is not indexable by Google in any meaningful way. We have never deployed it as a public site and we would actively advise against it. For public pages - marketing, lead capture, customer portals that need to be discoverable - use a real web stack (Webflow, Next.js, React) and call FileMaker through the Data API behind the login wall.
It means a separate front-end (typically React, Next.js or Vue, sometimes Webflow for content-heavy sites) deployed to its own host, that talks to FileMaker Server's REST Data API (or OData) for data and scripts. The FileMaker file becomes the system of record and the script engine; the web stack becomes the user-facing layer. This is the architecture you want for customer-facing portals, high-traffic apps, anything that needs proper SEO, or anything that needs design fidelity that WebDirect cannot match.
Yes, materially - by roughly a factor of 3 to 10 depending on scope. A WebDirect layout is essentially free once you have the FileMaker solution; a custom React front-end with auth, design, hosting, CI/CD and ongoing maintenance is a real project. The question is not which is cheaper, it is whether what WebDirect gives you is good enough for the audience and use case. For internal users, almost always yes. For customers and the public, almost always no.
Sort of. FileMaker layouts can be designed for tablet and phone form factors, and WebDirect will render them, but the interaction model (modal-heavy, click-driven, full-page redraws) feels dated on a phone in 2026 compared to a properly-built mobile web app. For a serious mobile user base, FileMaker Go on iPad/iPhone is a much better experience than WebDirect on a phone - and for Android, a thin native or web app over the Data API beats both.
Yes - WebDirect supports SAML and OAuth-based external authentication (Microsoft Entra ID, Google Workspace, Okta), the same identity providers FileMaker Pro does. This is one of the genuine strengths of staying on WebDirect for internal tools - you inherit the FileMaker authentication model for free, including row-level privilege sets, without having to rebuild it in a separate web stack.
WebDirect for the internal back-office (heavy CRUD, finance, operations, scheduling), and a separate modern web stack for anything customer-facing or public (lead capture forms, customer portals, marketing site). Both talk to the same FileMaker file. The public web stack uses the Data API behind a token; the WebDirect users sit inside the FileMaker security model. This is how we deploy at scale and it sidesteps the false choice of one or the other.
