GeneratorsExport and import generators

Export and import generators

You can transfer generators between environments by exporting a trained generators from one environment and importing it into another.

This feature is useful when you are using an air-gapped environment to train generators or work with multiple MOSTLY AI accounts.

You can export the trained generator from a secure or otherwise separate environment and import it into a running instance of MOSTLY AI, where the generator can be used by anyone in your organization.

Export a generator

With the platform, you can export a generator in one of two ways.

Prerequisites

To export a generator, you must be its creator or have the Admin role in the organization.

Steps

  • Export a generator directly from the Generators page.
    1. From the Generators page, click the kebab menu of a generator, and select Export generator.
  • Export a generator after you open it.
    1. From the Generators page, click a generator to open it.
    2. Open the action menu by clicking the generator name, and select Export generator.

Result

The generator is exported as a ZIP archive. You can now import it into another instance of the MOSTLY AI Platform (local or remote).

Import a generator

You can import a generator into another instance of MOSTLY AI on the platform or with the Synthetic Data SDK.

With the platform, you can import a generator into another instance of MOSTLY AI.

  1. From the Generators page, click Import a generator.
  2. Use the upload area to browse your local file system or drag-and-drop the exported generator ZIP file.
  3. Click Proceed.

Result

The imported generator opens upon successful import. You can now use it to generate synthetic data.

Generator folder structure

You can explore the interactive folder and file structure of exported generators below.

📑

The structure below is an example containing template file names.

For example, <table_name> is replaced by the actual table name in the generator.

In an actual exported generator:

  • The template filenames depend on model types and table names.
  • The number of model folders and QA reports depend on the number of models and the number of tables in the generator.
  • generator.json
  • job_progress.json