Skip to main content
Star2,000

Security and data boundaries

This page summarizes documented controls in MemoraX Code. Enterprise terms are agreed separately.

Data flow

01

Local client

A supported coding agent produces workspace conversations and user instructions.

02

Local selection

The integration selects retrieval or write-back content according to configuration and applies documented local filtering.

03

Network request

The query, selected content, and scope identity are sent to the configured MemoraX service.

04

Memory use

The service returns relevant memories, which the local client uses in later tasks according to configuration.

Currently documented controls

Controls documented for the current MemoraX Code release.

Credential boundary

The API key is written to private configuration, with a connection record stored by the current user's platform credential backend.

Retrieval and write-back switches

Automatic retrieval and automatic write-back can be configured separately; explicit Search and Add actions follow user input.

Local redaction

Automatic write-back includes best-effort sensitive-pattern replacement, but the public documentation explicitly says this is not complete DLP.

Workspace scope

Repository identity and authorization results constrain workspace memories, with conflicting states failing closed.

Local diagnostics

Local traces may contain prompts, responses, and paths; the public version has no trace uploader.

Configuration transparency

Configuration precedence, storage locations, client selection, and reload behavior are documented publicly.

This page does not claim SOC 2, ISO 27001, or any other certification that has not been publicly verified. Public MemoraX Code security documentation is not an audit report for the entire platform or a particular enterprise deployment.

Source documentation