ClearPoint Logic
Get early access
The Platform

Four products. One trust fabric.

ClearPoint Logic is built in layers. Anchor at the bottom, the trust fabric that signs every artifact. Agent Core in the middle, where agents actually run, across the major frameworks. The five product surfaces on top, the ones your team actually touches.

Get early access
Architecture

How the platform is layered.

The same architecture diagram our engineers walk customers through on day one. Every piece below is one they can take you through in depth.
01SurfacesThe four products customers interact with
Studio
Build
Meridian
Govern
Helm
Operate
Periscope
Measure
02Trust fabricIdentity, policy, and signed evidence
Anchor
Trust fabric
Cert. Standard
Open spec
AI BOM
Per-artifact
Agent Passport
Identity
Signed Evidence
Per-run
03Agent runtimeWhere agents run, across frameworks
Agent Core
Agent runtime
Framework
ADK Go
Framework
LangChain
Framework
Anthropic SDK
Framework
Microsoft AF
04Agent codeSigned packages that load into Agent Core
Layer 02 · Anchor

The trust fabric.

Anchor is the layer everything in the platform is signed against. It ties people, agents, models, prompts, tools, datasets, and runs together into a single signed record, auditable end-to-end, exportable to your evidence system.

Certification Standard
An open spec for what “governed” means at the artifact level. Every claim points to it.
AI Bill of Materials
A signed manifest per agent: every model, prompt, tool, dataset, dependency, and version.
Agent Passport
A vendor-neutral identity record. The same passport works on Microsoft, Google, custom, BYOA.
Signed Evidence
Every run produces a signed trace - inputs, decisions, approvals, outputs - retained per policy.
AgentPassportAI BOMModelToolRunOperatorDataset
CoreIdentitySpecificationEvidence
Frameworks (pluggable)
ADK Go
LangChain
Anthropic SDK
MS Agent FW
Agent Core runtime
Lifecycle
deploy · canary · rollback
Approvals
role · dual · reversible
Audit
signed traces · streaming
Memory layer
Cloud SQL · pgvector · tenant-partitioned
Kill switches
agent · tool · tenant
Anchored to Anchoridentity · evidence
Layer 03 · Agent Core

Where agents run.

Agent Core runs your agents, whichever framework they were written in. ADK Go, LangChain, Anthropic Agent SDK, Microsoft Agent Framework, all of them share the same identity, lifecycle, approvals, evidence, and memory.

Multi-framework runtime
Run agents written for ADK Go, LangChain, Anthropic SDK, or Microsoft AF - same lifecycle, same telemetry.
Lifecycle management
Versioning, blue/green, canary, rollback. Promotion is a policy decision, not a deploy.
Approval routing
Human-in-the-loop checkpoints with role-based routing, dual control, and reversible actions.
Audit pipeline
Every tool call, prompt, and decision streamed as signed traces - retained per policy.
Memory layer
Cloud SQL with pgvector, tenant-partitioned. Per-agent retention and PII redaction at ingest.
Kill switches
Per-agent, per-tool, per-tenant pause and revoke - enforced at the runtime, not by configuration.
Layer 04 · CPL Agents

The agent code layer.

CPL Agents are the actual agent implementations, code, prompts, tool bindings, and AI BOM. They’re published as signed packages from Studio, certified against the Anchor standard, and load at runtime into Agent Core or a customer-deployed Meridian instance.

Multi-framework: an agent can be authored in ADK Go, LangChain, Anthropic SDK, or Microsoft Agent Framework. Same publishing pipeline, same passport, same evidence. The framework is an implementation detail; the contract with the platform is not.

signed packagesAI BOM includedframework-agnosticreproducible buildsreversible deploy
[email protected] · package.json
{
  "name": "invoice-triage",
  "version": "1.4.0",
  "framework": "anthropic-sdk",
  "passport": "cpl:passport:8f2a91c4",
  "bom": {
    "models":   ["claude-3-5-sonnet@20251022"],
    "tools":    ["sap.lookup", "erp.write", "pii.redact"],
    "datasets": ["finops.invoices.v3"],
    "prompts":  ["sha256:a4f2…"]
  },
  "scopes":     ["read:invoices", "write:erp"],
  "policy":     "envelope://acme/finance/tier-1",
  "signature":  "anchor:sig:rsa256:c7d1…"
}
Build
Studio · reproducible
Deploy
Agent Core · Meridian
Cross-vendor by design

Govern across vendors. Not just one ecosystem.

Vendor governance products only see their own ecosystem, and they prefer their own agents. Meridian is independent: one identity, one rulebook, one evidence layer for the agents you buy, build, and host, across the clouds and tools they already run on.

Ecosystems and tools we connect to
Microsoft
Google
AWS
Salesforce, ServiceNow, and MCP/A2A are live today, with more on the expansion roadmap.
One passport · one policy envelope · one evidence layer
How we're built

Independent for you. Opinionated for us.

Your agents stay independent: we govern across AWS, GCP, Azure, and the agents you build and bring, and route across model families in the request path. How we build ClearPoint is our business, and we made some good calls.

Built on Google Cloud and AWS
Our cloud · runtime

Our own stack runs on Google Cloud and AWS, with Agent Core on the control plane and ADK Go as a first-class runtime path. That's how we run. It's not a cloud we make you adopt.

  • Google Cloud and AWS control plane
  • ADK Go runtime in Agent Core
  • Postgres + pgvector memory
  • Azure governed as a peer
Anthropic Partner
Reasoning · MAP · network

Claude is the primary reasoning model for CPL Agents. We integrate with the Managed Agent Platform and align with the Anthropic Partner Network for distribution and reference patterns.

  • Claude as primary reasoning
  • Managed Agent Platform integration
  • Anthropic Partner Network alignment
  • Anthropic Agent SDK runtime support

Want to go deeper?

See how the platform fits together, or get in touch for a technical walkthrough of the layers.

Get early accessMeet Meridian