A Tonic Structural implementation can involve the following roles - from those who set up the Structural environment to the consumers of the data that Structural processes.
Note that these roles are not related to role-based access (RBAC) within Structural, which is managed using permission sets.
For self-hosted instances of Structural.
Infrastructure engineers set up the Structural application and its relevant dependencies. They are typically DevOps, Site Reliability Engineering (SRE), or Kubernetes cluster administrators.
Infrastructure engineers perform the following Structural-related tasks:
Ensure that the proper infrastructure is ready for Structural installation based on the deployment checklist.
Follow the installation instructions. Works with Tonic.ai support as needed.
Perform routine maintenance of Structural and the Structural environment. Updates Structural and its dependencies as needed.
Create Structural-processed data pipelines for development and testing workflows.
For both self-hosted instances of Structural and Structural Cloud.
Database administrators integrate Structural into your data architecture to support Structural data connectors.
They ensure that source databases are available to Structural, and that Structural can write to destination databases.
Database administrators perform the following Structural-related tasks:
Set up the required Structural access to source databases.
Set up destination databases for Structural to write transformed data to.
Structural users are the actual users of the Structural application.
Depending on the use case, Structural users might be compliance analysts, DevOps, or data engineers.
Tonic users perform the following Structural-related tasks:
Use the Structural data generation workflow to configure the logic used to transform source data and to generate the transformed data.
Work with data consumers to produce usable data
Data consumers are the end users of transformed destination data.
They are typically QA testers, developers, or analysts.
Data consumers perform the following Structural-related tasks.
Validate the usability of the destination data.
Provide guidance on application-specific requirements for data.
Security and compliance ensure and validate that the data that Structural produces meets expectations, and that Structural is compliant with other security-related processes.
Security and compliance specialists perform the following Structural-related tasks:
Provide guidance on what data is sensitive.
Sign off on proposed approaches to mask sensitive data.
Approve data access and permissions.
Tonic Structural provides different license plans to accommodate organizations of different sizes who have more or less complex data architectures.
The Basic license is designed for very small organizations who have a very simple data architecture. It provides access to Structural's core de-identification and data generation features.
The Basic license allows access for a single user, with an option to purchase an additional two users.
There is no access to .
With a Basic license, you can create workspaces for one data connector type. The data connector type must be one of the following:
With a Basic license, your Structural instance can have only one Structural worker. This means that only one sensitivity scan or data generation job can run at the same time.
With a Basic license, you can create and configure workspaces, and run data generation for those workspaces.
The Basic license does NOT provide access to the following features:
Custom generators
With a Basic license, you only have access to the basic version of the Structural API.
You cannot use the basic Structural API to perform the following API tasks, which require the advanced API:
The Professional license is designed for larger organizations that have more complex data architectures. The organization might have a larger team that supports multiple databases.
The Professional license provides access to a larger set of Structural features than the Basic license.
The Professional license allows up to 10 users. You can purchase access for unlimited users as an add-on.
With a Professional license, you can create workspaces for up to two types of data connectors. You can purchase one additional data connector type as an add-on.
With a Professional license, your Structural instance can have more than one Structural worker.
This means that you can run multiple jobs from different workspaces at the same time. You can never run multiple jobs from the same workspace at the same time.
With a Professional license, you can do the following:
Create and configure workspaces, and run data generation for those workspaces
The Professional license does NOT provide access to the following features:
With a Professional license, you only have access to the basic version of the Structural API.
You cannot use the basic Structural API to perform the following API tasks, which require the advanced API:
The Enterprise license is ideal for very large organizations that have multiple teams that support very large and complex data structures, and that might have more requirements related to scale and compliance.
It provides full access to all Structural features.
An Enterprise instance does not limit the number of users.
You can use any number of any of the available data connectors.
The following features are exclusive to the Enterprise license:
The Enterprise license provides exclusive access to the advanced API.
The advanced Structural API provides access to all of the available API tasks, including the following tasks that are not available in the basic API:
The following table compares the available features for the Structural license plans.
You can .
For a self-hosted instance, Structural provides administrator tools that allow you to and .
You can to customize your instance.
On a self-hosted instance, based on your , you have access to the full set of supported data connectors.
Structural Cloud is our secure hosted environment. On Structural Cloud, Tonic handles monitoring Structural services and updating Structural.
Structural Cloud does not include:
. Structural Cloud uses a single configuration.
Access to the following data connectors:
Each Structural Cloud user belongs to a Structural Cloud organization, which is determined either by the user's email domain or by a workspace invitation. Structural Cloud users do not have any access to workspaces or users from other organizations.
Each free trial user is in a separate organization, along with any users that they invite to have access to a free trial workspace.
You can use to view the current sensitivity status based on the current workspace configuration.
- Can view foreign keys from the data, but cannot add virtual foreign keys
The Professional license is also granted to .
You can use to manage your Structural users.
Those data connectors can be of any type except for and .
Use to view the current sensitivity status for your workspace configuration.
. The Professional license does not allow you to assign the built-in Viewer and Auditor permission sets.
. The comments can trigger email notifications.
Run and configure .
Use to generate a smaller destination database.
Create .
Use to add destination database records and update existing destination database records, but keep unchanged destination database records in place. The Professional license does not allow you to connect to migration scripts.
Use view to view and address both conflicting and non-conflicting changes to the source data schema.
Use to have Structural decrypt source data, encrypt destination data, or both.
Request , which are primarily developed to preserve encryption that can't be managed using Structural data encryption. You can also purchase custom generators.
The Enterprise license provides exclusive access to the and data connectors.
| Feature | Basic | Professional | Enterprise |
|---|
Structural Cloud also supports a pay-as-you-go plan, where free trial users can move on to set up a monthly subscription. For more information, go to .
For information about Structural Cloud organizations, go to .
The Account Admin permission set allows a Structural Cloud user to manage organization users and workspaces. For information about granting access to the Account Admin permission set, go to .
Number of users | 1 2 additional users available as add-ons | 10 Unlimited users available as an add-on | Unlimited |
1 data connector PostgreSQL or MySQL | 2 data connectors 1 additional data connector available as an add-on Any data connector except for Oracle or Db2 for LUW | Unlimited number from any available data connector |
Manager | Manager, Editor | Manager, Editor, Auditor, Viewer |
Custom generators | Available for purchase | 2 included Additional ones available for purchase |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
✓ | ✓ |
Concurrent jobs (more than 1 worker) | ✓ | ✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
✓ |
Structural API |
Tonic Structural data generation combines sensitive data detection and data transformation to create safe, secure, and compliant datasets.
The Structural data generation workflow involves the following steps:
You can also view this video overview of the Structural data generation workflow.
To get started, you create a workspace. When you create a workspace, you identify the type of source data, such as PostgreSQL or MySQL, and establish the connections to the source database and the destination location. The source database contains the original data that you want to synthesize. The destination location is where Structural stores the synthesized data. It might be a database, a storage location, a container repository, or an Ephemeral database snapshhot.
Next, you analyze the results of the initial sensitivity scan. The sensitivity scan identifies columns that contain sensitive data. These columns need to be protected by a generator.
Based on the sensitivity scan results, you configure the data generation. The configuration includes:
Assigning table modes to tables. The table mode controls the number of rows and columns that are copied to the destination database.
Indicating column sensitivity. You can make adjustments to the initial sensitivity assignments. For example, you can mark additional columns as sensitive that the initial scan did not identify as sensitive.
Assigning and configuring column generators. To protect the data in a column, especially a sensitive column, you assign a generator to it. The generator replaces the source value with a different value in the destination database. For example, the generator might scramble the characters or assign a random value of the same type.
After you complete the configuration, you run the data generation job. The data generation job uses the configured table modes and generators to transform the data from the source database and write the transformed data to the destination location. You can track the job progress and view the job results.
The Tonic Structural synthetic data platform combines sensitive data detection and data transformation to allow users to create safe, secure, and compliant datasets.
Common Structural use cases include creating staging and development environments and trying out a new cloud provider without complex data agreements. Structural allows you to reduce bug counts, shorten testing life cycles, and share data with partners, all while helping to ensure security and compliance with the latest regulations, from GDPR to CCPA.
You can use Structural APIs to integrate with CI/CD pipelines or to create automated processes that ensure that the generated data is available on demand.
Structural data generation workflow
Overview of the Structural steps to generate de-identified data
Structural deployment types
You can use Structural Cloud or set up a self-hosted Structural instance
Structural implementation roles
Functions that participate in a Structural implementation
Structural license plans
View the license options and their available features