FileMaker Cloud. Application hosting without your own server.

What remains with the application owner?

The hosting service does not replace role design, data quality, or script maintenance. The organization is still responsible for who has access to the information and how the application works. The method of logging in and assigning users must comply with the terms of the service.

Claris Customer Console is used to manage your team, users and the service. The application still needs access accounts and permission sets corresponding to the roles. When an employee leaves, we check both team membership and access to the solution.

FileMaker Cloud limitations important for migration

Cloud does not support server-side plug-ins, PHP/XML publishing, or sharing your own database with ODBC/JDBC clients. Using supported external ODBC sources is a separate connection direction.

If your existing system relies on such mechanisms, you need to design an alternative or stick with Server. First, we inventory dependencies, then choose hosting.

Backups and service terms

Cloud has its own mechanisms for automatic copies, downloading and restoring data. We check the current retention, available functions, region and license scope for the selected plan. We do not equate product settings with an individual commitment to reproduce the entire company process.

The move starts with a dependency review

We inventory .fmp12 files, containers, accounts, server scripts, plugins and connections. We check paths to local resources and operations requiring the host system. Containers stored externally must meet Cloud requirements.

First, we prepare users and a test version of the application. Then we check logging in, working with data, scripts, reports, Go, WebDirect and API. Only after receipt do we plan to switch over and control the final changes in the data.

Convenience of service or greater control over the environment?

Cloud is worth considering when the application falls within the scope of the service and the company wants to limit the administration of its own host. The login method, service region, plan costs and availability of connections to other systems are important.

Server gives you more freedom with plugin dependencies and system configuration. The comparison covers the entire solution: application functions, integration, copies and administrators' work. The name "cloud" alone should not determine the choice.