FileMaker Server. Shared data under your control.

Sharing databases via FileMaker Server

The server makes FileMaker files available to Pro, Go and WebDirect users and to prepared integrations. Data remains on the host, and access is controlled by accounts and permission sets. Before implementation, we check the compatibility of the client, server and operating system versions.

• Access via Pro, Go and WebDirect according to host version.
• Admin Console: files, user sessions and service status.
• Roles and permissions in the application and securing connection channels.
• Resources tailored to data, reports, integrations and workloads.

Integrations and background tasks

The server can support scheduling tasks, FileMaker Data API and ODBC/JDBC connections in version-available variants. A plug-in launched on a server must be compatible with its system, version and execution context.

Each task receives monitoring and error handling rules. The environment requirements depend on the running time of imports, the number of parallel requests and the size of files.

Administration and recovery

The scope includes updates, certificates, resource monitoring, logs and backups. We also plan tests to restore data and key functions. Local backups, an additional off-site backup and a possible standby environment serve different purposes.

We start with an inspection of existing installations. We do not assume that purchasing a new license or simply moving a file will remove the dependencies of the old solution.

Accounts, certificate and access rules

Server preparation includes a compatible operating system, domain, TLS certificate and access to only the services you need. We separate administrator, user and integration accounts. The scope of visible records and allowed operations is set in the application.

We check file encryption and key storage, logging, and dependencies on identity services. We test configuration changes using an account with limited privileges. Maintenance documentation also indicates who is responsible for updates and recovery.

Local Backup, Remote Backup and Standby Server

Local backups let you recover earlier data, while an additional backup outside the primary environment protects against losing that environment. FileMaker Server 2026 offers Remote Backup and Standby Server add-ons. The first provides remote backups; the second prepares a standby environment.

Selecting add-ons does not replace defining retention, access to backups and a switchover procedure. We check requirements, licenses and how to restore database files and container data. The test ends with a user logging in and completing a key task in the restored application.

When taking over an older host, we also check Custom Web Publishing and PHP/XML dependencies. Support varies by version and host system; migration may require switching to FileMaker Data API or changing the publishing layer.