Dedicated instance
Your own application and database establish the customer boundary.
MORPHEUSOS / SECURITY & TRUST
Isolation you can verify.
Every customer has a dedicated application and database. The release pipeline checks customer scoping, and access inside the instance follows the permissions granted for the work.
DEDICATED INSTANCE BOUNDARIES
INSTANCE A / CUSTOMER scoped access
Applicationprivate runtime
Databaseprivate records
ACCESS
DENIED
DENIED
INSTANCE B / CUSTOMER scoped access
Applicationprivate runtime
Databaseprivate records
Each customer keeps its own application, database and memory. Cross-customer database access is denied.
THE REVIEWER’S FIRST PAGE
Clear boundaries.
Visible responsibility.
Scoped access
Workspaces, channels, clients and organisations receive only the access they are granted.
Human approval
Workflows prepare and recommend, then wait at gates a named person passes.
Traceable activity
What ran, what it produced and who approved it are recorded as the work happens.
STATUS AT A GLANCE
Control status and engagement scope.
AreaCurrent status
Australia regionLive Available today.
United States regionPer engagement Provisioned at onboarding.
SOC 2In preparation Controls and evidence are being collected for assessment.
Subprocessor register & DPAIn preparation Published in full before enterprise launch.
Private network, BYOK, pen-test reportPer engagement Agreed for the production tier of an engagement.
01
THE WALL
A dedicated customer boundary.
Each customer’s application and database form a distinct boundary, with permissions and release checks supporting that separation.
Review the isolation controls
Dedicated database
Each customer has an application and database dedicated to its own data.
Denied at the database level
Database permissions enforce the separation between customer systems.
Enforced in the build
The release pipeline fails if a query runs without correct scoping. The check runs on each release.
Permissions inside
Role-based access, workspace separation, per-user credentials. Connections use the credentials and permissions granted to their user.
Second factor on sensitive actions
Deleting a workspace, unmasking personal data or running an erasure each need a fresh one-time code.
Accountable oversight
Admins may review for quality and safety, but personal data is masked by default. Unmasking is logged.
02
PRIVACY ENGINE
Personal data is handled first.
Recognition, redaction, routing and rights act before information moves through the workflow.
Review the privacy controls
Recognises it
Validated recognition of Australian, US and EU identifiers, alongside emails, phone numbers and payment cards.
Redacts it
Always-on log redaction. The audit trail records what kind of data was involved, never the data.
Routes it
Sensitive content reaches only providers under contractual no-training terms — by default, Anthropic.
Answers requests
GDPR, CCPA and Australian Privacy Act tooling, with the legal clock tracked and erasure safe under hold.
03
OWNERSHIP
You own the instance. You own the data.
Regional cells and a clean exit keep ownership and contractual boundaries explicit.
Review ownership and region controls
The instance
Dedicated to you, operated on your behalf.
The data
Your property. We make no claim over it and do not train models on it.
Your region
Australia is live. A United States instance is provisioned per engagement at onboarding.
Clean exit
Exportable. On offboarding the instance and its data are returned or destroyed.
04
GOVERNANCE
Trust is structural.
Evidence, approvals and access boundaries are recorded and checked as the workflow runs.
Review governance controls
Existing systems stay central
Your systems of record remain authoritative. No migration is required.
Scoped access
By workspace, channel, client and organisation — and by contractual boundary.
Human approval modes
Workflows prepare and recommend, then wait at gates a named person passes.
Audit trails
What ran, what it produced and who approved it — recorded as it happens.
Evidence links
Recommendations carry their sources, and name the evidence that is missing.
Connector permissions
Each connection granted explicitly, and withdrawable.
05
ENFORCED IN THE PRODUCT
Read from the control plane.
These mechanisms are settings a reviewer can be shown, read from the live customer-zero admin surface.
Review the control-plane mechanisms
POLICY GATE
Policy checked before action
One PII taxonomy, one gate — every surface consults the policy before it acts. Jurisdiction detector packs are configured per tenant so the applicable enforcement follows that tenant’s policy.
GRANT CEILINGS
Bound to named tools
A channel is granted individual tools — never a whole server. Nothing said inside a channel can widen what it may reach, so instructions arriving in a conversation cannot escalate it.
LOG REDACTION
Always-on redaction
Every log, trace and error line is stripped of credentials and sensitive-tier identifiers — tax file numbers, government IDs, cards, bank identifiers — before it reaches any sink, independent of policy state.
OPERATOR LEDGER
The admins are audited too
Every admin change records itself — who, what, where, when. Oversight queries run with the asker’s permissions, nothing more, audited under their name.
Customer zero, read from the live admin surface. These are the mechanisms behind the claims above — ask to be shown them in a briefing.
06
ENGAGEMENT DETAILS
Confirm the controls for your engagement.
Review the available controls, assurance work and agreed deployment options with the team.
Review qualifications and engagement status
SOC 2 — in preparation
Controls are built to the Trust Services Criteria and evidence is being collected. SOC 2 remains in preparation until an assurance report is issued.
Subprocessor register and DPA — in preparation
On request as finalised, published in full before enterprise launch.
US region — per engagement
A provisioning step at onboarding. Live today is Australia.
Private network, BYOK, pen-test report — per engagement
These production-tier options are agreed and configured for the engagement.
How do you know the isolation still holds?
Because it is checked on every release. The build fails if code attempts a data query without correct customer scoping. The release check provides continuing evidence that the customer-scoping rule is enforced.
Which model providers see our data?
Sensitive content reaches only enterprise providers under contractual no-training terms — by default, Anthropic. Consumer AI tools are blocked unless an administrator makes a deliberate, logged and reversible exception.
What is the current SOC 2 status?
SOC 2 is in preparation: controls are built to the Trust Services Criteria and operating evidence is being collected. Review the controls currently in place and the evidence available for your engagement. Formal assurance remains subject to an issued report.
Can we run in our own region?
Australia is live. A US instance is stood up as a provisioning step at onboarding — a dedicated deployment in the agreed region.