A platform to control the complete cycle of sensitive data
Four capabilities that work together inside your infrastructure. This is what happens between your production databases and the environments where your teams work.
Your sensitive data never leaves your infrastructure
Overview
- v4Current version2 days ago
- v3New version3 months ago
- v2New version8 months ago
- PII found
- 11
- Entities
- 8
- Fields
- 49
- Records
- 542,143
| Name | Last run | |
|---|---|---|
| load-job-2964 | 4 hours ago | |
| load-job-2949 | 1 day ago |
Four phases, a single workflow
Each phase works with what the previous one produced, so rules are defined once and there are no manual handoffs between teams.
Discover
Find and classify the sensitive information in your sources.
View DiscoverGovern
Trace the journey of every piece of data and record who classified what and when.
View GovernAnonymize
Replace each sensitive piece of data with a realistic one, keeping the relationships between tables.
View AnonymizeProvision
Publish the dataset in the target environment or deliver it in the format you use.
View ProvisionWhat runs inside your infrastructure
Gigantics is installed on your own servers. Sensitive data is analyzed and transformed without leaving your perimeter.
Data sources
Oracle, PostgreSQL, SQL Server, MySQL, MongoDB and more, connected through taps.
Gigantics engine
Schema reading, personal information detection and risk level per field.
Rules and transformations
Fake data, masking, random shuffling and synthetic data, configurable field by field.
Secure destinations
Development, QA, analytics or AI databases, or download as SQL, JSON and CSV.
Orchestration through web interface and API, so the cycle can be triggered from your own pipeline.
Every decision is recorded
Lineage, access control, a reason for every change and signed reports: what an auditor asks for, generated while you work.
Immutable reports
Audit reports are signed. Once signed, a report cannot be modified or deleted.
Queryable lineage
For any field you know which source it comes from, which rule was applied to it and which environments it is in today.
Decisions with a reason
Every classification change is linked to who made it, when and why.
Role-based access
Organizations and projects separate access by team, with viewer, editor or administrator permissions.
Secure connections
SSH tunnels and encrypted protocols to connect to the source and destination databases.
Fits with what you already have
Databases
Relational, document, cloud, big data and mainframe: PostgreSQL, Oracle, SQL Server, MySQL, MongoDB, Cassandra, Neo4j, DB2 zOS and more.
View the connectorsDelivery and formats
Direct publishing to the destination databases, or download as SQL, JSON and CSV to load it wherever it's needed.
Orchestration
Web interface and API. Scheduled execution or triggered from your continuous integration tool.
Questions about the platform
Where is Gigantics installed?
On your own servers, Linux or Windows, in your data center or in your private cloud. Schema analysis, personal information detection and transformations run inside your perimeter.
Can I orchestrate the cycle from my pipeline?
Yes. Every project has API keys to invoke datasets, pipelines and jobs from external systems. A pipeline can be scheduled (daily, weekly…) or triggered from your CI/CD tool with an HTTP call.
Does Gigantics certify regulatory compliance?
No. Gigantics provides the operational capabilities—discovery, anonymization, access control and audit reports—that support frameworks such as GDPR, Chile's Law 21.719, DORA or ISO 27001. Effective compliance depends on the configuration applied and on each organization's processes.
See the complete cycle on your own data
We show you the four capabilities working on an architecture like yours.