Project isolation
Every external user and agent identifier is transformed into a project-private storage namespace. API-key principals cannot address another project's memory.
A direct view of the isolation, access, deletion, delivery, and operational controls in the current Syntarus Memory platform.
Every external user and agent identifier is transformed into a project-private storage namespace. API-key principals cannot address another project's memory.
Project keys use least-privilege scopes. Short-lived delegated tokens can be bound to one end user and optionally one agent, and parent-key revocation invalidates them immediately.
Writes are accepted asynchronously and return an event identifier. Clients can poll explicit success or failure instead of assuming a memory is immediately searchable.
Customers can export memories or run durable user-deletion jobs. Completion receipts report each affected store and can trigger a signed deletion-complete webhook.
Webhook requests are HMAC-SHA256 signed. Signing secrets are encrypted at rest, and retry attempts are durable, inspectable, and project-isolated.
Readiness monitoring covers the memory worker and primary data stores. The deployed stack uses Postgres, Qdrant, Redis, and Neo4j health checks.
Owners can configure retention, PII handling, credential blocking, and delegated-token limits. Append-only audit events contain identifiers and decisions, never memory text or secrets.
A dedicated deployment package keeps Postgres, Qdrant, Redis, Neo4j, and the API inside the customer's network and exposes only the enterprise memory surface through TLS.
Before production traffic, we agree on the expected request volume, latency target, data-retention need, incident contact, and recovery expectations. A pilot includes integration support, failure-mode review, and a written go/no-go result.
We do not claim certifications we do not yet hold. Syntarus Memory is not currently presented as SOC 2, ISO 27001, HIPAA, or PCI certified. Formal uptime SLA, SSO/SAML, managed-cloud regional residency, and cloud-KMS-backed customer-managed keys still require an explicit enterprise agreement. Customer-hosted deployments provide a stronger ownership boundary, but production use still requires the customer's backup/restore, network-egress, key-rotation, load, and incident-response acceptance tests.
Send vulnerability reports, security questions, or architecture-review requests to [email protected].
Request a technical review ->