Cohere North vs Moterra (2026)

Named integrations reach Google Drive, SharePoint, Slack, Salesforce, Gmail, Outlook and Linear, spanning storage, messaging, CRM, email and project management. The vendor describes these as first-party integrations maintained by Cohere rather than a marketplace of community connectors. The open-ended half is explicit and matters most for an enterprise behind a firewall: North uses the customer's own MCP servers for any custom tool, and Agent Studio documents enhancing agents with custom tools including MCP integration. A bank running North air-gapped needs to reach internal systems no vendor has built a connector for, and MCP is how that happens without waiting on a roadmap. Compass adds a second integration surface through pre-built connectors for retrieval, so systems can serve as knowledge sources as well as action targets.

Read-write connectors across CRM, comms, support, docs, code and data, naming Salesforce, Slack, Teams, SharePoint, Jira and Google Workspace, with permissions inherited.

North Automations, launched around July 2026, is a dedicated orchestration layer. The vendor positions it as moving from isolated task automation to coordinated outcome-driven workflows, with a centralized layer to coordinate diverse agents across an enterprise. Agent-to-agent coordination is named separately on the Agent Studio page. The underlying work is specific: agents automate repetitive tasks, conduct market research, interpret data, and produce documents, tables, charts and slideshows, strengthened by Cohere's acquisition of Ottogrid for market-research automation. Agent-powered workflows are designed around a team's own tools and processes. On control flow, Cohere's announcement says North Automations creates a clear and auditable execution path with loops and branching. Cohere publishes no North product documentation, so how those constructs are built rests on that announcement.

Customers build agents in Dify's visual workflow builder with conditional logic, hosted in their own VPC, combining knowledge bases, MCP tools and workflows.

North Automations runs on a schedule: the announcement lists setting the frequency with scheduled runs among its key features, and its example of a daily customer engagement tracker runs each morning and sends a Slack message for review. North is also a workspace where teams chat with agents, integrated with Slack, Gmail, Outlook, Salesforce, Google Drive and SharePoint, so it sits close to where people already work. The gaps: no webhook or external event trigger is named, and because Cohere publishes no North product documentation, the schedule rests on the vendor's announcement.

Agents run when a user asks in the Cowork and Code apps; no schedule, webhook or event trigger is named.

Grounding is the product's technical core, served by a purpose-built stack rather than a generic retrieval step. Compass is an intelligent search and discovery system with pre-built connectors, document parsing and a managed index, which is a maintained standing structure. Behind it sit Embed for semantic search and Rerank for retrieval precision across documents, tables and code, so the retrieval pipeline is built from components the same company builds and tunes. Two properties lift this above standard retrieval. Every answer returns citations and transparent reasoning chains, so a reader can verify both the source and the path to the conclusion. And the Command family is optimized for grounded generation rather than adapted to it. A third is structural: because North deploys inside the customer's environment, the index over their proprietary documents is built and held within their own perimeter. For the banks, hospitals and government agencies this product targets, grounding on sensitive material is usually where an AI project stops; here the corpus never leaves. Documented connectors reach Google Drive, SharePoint, Slack and Salesforce among others.

Permission-aware SharePoint retrieval over multiple scoped knowledge bases kept in the customer's AWS account, plus a semantic layer for Text-to-SQL.

What Cohere documents is retrieval, not memory. Compass maintains a managed index over the customer's data and North grounds every answer in it with citations, but that is a corpus the customer supplies. Nothing describes an agent retaining conversation context across sessions, carrying a conclusion from one task into the next, or updating what it knows from experience. Agent configuration persists, which is setup rather than accumulated state. The distinction is easy to blur on a product like this because the retrieval is so good: an assistant that always knows your documents can feel like it remembers while holding no state between conversations. Cohere publishes no product documentation for North, so this rests on marketing pages rather than a documentation index. Conversation persistence often ships without being marketed, so this finding could be wrong; a customer-facing user guide would settle it.

No agent-written memory or conversation persistence is described; skills are configuration and the vector stores are retrieval indexes.

North Automations names an approval step: the announcement lists identifying the key moments to loop in colleagues for approval as a governance feature. Plan mode lets a person review and edit the approach before an automation is built, and the vendor advises starting with supervised autonomy and setting policies for agent interactions and oversight. Guardrails and granular roles and permissions sit around that, and agents operate within the organization's guardrails. The gaps: the approval step is described in an announcement rather than product documentation, and nothing says what a guardrail actually enforces. Buyers should ask to see where a run pauses for approval.

Per-user model access, token quotas and device policies constrain use, but no approval step or review queue sits in the run path.

Cohere operates a trust center listing SOC 2 Type II audited annually, with the report available on request under mutual NDA, ISO 27001 for information security management, ISO 42001 for AI management, and the UK government-backed Cyber Essentials standard, plus a documented bug bounty program with published rules of engagement. ISO 42001 is worth naming separately because it certifies the AI management system rather than general information security, and it is unusual. Controls match: granular roles and permissions, agent autonomy policies, full data traceability and audit-ready logs, a multi-jurisdictional Data Processing Addendum, and HIPAA readiness. A name collision to watch: cohere.io is a different company, Caldera Labs Inc. of New York, selling customer-service cobrowsing. It publishes its own security page and its own SOC 2 Type II announcement describing Google Cloud hosting and HITRUST. Those pages do not describe Cohere Inc.; the AI company is cohere.com. A vendor risk aggregator asserts Cohere holds no SOC 2, ISO 27001 or GDPR compliance, which Cohere's own trust center contradicts directly.

Entra ID or Google Workspace sign-in, customer-managed keys and permission-scoped retrieval, but ISO is badged as aligned and the SOC 2 reports are AWS's and Anthropic's.

Several documented properties together give an auditable record. "Full data traceability and audit-ready logs" are stated on the Agent Studio page as the compliance mechanism, a record of what happened rather than a dashboard of how much. Analytics are named alongside guardrails and granular roles as the visibility and control layer of North Automations. The North product page says North connects to existing tools, data and monitoring systems, so the record can leave the platform for the customer's own observability stack. The most distinctive element is transparent reasoning chains returned alongside citations: an employee can see not only which source produced an answer but the path taken to it. That addresses why, not only what. For regulated buyers, North's whole market, the audit record is generated and kept inside their own perimeter because North deploys in their infrastructure, so there is no vendor-side log to subpoena or trust.

Every prompt, response, plugin call and admin action is logged to CloudTrail and a log bucket in the customer's account, with SIEM forwarding and cost tracking.

North is brought to the customer's infrastructure through virtual private cloud, on-premises and air-gapped options, so Cohere itself never sees or touches customer data, and North Automations is documented as deploying securely across any on-prem or cloud environment. This is confirmed on the vendor's own security page. The engineering claim behind it is what makes this practical: North was built to run on as few as two graphics processors, described by the company's co-founder as deploying on a machine in a closet. Air-gapping is common as a promise and rare in practice, because most agent platforms assume network access for model inference; North removes that assumption by bringing the models with it. Model Vault provides dedicated deployment for the model layer specifically. This is the reason regulated buyers evaluate North at all. For a bank that cannot let data leave its firewall, most other capabilities are secondary to this one.

Runs inside the customer's own AWS account or Azure tenant, with customer-held keys and a region the customer chooses; Google Cloud and on-premises on request.

What qualifies as ready to adopt is thin. North for Banking is the strongest item: an industry variant co-built with RBC, a real packaged offering rather than a template, but one vertical rather than a set. Agent Studio provides customizable agents and workflow automations, which is machinery for building rather than assets to take. Compass contributes pre-built connectors, which are integration components rather than agents. So a customer arriving at North gets a capable builder and, if they are a bank, a head start. They do not get a library of ready-made agents to adopt. The public surface is marketing rather than documentation, and a customer-facing agent library could exist behind the sales-led onboarding without appearing publicly. For a product sold through a six-to-sixteen-week enterprise engagement, a template catalog may simply not be public.

Moterra builds an initial set of agents for each customer during onboarding, with 12 built-in capabilities, but publishes no catalog.

The vendor says North lets enterprises "flexibly choose from Cohere's enterprise-specific generative or search models, or any external LLM". The customer chooses which model powers the product, and the choice is not limited to the vendor's own family. That is notable for a model company: it lets its agent platform run on a competitor's model, competing on the platform rather than locking the model in. Within Cohere's own range there is real breadth too: the Command family including Command A Reasoning and Command A+, North Mini Code for agentic coding, Embed for semantic search, and Rerank for retrieval precision, with the vendor documenting which product each model suits.

Every model offered is Anthropic's Claude, served through Bedrock or Azure, with per-user model access but no choice across makers.

Cohere names an SDK directly: enterprises interoperate with their stack using Cohere's "first-party integrations, their MCP for any custom tool, or our SDK to power bespoke agentic platforms". An SDK offered specifically for building bespoke agentic platforms on top of North is a real build surface, not merely a client library for calling models. The North product page adds that it connects to existing tools, data and monitoring systems through flexible APIs and built-in connectors, so the platform is addressable programmatically in both directions. North's MCP support uses the customer's own MCP servers for custom tools, which is North calling out to other tools. What makes North itself callable is the SDK and the APIs. Underneath sits Cohere's broader developer platform, documented as direct API access alongside North, so the engineering surface is mature rather than nominal.

API tokens in the admin console point to an API, but no reference is published; the MCP plugins expose the customer's systems to Claude.

North Automations offers a test-before-publish loop: the announcement lists testing and iterating before publishing to production, versioning to track changes over time, Plan mode to review the approach before building, per-step model choice to balance cost and performance, and analytics on usage and input and output tokens. What is missing is a readable result. No scored test set, judge, metric or comparison of versions on the same inputs is described. Cohere's red teaming and its retrieval benchmarks are run by the vendor, not by the customer, so they do not tell a buyer how their own agents perform.

No evaluation or scoring is described; Moterra tests new Claude models against the customer's setup as a service.

Every action path Cohere documents runs through a programmatic interface: first-party integrations to Google Drive, SharePoint, Slack, Salesforce, Gmail, Outlook and Linear, the customer's own MCP servers for custom tools, Compass connectors for retrieval, and APIs and an SDK. Nothing describes a browser, navigation, clicking, form filling or session control. The near miss is asset creation: agents producing documents, tables, charts and slideshows. Generating a file is not operating an application. North Mini Code, Cohere's agentic coding model, writes and executes code, which is also not computer use. The deployment model makes the absence coherent. A platform built to run air-gapped inside a customer's perimeter often has no external network access at all, so driving external browser sessions would cut against its main design choice. Cohere publishes no public product documentation for North, so this rests on marketing pages and announcements.

Web search and scrape is retrieval; no browser control, navigation or screen interaction is described.