Trust · Customer-hosted and dedicated deployment
Can it run where we need it, and connect the way we need?
Five ways of bringing data to the platform were assessed. Two exist and are tested locally, one is built but deliberately not connected, and two do not exist yet. The page says which.
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 locallySecure upload exists and is tested locally.Recorded in the data access assessment.
- Tested locallyA governed read-only database connection exists for PostgreSQL and is tested locally.Recorded in the data access assessment.
- Reviewed in codeAsking questions of already-authorised sources exists as tested code and is deliberately not connected to a customer screen.Recorded in the data access assessment.
- Not in placeA connector that runs inside a customer's network and only calls out does not exist.Recorded in the data access assessment.
- Not in placeA separate environment for one customer does not exist: no per-customer deployment mechanism was found.Recorded in the data access assessment.
- Reviewed in codeThe platform has its own cloud set-up and a registry of regional placement and residency.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.
Answer a deployment question with only what exists
- What happened
- A prospective customer, Stonehaven Water (fictional), asks whether it can keep its data inside its own network and whether the platform can run in a dedicated environment.
- The question
- Which statements about deployment and connection can the reply contain because the project's records support them? Asked by: Sales engineer (fictional).
Answer a deployment question with only what existsChoose the statements for the reply. A statement the records do not support is refused; an estimate is labelled as one.Open
Choose the statements for the reply. A statement the records do not support is refused; an estimate is labelled as one.
Choose which statements go into the brief. A statement with no source is refused; each one you include carries its sources with it.
Reply to Stonehaven Water: deployment and connection
Choose the statements to include. Each one carries its sources into the brief.
0 of 6 statements included · 2 held back for lack of a source.
0 statements are ready with a source; 2 were left out because the records show nothing.
The reply says what exists and where it has been shown [S1][S2]. A connector inside the customer's network and a dedicated environment do not exist, so the reply says they are not available; it does not describe them as plans.
0 statement(s) are labelled as estimates.
Relies on: S1 · The project's assessment of ways to bring data to the platformS2 · The platform's regional placement and residency registry
The sales engineer with the head of security decides. Approving releases these statements as the factual basis of the reply. It does not promise any capability the records do not show.
Not ready. Choose at least one supported statement for the brief first.
Not done here. It does not describe unbuilt options as available or as on the way: where nothing exists, the reply says nothing exists.
What a reviewer can have, and what not yet
- We can hand overThe assessment of the five ways of bringing data to the platform, with the status of each.
- We cannot yetA customer-hosted connector, a dedicated environment, and proof of upload and read-only connection on a deployed system.
The capabilities behind this
- The ways your information can reach the platformOrganisations differ in what they will share, with whom, and how.
- Retention, holds and where work is processedRecords are kept too long or deleted too soon, and nobody can show why.
The other nine
- Customer-controlled accessAccess by organisation, role and location, decided on the server, and what stops when it is withdrawn.
- Read-only database connectionsWhat a read-only connection proves before every use, what it cannot do, and what a customer's administrator should check first.
- 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.
- Pilot security requirementsThe twenty-item gate, what it counts, and what is open.