Blocks

Executive Summary

Blocks is a workflow-integration platform that brings coding agents into the tools teams already use — GitHub, GitLab, Bitbucket, Slack, and Linear. Rather than building its own agent, Blocks orchestrates existing ones (Claude Code, Codex, OpenCode, Kimi Code, and more) and lets teams invoke them via simple @mentions. Since this profile's original publication (February 2026), Blocks has shipped event-driven automations, automated PR review, a REST API, and enterprise features (SSO, audit logging, RBAC, self-hosting), and claims 800k+ tasks executed. ^{[1] [2]} It remains free to try, with no published pricing as of June 2026.

---

Product Overview

Blocks positions itself as a workflow-first agent platform — rather than replacing your dev tools, it embeds coding agents inside them. Mention @blocks in a GitHub issue, Slack thread, or Linear ticket, and a coding agent of your choice picks up the task. ^[3]

The key differentiator is agent choice: teams aren't locked to a single AI. Claude Code handles most tasks well, Codex brings deep reasoning, OpenCode offers privacy-focused open-source, Kimi Code adds a low-cost option, and Sisyphus provides multi-agent orchestration for complex workflows.

The product now spans "three levels of AI-native" work: ad-hoc @mention sessions, automated PR review with custom instructions, and event-driven automations triggered by CI failures, Slack alerts, or new tickets. ^{[1] [4]}

Key Capabilities

Product Surfaces / Editions

---

Technical Architecture

Blocks runs agents in serverless remote environments — no infrastructure to manage. When invoked via @mention, Blocks:

1. Detects the context (repo, issue, PR, thread)
2. Spins up the selected coding agent in an isolated environment
3. Provides real-time progress updates
4. Delivers results (PRs, comments, answers) back to the source tool

Key Technical Details

---

Strengths

• Workflow-native — Meets teams where they work (GitHub, GitLab, Slack, Linear) instead of adding another tool
• Agent-agnostic — Choose the best agent per task; not locked to one provider
• Low friction — @mention interface requires zero context-switching
• Automations shipped — Event-driven agent runs (CI failures, alerts, tickets) and automatic PR review closed an earlier feature gap ^[4]
• Enterprise-ready claims — SSO, audit logging, RBAC, Zero Data Retention, and self-hosting now advertised ^[3]
• Multi-repo support — Agents understand cross-repository context
• Custom SDK — Build custom agents with Python, smolagents, and LiteLLM
• BYOS (Bring Your Own Subscription) — Uses existing Claude/Codex subscriptions
• Rapid shipping cadence — Frequent point releases (GitLab support, REST API, PR panel, new models) through mid-2026 ^[2]

---

Cautions

• Pricing opacity — Site offers "Try Blocks free" but publishes no pricing page (the /pricing URL returned 404 as of June 11, 2026); cost at scale is unknowable upfront ^[1]
• No local development — Cloud-only, no CLI or local agent support
• Limited visibility — No disclosed funding, team size, or named customers; the homepage's "374 active sessions at Acme Corp" is a mock, and traction claims (800k+ tasks, 99.99% uptime) are self-reported and unaudited ^[1]
• Near-zero public footprint — No Hacker News stories or comments mention blocks.team as of June 2026, and broader community discussion is scarce, making third-party validation difficult ^[5]
• Compliance certifications unstated — Enterprise features are advertised, but no SOC 2 or ISO certification is documented
• Privacy details sparse — Zero Data Retention is offered, but "no training" policy details remain thin

---

What Developers Say

Public developer commentary on Blocks is essentially nonexistent as of June 2026. A Hacker News search for blocks.team returns zero stories or comments ^[5], and outside the company's own launch post on r/Linear ^[6], no substantive Reddit threads, reviews, or testimonials surfaced in searches. There are no verbatim third-party quotes to report — itself a signal worth weighing: the product is shipping fast, but adoption evidence beyond the company's self-reported task counts has not yet reached public channels.

---

Pricing & Licensing

As of June 11, 2026, Blocks still publishes no pricing page — the /pricing URL returns 404 — more than three months after this profile first flagged pricing as TBA. ^[1]

Licensing model: Freemium with sales-led enterprise (apparent)

Hidden costs: Requires Anthropic subscription for Claude Code, or API keys for other agents

---

Competitive Positioning

Direct Competitors

When to Choose Blocks Over Alternatives

• Choose Blocks when: You want to use familiar agents (Claude Code, Codex, Kimi Code) directly from GitHub/GitLab/Slack/Linear, with event-driven automations, and don't need published pricing or audited compliance
• Choose Tembo when: You need mature automation, deep integrations (databases, Sentry), and CLI agent orchestration from a funded vendor
• Choose Devin when: You want a fully autonomous AI engineer for junior-level tasks at scale
• Choose Factory when: You need certified enterprise compliance and proven large-org deployments

---

Ideal Customer Profile

Best fit:

• Teams heavily using GitHub, Slack, and Linear for development workflow
• Organizations wanting agent flexibility without building infrastructure
• Developers who want to try multiple coding agents without switching tools
• PMs and non-engineers who want to delegate technical tasks via Slack/Linear

Poor fit:

• Organizations requiring audited compliance certifications (SOC 2, ISO) before procurement
• Developers wanting local/CLI-first workflows
• Buyers who need transparent, published pricing to budget agent spend
• Teams that want a vendor with publicly verifiable funding and customer references

---

Viability Assessment

Blocks has executed well on product since this profile's first publication: the two biggest gaps flagged in February 2026 — no automations and no enterprise features — have both been addressed. ^[4] What hasn't changed is the visibility problem: no disclosed funding, no published pricing, and almost no public community footprint. In a fast-churn category, that combination means buyers are taking vendor risk on faith.

---

Bottom Line

Blocks brings coding agents to where teams already work — GitHub, GitLab, Slack, and Linear — and in 2026 it has grown from an @mention tool into a three-tier platform spanning ad-hoc sessions, automated PR review, and event-driven automations. The agent-agnostic approach is compelling for teams wanting AI assistance without adding another tool to their stack.

Recommended for: Teams using GitHub/GitLab/Slack/Linear who want to run multiple coding agents — including via automations and PR review — through a unified workflow-native interface.

Not recommended for: Buyers needing published pricing, audited compliance certifications, local development support, or public evidence of adoption before committing.

Outlook: Blocks has answered the product critique — automations, enterprise features, and a fast release cadence are all real now. The open question has shifted from "can they ship?" to "can they convert?": with no disclosed funding, no pricing page, and near-zero community discussion as of June 2026, Blocks must turn velocity into visible traction before better-funded orchestration platforms absorb its workflow-native positioning.

---

Research by Ry Walker Research • methodology