How embedded deployment works

Deploying a Web Viewer app means getting your built web bundle into a place FileMaker can render it inside a Web Viewer object. There's no server to stand up by default — the Agentic Development Toolkit (ADT) project template builds your app with vite-plugin-singlefile, so pnpm build produces one self-contained file, dist/index.html, with everything inlined. What differs between deployment methods is where that file lives and how a Web Viewer finds it.

Embedded: the built-in method

This is the method ADT sets up for you, and the only one its tooling automates. The built HTML is stored as data inside your FileMaker file, and a Web Viewer loads it from there — no external host required.

ADT's installed components provide this storage. They include a small ADT table with an AppName field: set that field to the app name for a given Web Viewer, and the Web Viewer's calculated URL renders the matching HTML. The HTML is stored using FileMaker's Persistent Data feature rather than an ordinary field, which is what lets more than one deployed app live in the same file, each identified by its own app name.

Ask your coding agent to Deploy to FileMaker. The agent builds the app, selects the intended connected file and app name, stores the result, and verifies it in the target Web Viewer. FileMaker Pro must be running with the target file open and Agent Access turned on.

Pros	Cons
No external host to run or pay for	Can't use server-side JavaScript libraries
Works fully offline after the app is stored	Can't use server-side JavaScript libraries
Multiple apps can share one file, selected by app name	The stored build is separate from editable project source

See Deploy to FileMaker.

Note  Other deployment shapes exist A Web Viewer can also be pointed at a hosted URL instead of the file's stored HTML. See Custom deployment patterns for the Hosted and Downloaded (hybrid) architectures — neither is built or supported by ADT.

Next step

Deploy to FileMaker walks through the embedded deploy step by step. How ADT Connects to FileMaker covers how Agent Access, ADT's components, and MCP server fit together around it.