Information for pay-as-you-go subscriptions and organizations that use Structural Cloud.

For general information about differences in feature support between self-hosted and Structural Cloud, go to .

Here are some items to be aware of if you use Structural Cloud.

Structural Cloud locations

We host instances of Structural Cloud in the following AWS Regions:

• us-east-1 - US East (N. Virginia)

• eu-central-1 - Europe (Frankfurt)

We can add additional Regions by request.

Structural Cloud security

For details about security in Structural Cloud, go to the .

Structural access to database servers

If you allowlist access to your databases, then add the to your allowlist.

Source and destination databases

Source databases contain the original data for Structural data generation. Structural writes the transformed data to a destination database.

contains an overview of the requirements for Structural source and destination databases.

Account Admin assignment

At least one account in your organization must be granted the built-in Account Admin global permission set, so that you can manage organization users and download the usage report.

By default, the first account in an organization is granted the Account Admin permission set. They can then grant the Account Admin permission set to other users in the organization.

For more information, go to .

SSO support in Structural Cloud

For single sign-on (SSO), Structural Cloud only supports Okta.

For information on how to enable and configure SSO, go to .

About the pay-as-you-go plan

The Tonic Structural Cloud pay-as-you-go subscription plan charges a regular monthly credit card payment for a Structural account. To manage the payments, Tonic.ai integrates with a payment processing solution.

The pay-as-you-go subscription grants a Structural Professional license.

You can configure generators for up to 20 tables across all of your workspaces. If you exceed the limit, Tonic.ai charges a flat fee per month for each additional table. Tonic.ai bills you separately for the additional tables.

Updating the payment information

Only the user who set up the account can update the payment information. Other users from the same email domain can only view the renewal date.

Access is not based on a global permission.

From the Billing tab, to update your payment information:

1. Click Manage Subscription.

2. In the payment processing solution, provide the updated payment details.

For Structural Cloud accounts, Structural Cloud onboarding is a two-week process to allow you to become familiar with the application and to generate Structural processed data to use in a variety of workflows.

Here are the necessary steps and overall process that you complete with your designated Tonic.ai Solutions Architect.

Prerequisites

To ensure that you are ready to start onboarding, make sure that Structural Cloud can access your source data.

Depending on your data source type, you might need to:

• Create a database user with read access.

• Configure profile permissions with your cloud provider.

• Make other configurations.

The required setup is described in the documentation for the specific data connector. For a list of connectors, with links to the individual connector documentation, go to .

If your database only allows connections from allowlisted IP addresses, then you must allowlist Structural static IP addresses. For details, go to .

Scoping requirements

When you start the onboarding process, you should have a good idea of following topics:

Select the datasets that are in scope

Select the first datasets for Structural to process.

These datasets should reflect a full use case for the Structural data, such as a testing workflow or a developer experience.

Decide the goals

You can use Structural to de-identify sensitive data and to subset data. You can also add Structural to your automation toolchain.

Your data also might have specific features that need special handling.

Decide what you want to focus on.

Set up the destination

Depending on your database, Structural can write output to:

• Destination database

• Files

• Container repository

• Tonic Ephemeral

Select the output mode and prepare the destination.

Plan who will configure how datasets are processed

De-identifying the data or creating a subset might require knowledge from the data users or database administrators.

Choose your teams and ensure that they are available.

Plan who will validate the output data

For example, depending on your organization’s needs, the validation might be done by the data users or the security personnel.

Ensure that they are available.

Onboarding process

After you meet the above requirements, it’s time to use Structural.

Here are the basic steps involved and expectations.

Scoping and planning

In the scoping requirements, we asked you to plan ahead:

• The preferred datasets.

• The onboarding goals.

During the first onboarding step, we finalize these plans.

Structural configuration

After a Structural training session, you should be able to complete the configuration needed to produce a desensitized output dataset.

This involves:

• Proper application of generators. For information about generators and how to apply them, go to .

• Any necessary subsetting. For information about subsetting in Structural, go to .

• Other configuration.

Iteration

To find a suitable configuration, you usually must work with the end data users to fine-tune the generator selections and subset configuration.

Automation

Determine the full processes and automation to ensure continued Structural value.

Onboarding timeline

The Structural Cloud onboarding uses the following timeline:

Day 1 - Project kick-off call (30 minutes), Structural Cloud license activated

Day 2 - Product training (1 hour)

Day 4 - Progress meeting (30 minutes)

Day 9 - Progress meeting (30 minutes)

Day 12 - Project closing meeting (30 minutes)