Skip to main content

Before You Buy

Table of Contents:

Before You Buy

Overview​

360Deploy is a product that simplifies the tedious process of deploying changes in a development database to an existing production database. This can be done with the click of a button while eliminating human error and reducing the downtime traditionally associated with the process. All that is required is some simple configuration, and click Deploy!

For a better understanding, consider the typical FileMaker file development scenario of a production and development server. The production server continuously hosts solutions for clients. The development/staging file is the database where alterations are being made by developers to enhance utility and better serve client's needs. Overhauling the old file to reflect the new one typically involves a process during which production is shut down and administrators sift through tables, scripts, and fields to reflect updates. We seek to bypass this arduous task by automating the entire series of events.

The entire process takes only as long as it takes to import data based on your database size, during which the databases are paused. This allows files to be updated without worrying about how often or when the changes occur. The setup consists of installing our plug-in in the FileMaker client running the deploy file, and some simple script copy/pasting.

Why use 360Deploy?​

Altering live databases has traditionally been a tedious, intrusive task. It consists of server downtime and technical labor at the expense of company resources. 360Deploy is capable of doing that in minutes by seamlessly automating the process. What our software does is create a clone of the development database, transfers it to the production server, and then imports data from production into the clone to absorb the new architecture. As a safeguard, a back-up of the production file is also created on the machine before the imports occur should clients wish to revert back to the old structure.

  • Ideal for frequent upgrades to a databases of any size
  • Minimizes file downtime, only pausing file temporarily during import of data
  • Drastically reduces complexity and time required to upgrade new database architecture
  • Includes import of scripts and calculations
  • Backs up production file in event changes want to be reverted

System requirements​

  • 360Deploy requires FileMaker Pro or Advanced 16 or later to run the actual import process.
  • Production databases must be hosted on FileMaker Server 14 or later
  • FileMaker Cloud is NOT compatible with 360Deploy

Licensing​

There are four types of licenses for 360Deploy. Pricing for each license type is available here by clicking the 'pricing' button.

  • Demo license
    • Can only deploy to the 360Deploy Demo Solution included in the download.
  • Enterprise License
    • This allows deployment of unlimited FileMaker solutions to a single deployment server. It is not legal to use this license for multiple different clients, for instance in a shared hosting server or vertical market hosted server.
  • Solution Bundle License
    • This allows deployment of a single FileMaker solution (this can be a multi-file solution) to unlimited deployment servers. The deployed solution can have different names for different customers. This license edition is ideal for vertical market solution developers deploying changes across multiple servers for a single solution. It can also be used by businesses with a single in-house solution deployed across multiple servers.
  • Express License (DISCONTINUED)
    • This license originally allowed for deployment of a single FileMaker solution (this can be a multi-file solution) to a single deployment server. This license type was discontinued and is now treated the same as an Enterprise license.

An Enterprise License is included with the 360Works Portfolio License at no additional charge. Any current Portfolio License holders will be able to immediately start using 360Deploy.

Note:

360Deploys captures the list of databases when you run your first deployment for a license (and after a license reset). This is assumed to be all the files in your solution. Following that, you are allowed to deploy a subset of that list of files. If you have a large list of files in your solution, and you don't want to deploy them all at once, reach out to support@360works.com, and we can hard code the list of databases against your license, so you will be able to deploy a subset of that large list of databases without issue.