Platform / Provision
Teams receive usable data without touching production
The protected dataset reaches the target environment or is downloaded in the format you need, on demand or on a schedule. Development, QA and analytics stop needing production credentials.
Datasets
Only the volume each environment needs
A QA environment rarely needs the full copy of production. Gigantics generates bounded, reproducible subsets, and saves them as versioned datasets.
- Limit by number of records or percentage
- Condition filters to isolate test cases
- Versioned, reusable datasets
- Download as JSON, CSV or SQL
Destinations
From the ticket to the pipeline
Destinations are configured once in the platform. From then on, the dataset is loaded directly into them: provisioning stops being a request and becomes one more step in the pipeline.
- Direct load into the destination databases
- Scheduled execution or triggered by API
- Key-protected endpoints for teams or vendors without an account
- Keys that are rotated or revoked once access is no longer needed
The four capabilities
Questions about data delivery
Does it integrate with my CI/CD pipeline?
Yes. Pipelines can be scheduled or triggered by API, so environments are refreshed on every deployment or at the frequency you define, without manual intervention.
Can I deliver just part of the data?
Yes. You can limit the volume by number of records or percentage and filter by specific conditions, so each environment receives only what it needs.
What formats can I receive the data in?
Directly into the configured destination databases, or as a downloadable dataset in JSON, CSV or SQL.
Can I deliver a dataset to someone who doesn't use the platform?
Yes. A dataset can be exposed on an endpoint with an API key, so a third party downloads the already transformed set. The key is rotated or revoked once the access is no longer needed.
Set up your first environment
We show you the full cycle, from discovery to delivery, on an architecture like yours.