Trust & security

Built to be read by your security team.

DataConverse is a managed service that connects inward to the databases you nominate, from addresses you whitelist, using a read-only credential you issue. Here is exactly what that means, in writing.

Read-only accessWhitelisted IPsSchema indexed, not dataIsolated index per databaseSLA-backed support
Connection

How the connection is made.

You whitelist our addresses

We connect from a fixed set of service IP addresses. Anything else is refused at your firewall, by you.

You issue a read-only credential

Every database is registered with a read-only credential that you create. The product does not issue writes.

We index the schema, not the data

Extraction reads metadata only: tables, columns, types, keys and relationships. Your rows stay in your database.

Controls

Commitments your reviewers can check.

Read-only, always

Every database is connected with a read-only credential. The product does not issue writes, and a read-only role means it cannot, whatever happens.

We index your schema, not your data

Extraction reads metadata only: tables, columns, types, keys and relationships. Your rows are never copied into our index.

Isolated per database

Each database gets its own vector index. Nothing is pooled across your databases, and nothing is shared between customers.

Connections from named addresses

We connect from a fixed set of service IP addresses that you whitelist. Anything else is refused at your firewall, by you.

Every query is visible and checked

Generated SQL is sanitised and validated for execution safety before it runs, and it is shown to the person who asked, every time.

Supported to an SLA

After go-live the deployment moves to active production support, with a service level rather than best effort.

See it answer questions on your own data.