FileMaker hosting. Team access and database support.

Own infrastructure, managed hosting or FileMaker Cloud?

FileMaker Server can run in an environment managed by a company or hosting provider. We then determine the scope of administration of the system, FileMaker and the application itself. These are different responsibilities: an efficient server does not determine the correctness of the script or integration.

FileMaker Cloud is a separate Claris product. It limits the scope of self-administration, but requires checking login, licenses, plug-ins and connection to other systems. Not every legacy application can be migrated without changes.

Team access and connections to other systems

We check the number of users, their devices and places of work. Pro, Go and WebDirect clients must be compatible with the host version. Access from the Internet requires a valid certificate, account security and an appropriate range of open services.

We document integration accounts, schedules, drivers and plug-ins separately. Connecting to an external database through ODBC is different from exposing FileMaker as an ODBC data source. This distinction matters when choosing Server or Cloud.

Backup is also recovery

Timing and retention should depend on how much data the company can lose and how long it can operate without the system. We determine the storage location, an additional copy outside the basic environment, access to files and control of task execution.

Server provides local and progressive backups, plus Remote Backup and Standby Server add-ons in version 2026. Cloud has its own managed backup mechanisms. We choose the approach, retention and recovery procedure to match the company's needs and the terms of the selected service.

A restore test covers database files, container data and application dependencies. After restoration, we check login, key scripts, a report and an integration. Verifying a file alone does not replace this test.

Scope of administration and updates

Before launching, we agree on who watches the logs, disk usage, copying, certificate expiration and schedule tasks. We determine the method of accepting applications and the windows for planned work.

The update requires checking the clients, operating system, plugins and integrations on the copy. The plan should include a period of unavailability and a return to the previous environment if the acceptance test indicates a problem.

The review covers encryption of database files, container data and backups, as well as key protection. For older environments, we also inventory PHP/XML publishing and check whether the planned environment supports it.

What to prepare for a hosting quote?

The better we describe the use of the system, the easier it is to choose the environment and scope of care. If some information is unknown, the first step may be to audit the existing host.

The offer also specifies the launch or migration cost, settlement period, minimum contract period and terms of its termination. We separate the environmental, licensing, maintenance and ancillary work fees so you can compare the full cost of the options.

The availability of the SLA service, the method of its measurement and exclusions related to planned work are determined separately from the response time to the notification and the data recovery time.

• versions of FileMaker, server and user systems
• number of people and way of working in Pro, Go and WebDirect
• number and size of files, containers and data growth
• list of APIs, ODBC, plugins and server tasks
• data location, access and logging requirements
• expected recovery time, acceptable data loss and backup retention
• bandwidth, typical transfer and remote work requirements

Changing the environment with a test before switching

The transfer covers not only the main database files. We include container data, schedules, certificates, plugins, drivers and integrations. We determine administrative access, work time and how to stop changes in the final stage of migration.

In the test environment, we check login and selected user processes. After switching, we control data, reports and background tasks. We document the acceptance criteria and the decision to return if the application fails the agreed tests.