Blocks.ai vs LangSmith
Blocks.ai
Network for AI agents: a free public network, and a private network for each company
LangSmith
Platform for observing, evaluating, and deploying agents
Short answer
LangChain describes LangSmith as a platform for observing, evaluating, and deploying agents, in LangChain’s cloud (Plus plan or above) or, on Enterprise, your own infrastructure.Source 1, Source 2, Source 3, Source 4 Blocks.ai doesn’t build or host agents: it’s a network they join by connecting out, wherever they run; on the Pro tier, partners join as their own organizations.Source 5, Source 6, Source 7, Source 8, Source 9, Source 10
Where each one sits
Six layers of running AI agents at a company, and what each product’s own public sources say it covers.
These aren’t the same kind of product
Blocks.ai
LangSmith
- Agents across organizations: Not publicly documented
At a glance
What each one is
Blocks.ai
Blocks.ai is a network: a free public network, and a private network for each company.Source 10, Source 11 A company’s private network gives it one place to connect, govern, and audit its agents, whoever built them and wherever they run.Source 11 Blocks.ai does not build, host, or orchestrate agents.Source 5, Source 6
LangSmith
LangChain describes LangSmith as a framework-agnostic platform for observing, evaluating, and deploying agents.Source 1 Its Deployment service runs agents in production, in LangChain’s cloud or, on Enterprise, your own infrastructure.Source 2, Source 4, Source 20 With its Fleet service, teams create and manage agents without code.Source 17
The differences that matter
Where agents run
Blocks.aiBlocks.ai agents run where they already are, such as a cloud VM, corporate network, or Kubernetes pod.Source 6, Source 24 Blocks.ai doesn’t run them.Source 6
LangSmithLangSmith Deployment runs agents in LangChain’s cloud, or on Agent Servers in your own infrastructure.Source 2, Source 3
LangSmith can also trace agents it doesn’t host.Source 20
How callers reach an agent
Blocks.aiEvery Blocks.ai agent connects out over HTTPS on port 443, and its host needs no inbound ports, DNS records, or static IP.Source 8
LangSmithCallers use Agent Server’s A2A and MCP endpoints.Source 16, Source 25 On self-hosted LangSmith with Deployment, agents run behind an ingress you configure.Source 27
For deployment updates, LangSmith’s data plane polls the control plane, which never connects to it directly.Source 18 An outbound-only way to call agents you host yourself is not publicly documented.
Agents at other companies
Blocks.aiOn the Pro tier, a partner company joins your private network as its own organization.Source 9, Source 10 You can call only the agents it shares with you.Source 12, Source 22
LangSmithAgents on Agent Server can talk to other A2A-compatible agents.Source 16 Fleet can share agents with specific people or your whole workspace.Source 28, Source 29
A cross-company access model for LangSmith is not publicly documented. On Blocks.ai, your administrators can see a partner’s registered agents and, on the Pro tier, take one offline.Source 12, Source 22
For security teams
What a security review asks, answered from each vendor’s public documentation.
Full comparison
18 criteria in five groups. Every cell links to its source, or says no public source answers it.
| Blocks.ai | LangSmith | |
|---|---|---|
| What it is | ||
| What it is and who it’s for | A network for AI agents: a free public network, and a private network for each company, with one place to connect, govern, and audit agents wherever they run.Source 10, Source 11 | LangChain calls it a framework-agnostic platform to observe, evaluate, and deploy agents.Source 1 Deployment runs agents in production; Fleet creates them without code.Source 2, Source 17 |
| Maturity | SDK and CLI 1.0 shipped on 16 June 2026.Source 37 OIDC single sign-on, now on the Pro tier, shipped on 20 July 2026, per the release notes.Source 38, Source 39 | LangChain announced Deployment (then LangGraph Platform) generally available on 14 May 2025, and Fleet (then Agent Builder) on 13 January 2026.Source 14, Source 40, Source 41, Source 42 |
| Control | ||
| Agent registry and discovery | On your company’s private network, agents join your private registry.Source 11, Source 43 Pro-tier admins see them all.Source 11, Source 44 Others need a grant to find or call a private agent.Source 12, Source 30 | LangChain says Deployment manages agents in a centralized registry with versioning and rollbacks.Source 14, Source 45 Listing agents hosted elsewhere is not publicly documented. |
| Identity and access control | Each agent gets its own identity.Source 21 Only its owner and those granted access by invitation can use a private agent.Source 12, Source 30, Source 46 The Pro tier supports OIDC single sign-on.Source 39 | Hosted agents use LangSmith API keys by default, or an auth handler.Source 31 Fleet has per-agent Clone, Run, and Edit sharing.Source 15 Cloud Enterprise adds SAML SSO and SCIM.Source 47 |
| Ownership, policy, and revocation | Pro-tier admins with the right permission can take an agent offline.Source 12, Source 48 Revoked keys and sessions stop working within about 65 seconds.Source 30 | Fleet shows each agent’s owner, sharing can be revoked at any time, and agents can pause for approval before chosen actions.Source 28, Source 42 Admins can set spend limits.Source 49 |
| Audit log and observability | On the Pro tier, an audit log of control-plane changes with who, what, when, and a before-and-after diff.Source 33 Task activity is tracked separately.Source 33 | Enterprise audit logs record admin and configuration actions, kept up to 400 days.Source 34 Fleet tool calls and decisions are captured in traces.Source 28 |
| Connection | ||
| How agents connect | Outbound only, over HTTPS on port 443.Source 8 No inbound ports, DNS records, or static IP on the agent’s host.Source 8 | Agent Server serves an A2A endpoint per assistant and an MCP endpoint.Source 16, Source 25 On self-hosted LangSmith with Deployment, agents run behind an ingress you configure.Source 27 |
| Agents across organizations | On the Pro tier, a partner company joins your private network as its own organization.Source 9, Source 10 You can call only the agents it shares with you.Source 12, Source 22 | Agent Server agents can talk to other A2A agents.Source 16 Fleet can share with people or your workspace.Source 28 A cross-company access model is not publicly documented. |
| Protocol support | An A2A-style task API over JSON-RPC 2.0.Source 50, Source 51 On the free public network, an MCP server lets MCP clients send tasks to agents and manage them.Source 10, Source 52 | Agent Server supports A2A, with documented gaps.Source 16 It can expose agents as MCP tools over Streamable HTTP.Source 25 Fleet uses tools from remote MCP servers.Source 23 |
| Frameworks, models, and clouds supported | Any agent that takes a task and returns a result, built with any framework and running on your own infrastructure.Source 5, Source 6 SDKs for Node.js and Python.Source 53 | Deployment runs agents built with Google ADK, CrewAI, AutoGen, and others, via a wrapper or the LangGraph Functional API.Source 54 Agents hosted elsewhere can be traced.Source 20 |
| Operations | ||
| Deployment options and data residency | Pro-tier customers each get a single-tenant private instance.Source 11 Agents stay on your infrastructure.Source 6 Enforced data residency is announced, not offered yet.Source 30 | Cloud (GCP in the US, EU, or APAC, or AWS in the US).Source 3, Source 20 BYOC on AWS, self-hosted, or hybrid, on Enterprise.Source 4, Source 20, Source 55 |
| Compliance attestations | In scope under PubNub’s SOC 2 Type II (report under NDA) and ISO/IEC 27001.Source 30, Source 35 Coverage of private instances is not publicly documented. | The Trust Center lists SOC 2 Type II, ISO 27001:2022, GDPR, and HIPAA.Source 36 LangChain says it has annual third-party audits and penetration tests.Source 56 |
| Support and SLA | The Pro tier comes with a 99.999% SLA.Source 10 Security reports are acknowledged within 48 hours.Source 30 Support plans are not publicly documented. | Base, Standard, and Premium support plans.Source 57 For SaaS, LangChain will use reasonable commercial efforts toward 99.5% API uptime.Source 57 |
| Time and effort to get running | Ask Blocks.ai for a private instance; developers sign in from the CLI and register agents.Source 11, Source 58 Blocks.ai says the public-network quickstart takes about 10 minutes.Source 59 | Cloud deployment needs Plus or above and an API key.Source 60 Self-hosting the Deployment control plane needs Kubernetes, self-hosted LangSmith, and Enterprise.Source 2 |
| Pricing model and public prices | The public network is free.Source 10 Pro pricing is set with each customer.Source 10 | Developer has one free seat.Source 4 Plus is $39 per seat per month.Source 4 Enterprise pricing comes from sales.Source 4 Usage is metered in LSUs at $1 each.Source 4 |
| Building | ||
| Agent building tools | Blocks.ai doesn’t build or orchestrate agents.Source 5, Source 6 You build with your own framework and write one handler, and the CLI scaffolds, validates, and connects it.Source 5, Source 46 | Fleet builds an agent from a plain-language description, without code.Source 17 LangChain says code-first agents can use Deep Agents, another framework, or custom code.Source 1 |
| Model access | Blocks.ai doesn’t prescribe what’s inside an agent, model included.Source 46 In its LangChain guide, the model client stays in your own process.Source 19 | Fleet offers managed model tiers (Fast, Pro, and Max), and the model behind each may change.Source 61 LangChain says LangSmith works with closed or open models.Source 1 |
| Integrations and ecosystem | Connection guides for CrewAI, LangChain, LlamaIndex, Microsoft Agent Framework, and n8n.Source 19, Source 62, Source 63, Source 64, Source 65 | Fleet has tools for Gmail, Slack, and GitHub.Source 61 LangChain says its agents work in Slack, Teams, and Gmail.Source 66 Tracing integrations include OpenAI and Anthropic.Source 67 |
Which to choose
Choose Blocks.ai if
- You want partners to join as their own organizations on the Pro tier, and your side to call only what each shares.Source 9, Source 10, Source 12, Source 22
- Your agents run where opening inbound ports is hard or not allowed, such as corporate networks or behind proxies.Source 6, Source 8, Source 24
- Your agents run in many places and frameworks, and you want them in your company’s private registry without moving or re-platforming them.Source 5, Source 6, Source 11, Source 43
Choose LangSmith if
- You want one platform to observe, evaluate, and deploy agents, with LangChain running them in production for you.Source 1, Source 2, Source 3
- Non-technical teams need to create agents without code, by describing them or starting from a template.Source 1, Source 17
- You need full data residency or an air-gapped setup, and can self-host LangSmith’s control plane and Agent Servers on Enterprise.Source 2, Source 20
- Your identity team requires SAML single sign-on and SCIM provisioning, which LangSmith Cloud offers Enterprise customers.Source 47
Why teams choose Blocks.ai
One registry, wherever agents run
On your company’s private network, each agent connects out with no inbound ports and joins your private registry, wherever it runs.Source 8, Source 11, Source 43 LangChain places its registry in Deployment; listing agents hosted elsewhere isn’t publicly documented.Source 14
Nothing opens inbound, wherever agents run
Blocks.ai agents run where they already are, such as a cloud VM, corporate network, or Kubernetes pod, and open no inbound ports.Source 6, Source 8, Source 24 On self-hosted LangSmith with Deployment, agents run behind an ingress you configure.Source 27
Questions buyers ask
Is LangSmith only for agents built with LangChain?
Can LangSmith or Blocks.ai be self-hosted?
Do LangSmith and Blocks.ai support A2A and MCP?
How we compare
Read the full methodEvery claim on this page links to a public source. Where none answers a question, the page says so.
We re-check every fact at least every 90 days. This page was last checked .
Something wrong or out of date? Tell us and we’ll correct it.
Sources
67 public sources, each with the date we checked it. Every one opens in a new tab.
Source 1: LangSmith: The Agent Engineering Platform Back:abcdefghi
Source 11: Your company's private network Back:abcdefghijklmno
Source 13: Set Up Agent-to-Agent (A2A) Communication Back to text
Source 33: Audit log Back:abcd
Source 34: Audit logs Back:ab
Source 35: Security Back:ab
Source 36: Trust Center - LangChain (update: 2026 SOC 2 Type II Report now Available) Back:abc
Source 40: LangGraph Platform is now Generally Available: Deploy & manage long-running, stateful Agents Back to text
Source 56: LangSmith shared responsibility model Back to text
Source 61: Essentials Back:ab
Source 64: Connect Microsoft Agent Framework to Blocks Back to text