Trust · Read-only database connections
Can the platform read our database without being able to change it?
A live read-only connection exists for PostgreSQL databases and has been tested locally on disposable databases. It is not offered for other engines, and it has not been proved on a deployed environment.
No certification, audit or independent assessment is held. Each statement below shows how sure the project is of it.
What exists, and how sure we are
- Tested locallyThe connection works with PostgreSQL databases only.Recorded in the data access assessment.
- Tested locallyBefore each use, the session is proved read-only against the live database: a read-only transaction, a restricted account, no writable table and no CREATE right in the allowed schemas.Recorded in the data access assessment.
- Tested locallyThe credential is kept in an encrypted envelope bound to the organisation, the connection and its version.Recorded in the data access assessment.
- Tested locallyQueries are fixed templates, such as a catalogue read or the monthly sum of one approved column. No query is written by a model anywhere.Recorded in the data access assessment.
- Tested locallyA connection can be tested, revoked (which deletes the secret) and rotated.Recorded in the data access assessment.
- Not in placeOther database engines are not offered, and neither are connectors to other software services in this form.Recorded in the data access assessment.
- Not establishedThe connection has not been proved on a deployed environment.Recorded in the data access assessment.
See it in an example
Simulation. A scripted example on fictional data. The wording is scripted and no model is called; the figures are computed from what you decide, and a person’s approval covers exactly what you decided.
Check a database connection before it is connected
- What happened
- The data team at Northfield Utilities (fictional) wants to connect a reporting replica for read-only discovery, and the administrator is reviewing it first.
- The question
- Is each protection the connection depends on in place, and what is missing? Asked by: Database administrator at a customer (fictional).
Check a database connection before it is connectedAttach evidence for a missing item, or confirm that a stale one still applies. The completeness is recomputed from what is actually held.Open
Attach evidence for a missing item, or confirm that a stale one still applies. The completeness is recomputed from what is actually held.
Resolve what is missing or out of date. Evidence counts only when it is attached, or when its owner confirms it is current; the sign-off needs the stated completeness.
55% complete · 90% needed
Database account
- A dedicated account created for the connection PresentAccount discovery_ro on the replica
- The account can read only the schemas named in the approval StaleLast checked before two schemas were added
- No table is writable by the account PresentThe grants listing shows read-only on every table
Network
- The database is reached on a public address with its certificate checked MissingThe replica is on a private address
- The platform's addresses are on the database's allow-list MissingNo allow-list entry yet
Session
- The session is read-only, with no CREATE right in the allowed schemas PresentProved by the platform's own check before each use
The connection is 55% ready; connecting needs 90%.
3 item(s) are open: The account can read only the schemas named in the approval; The database is reached on a public address with its certificate checked; The platform's addresses are on the database's allow-list [S1].
The platform proves the read-only session itself before every use, but it cannot make a private database reachable, or choose which schemas a customer exposes [S2].
Relies on: S1 · Connection request and the account's grants listing (fictional)S2 · Connection design note (fictional)
The customer's database administrator decides. Approving records that the connection may be created, with the evidence shown. It does not create the connection, and a connection can be revoked at any time.
Not ready. Evidence is 55% complete; the sign-off needs 90%.
Not done here. It does not connect to any real database, and it never runs a query written by a model: queries are fixed templates.
What a reviewer can have, and what not yet
- We can hand overThe description of the connection's checks and the tests that exercise them on disposable databases.
- We cannot yetA demonstration against a customer's own database, support for other engines, and proof on a deployed environment.
The capabilities behind this
- Understand a database, read onlyBusiness data lives in systems whose structure only a few people understand.
- The ways your information can reach the platformOrganisations differ in what they will share, with whom, and how.
The other nine
- Customer-controlled accessAccess by organisation, role and location, decided on the server, and what stops when it is withdrawn.
- Uploaded dataLimits, what is read and what is not, and the checks that are not done.
- AI provider disclosuresWhich features can send content outside the platform, what they may send, and what has not been established.
- Encryption and access controlsWhat protects sign-in, sessions and secrets, and the controls that only a live inspection can settle.
- Audit evidenceA tamper-evident decision record, what it proves, and what it cannot.
- Human approvalsWhat an assistant may draft or propose, what it refuses, and how a person's decision is recorded.
- Data retention and deletionWhat can be deleted now, what must wait, what is kept by design, and what is not finished.
- Customer-hosted and dedicated deploymentUpload, read-only connection, natural-language questions, a customer-hosted connector and a dedicated environment: what exists.
- Pilot security requirementsThe twenty-item gate, what it counts, and what is open.