Cohere’s October 5, 2026 product post introduces North 2 as a full-stack agentic platform built to end the usual tradeoff between security, intelligence, cost, and control. The Toronto-based company, as publicly reported in Canadian coverage including The Globe and Mail, frames the release around production deployments in finance, healthcare, telecom, manufacturing, energy, and the public sector. For Alberta operators who need data kept on site and a hard cap on agent spend, the primary post is worth reading for what it does and does not claim.
What Cohere says North 2 adds
The primary source is Cohere’s own post. It describes a redesigned orchestration system for multi-step automations and agents, and it lists core features: skills as reusable capabilities; libraries as shared knowledge; memory so agents keep context across sessions; applications for decks, dashboards, documents, and lightweight apps from natural language; automations with templates, a drag-and-drop builder, and monitoring; and connectors including Slack, SharePoint, OneDrive, Outlook, Exchange, Jira, Linear, Notion, and GitHub, with additional financial-data connectors planned. Guardrails and autonomy policies with human oversight are part of the security section. The post does not publish a dollar price.
“That's important not only for strengthening how we defend Bell and our customers, but for helping Canadian businesses and governments adopt agentic AI securely and with confidence.”Jawed Ahmad, Chief Technology and AI Officer, Bell Cyber — quoted in Cohere, Introducing North 2, October 5, 2026
Bell Cyber’s quote is the clearest Canada angle on the primary page. SiliconANGLE’s October 5, 2026 secondary report covers the rebuilt orchestration and token spending caps, and notes North has been generally available since August 2025. Treat SiliconANGLE as secondary context. Attribute product claims to Cohere’s post.
Security, certifications, and cost governance
Cohere says North deploys privately on-prem, in the cloud, or fully air-gapped, and that it exceeds global security standards with SOC 2 Type 2, ISO 27001, and ISO 42001 certifications. North Admin, per the post, configures visibility down to the user and agent level, integrates with existing identity systems, and supports flow control by defining consumption tiers based on requests and token rates for users and groups. Before limits are set, alert thresholds can notify teams. Org-wide caps are listed alongside rate limits and user quotas. Efficient token consumption on NVIDIA hardware with Cohere models is mentioned as a collaboration point; that is Cohere’s claim, not an independent Alberta benchmark.
| Area | What the primary lists |
|---|---|
| Deployment | Self-hosted, VPC, hybrid, on-premises; also fully air-gapped |
| Certifications | SOC 2 Type 2, ISO 27001, ISO 42001 |
| North Admin | Roles/permissions, per-user and per-agent visibility, token spend and limits, alerts, consumption tiers, rate limits, user quotas, org-wide caps |
| Pricing | No public list price in the post; see cohere.com/pricing |
What Alberta operators should decide now (our advice)
What follows is our advice, not Cohere’s. Energy, utilities, manufacturing, municipal, and public-sector operators in Alberta who need data kept on site should start from residency and spend control, not from a feature checklist. Ask whether the pilot can run on-prem or air-gapped with the connectors you actually use. Set an org-wide token cap and per-agent limits before anyone shares a workflow template. Prefer model portability so a Cohere model today can be swapped later without rewriting the process. For a contained private path, private AI security work should define the data boundary first. An AI consulting Alberta engagement is a better first step than a blanket platform swap across every department.