Dymium careers

Dymium sits on the network between the user and the data stores, wherever they might be housed. The owner of the data stores may choose what data fields can be presented, and in what fashion, using granular controls to allow, block, redact, or obfuscate.

Users can access Dymium just as they would typically access the data stores directly, using whatever identity and access management (IAM) schema is already in place. Unbeknownst to the user, their query terminates with Dymium, which then reaches out to data stores on the other side via a simple connector.

As the query request is fulfilled, Dymium performs the transformations to the data as specified by the data owner. Unlike other solutions, with Dymium, these transforms are performed on the fly. The source data itself is never exposed to the user; in fact, Dymium never even sees it!

Query results are presented as ephemeral “ghost” databases. While the user can download query results, a ghost database exists only for that session — it is never saved or cached, and Dymium has no visibility to it.