Docs / Integrations

Integrations

TraceMem works with the systems you already run. It takes identity from your provider, reaches your data through connectors that hold the credentials, sends approvals to where your approvers already work, and routes model calls to the providers you choose.
Identity
Your OIDC provider
Data sources
49 named, plus any API or MCP server
Approvals
Chat, email, webhooks and your ERP
Models
Commercial and self-hosted

Identity providers

Actors, agents and approvers are verified against your own provider, and people sign in to the dashboard with it. TraceMem issues no identities of its own.
  • Microsoft Entra ID
  • Okta
  • Google Workspace
  • Oracle IDCS
  • Keycloak
  • IBM Security Verify
  • Ping Identity
  • OneLogin
  • Any OIDC providerthrough the generic type

Groups sync from Microsoft Entra ID, Okta, Keycloak and Google Workspace, so approver pools and policies use the real groups in your directory rather than names typed by hand.

Data sources

Connectors are configured in TraceMem and hold the credentials. Agents see the data products and capabilities published on top of them, never the connector itself. Each deployment enables the connectors for the systems it uses.

Databases

  • PostgreSQL
  • MySQL
  • MariaDB
  • MongoDB
  • Microsoft SQL Server
  • CockroachDB
  • TiDB
  • TimescaleDB
  • SAP HANA
  • EdgeDB
  • Apache Cassandra
  • Azure Cosmos DB
  • Amazon DynamoDB
  • Neo4j
  • Redis
  • InfluxDB
  • Prometheus

Warehouses and analytics

  • Snowflake
  • Google BigQuery
  • Databricks
  • Amazon Redshift
  • Azure Synapse
  • ClickHouse
  • Apache Druid
  • Apache Pinot
  • Apache Iceberg

Search and vector

  • Elasticsearch
  • OpenSearch
  • Apache Solr
  • Pinecone
  • Weaviate
  • Milvus
  • Chroma

Object storage

  • Amazon S3
  • Google Cloud Storage
  • Azure Blob Storage
  • MinIO

Business apps

  • Salesforce
  • HubSpot
  • Stripe
  • Zendesk
  • PagerDuty

Cloud platforms

  • AWS
  • Azure
  • Google Cloud

Developer tools

  • GitHub
  • GitLab
  • Jira
  • Linear

Anything else

Any REST API

Any HTTP endpoint, with the authentication it expects.

  • API key
  • Bearer token
  • Basic
  • OAuth2

Any MCP server

Tools, resources and prompts from an existing MCP server, reached through TraceMem.

  • Tool calls
  • Resource reads
  • Prompt fetches

Core banking, EHR, policy administration and industrial systems connect the same way, through the API or MCP server they already expose.

Approval channels

An exception reaches a named approver wherever they already work, and every exception also has a hosted page. It resolves exactly once, whichever channel answers first.
  • Slack
  • Microsoft Teams
  • Email
  • WebhooksSigned with HMAC-SHA256
  • Hosted pageFor every exception

ERPs

  • SAP S/4HANAAnswered in the ERP
  • WorkdayAnswered in the ERP
  • Dynamics 365Answered in the ERP
  • Oracle NetSuiteAnswered in the ERP
  • Oracle FusionIn the ERP, with the Oracle Integration Cloud sample
  • OdooIn the ERP, with the bundled addon
  • CoupaAnswered on the hosted page
  • SAP AribaAnswered on the hosted page
  • Sage IntacctAnswered on the hosted page

Models

Agents never call a model provider directly. The gateway verifies identity, applies PII policy and evaluates the model gate, then calls the provider with credentials the agent never holds.
  • Anthropic
  • OpenAI
  • Azure OpenAI
  • vLLM
  • Ollama
  • Any OpenAI-compatible serverfor models you host
Client APISupported
Anthropic MessagesExisting Anthropic clients and coding agents point their base URL at TraceMem. Streaming supported.
OpenAI Chat CompletionsExisting OpenAI clients point their base URL at TraceMem. Streaming supported.

Either client API reaches any configured provider, so agents move between providers without code changes. More on connecting clients in SDKs and APIs.

Agent platforms

TraceMem connects to the platforms your agents are built and hosted on, and discovers the agents registered there.
  • Amazon Bedrock
  • Google Vertex AI
  • Microsoft Foundry
  • Copilot Studio
  • Salesforce Agentforce
  • ServiceNow
  • LangChain and LangGraph
  • CrewAI
  • Temporal
  • Intercom
  • Regal AI

Logs, audit and export

Your logging and security tooling reads what TraceMem writes, through the collectors you already run.

Service logs

Structured JSON or text, to standard output, standard error or a file, for whatever collector you already run.

Audit log

The trace store writes its audit events as JSON Lines, ready to forward to your SIEM.

Trace export

A decision exports as tracemem.trace.v3, carrying the hashes anyone you hand it to needs to verify it.