Agentic Index
cubic vs Ellipsis (2026)
Both vendors last verified
cubic and Ellipsis are the young challengers in AI review, expanding in different directions. cubic invests in the reviewing human, with a desktop app, ordered diffs, and diagrams, plus nightly repository scans with automatic fix pull requests. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Ellipsis invests in delegation, with coding agents defined as YAML in your repository that start from an @ellipsis mention, an issue, or a schedule, under hard spend caps. cubic is free for public repositories, and Ellipsis bills usage with no seat fees.
On the Agentic Index coding agent ranking, neither cubic nor Ellipsis clears the bar, which asks for all five merge loop capabilities documented in full. cubic does not document observability and auditability in full, nor human oversight and guardrails; Ellipsis documents two of the five in full. 3 of the 96 vendors in the lane clear it. See the coding agent ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. cubic and Ellipsis are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,140 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose cubic if
- Review ergonomics compound daily for your team, so the inbox and desktop experience matter.
- Latent merged bugs worry you, and nightly scans hunt them and open fixes.
- You want conventions learned from senior reviewers' history without config files.
Choose Ellipsis if
- Assigning small fixes to an agent from GitHub comments is the workflow you want.
- Spend capped, YAML defined agents fit your governance model.
- SOC 2 Type I, with Type II in progress, and credentials revoked at each session's teardown fit your security review.
| Feature | c cubic |
E Ellipsis |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
cubicIntegrations & Tool Calling A two way GitHub app drives inline comments, fix branches and approvals, project connectors cover Jira, Linear, Asana and Notion with Confluence on Pro, Slack and email notifications ship on Pro, PostHog (5 Oct), Sentry (8 Oct) and Datadog (11 Oct 2026) connect as production evidence so scan agents can confirm findings against real errors and logs, and cubic runs inside coding agent hosts through its MCP server and CLI. Sourcecubic.dev/pricing-plans and docs.cubic.dev/changelogread 2026-10-28 |
||
|
EllipsisIntegrations & Tool Calling The GitHub App, Slack and Linear integrations let agents open pull requests, post reviews and answer in the thread or ticket that started them, and a Sentry integration is documented but not generally released, with Jira listed as coming. Each agent's environment attaches MCP servers (Slack, Linear, remote or local) and secrets for further tools, so the customer extends the tool surface. GitLab no longer appears on the current site. Sourceellipsis.dev/docs/integrations and docs/environmentsread 2026-10-28 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
cubicWorkflow Orchestration Codebase scans are documented as thousands of parallel agents working through a staged process that maps the codebase, runs parallel checks, investigates, deduplicates and scores findings, and Ultrareview is a documented multi pass analysis. The scan docs still label scans beta and available by request, while the pricing page lists them on Pro. Reviews run a fixed sequence of review, inline comments, fix branches and optional approval, and heavier implementation can be handed to an outside coding agent. Sourcedocs.cubic.dev/codebase-scan/codebase-scans and cubic.dev/pricing-plansread 2026-10-25 |
||
|
EllipsisWorkflow Orchestration Agents are YAML files in the repository declaring trigger, harness, model, prompt, environment, permissions and budget, live on merge and previewed on branches. Parallel sessions each run in their own sandbox, branch and pull request, with a default of 32 live sessions per account, agents can start further sessions of their own, and a person can steer a session mid task. The documented harnesses are Claude Code, Codex and Gemini CLI; OpenCode, Copilot, Cursor, Pi, Grok Code and Antigravity are listed as not yet available, and no sub agent mechanism is documented. Sourceellipsis.dev/docs/agents, docs/harnesses and ellipsis.dev/pricingread 2026-10-28 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
cubicTriggers & Channel Coverage Reviews run automatically when a pull request opens and again on new commits, codebase scans run nightly on Pro, and the AI wiki regenerates on a weekly or monthly schedule, so work reaches the agent without a person starting it. @cubic mentions, Fix with cubic and the CLI add requested runs. Sourcecubic.dev/pricing-plans and docs.cubic.dev/wiki/ai-wikiread 2026-09-29 |
||
|
EllipsisTriggers & Channel Coverage Each agent carries one trigger: a cron schedule in UTC, or an event on GitHub pull requests (opened, pushed, merged, closed, review submitted, commented), pushes, issues (opened, labeled), check runs, check suites, workflow runs, statuses and releases, Linear issues, Slack channel creation or Sentry events, and each run starts a session with no one invoking it. Sessions also start on demand from @ellipsis mentions, the dashboard, the CLI and the API. Issue assignment is not a trigger, and webhooks are outbound only. Sourceellipsis.dev/docs/agents/triggersread 2026-10-28 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
cubicKnowledge Grounding & RAG The AI wiki automatically indexes the codebase into searchable documentation with source links and architecture diagrams, regenerated monthly on Team and on a daily, weekly or monthly schedule on Pro and Max as code changes. It can be queried in plain English, over MCP or as synced markdown, alongside whole repository and cross repository context during reviews. Sourcedocs.cubic.dev/wiki/ai-wiki 2026-09-29 and cubic.dev/pricing-plansread 2026-10-25 |
||
|
EllipsisKnowledge Grounding & RAG Context is assembled per session. Each session checks out the repositories its environment names from a cached environment image, so the Claude Code, Codex or Gemini CLI harness reads the working tree directly, alongside Codex skills and connected Slack, Linear and Sentry context. There is no persistent index, graph or embeddings layer over the customer's code. Sourceellipsis.dev/docs/environments and docs/sessionsread 2026-10-28 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
cubicMemory & State Persistence cubic extracts learnings from PR comments, reactions and senior reviewers' past reviews, scoped to the team and never shared across organizations or repositories. Learnings are browsable, editable and deletable under Memory and Learning, and a weekly cleanup merges duplicates and archives outdated guidance. Sourcedocs.cubic.dev/ai-review/memory-and-learningread 2026-09-29 |
||
|
EllipsisMemory & State Persistence A session stays open for follow ups that continue the same workspace, and a mention starts a durable conversation per pull request, issue or Slack thread that later replies continue, with session records kept for a customer set retention of up to a year. That state stays within one thread. No memory layer with its own scope and lifetime that the agent reads across independent sessions is documented. Sourceellipsis.dev/docs/sessions and docs/agents/triggersread 2026-10-28 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
cubicHuman Oversight & Guardrails Auto approval runs under a per repository policy the customer sets (low risk only, custom or always), and cubic approves only when its review finds no issues. No person approves anything before cubic acts, so the policy constrains the agent and is not an approval step. Shadow mode, which previews approvals before they go live, is covered under testing. Sourcedocs.cubic.dev/ai-review/auto-approvalread 2026-09-29 |
||
|
EllipsisHuman Oversight & Guardrails Ellipsis constrains what an agent can do rather than gating its actions. Permissions declared per agent limit each session's GitHub credential to named repositories and to read only or specific write scopes and set its Ellipsis API scopes, and hard budgets stop model requests per session, agent, developer and account before compute starts. A code review agent's output is set to stay silent, comment or approve on a pass and to comment or request changes on a fail, with blocking comments marked, and work reaches the codebase as pull requests the customer merges on its own code host. There is no step where a person approves an agent action before it commits, and no plan review or auto merge. Sourceellipsis.dev/docs/permissions, docs/budgets and docs/code-reviewread 2026-10-28 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
cubicSecurity, Identity & Governance Compliance is SOC 2 Type 1, with TLS 1.2 or higher in transit, AES-256 at rest, subprocessor agreements that prohibit training on customer code, and a trust center at trust.cubic.dev listing subprocessors. Enterprise adds SSO and SAML through GitHub OAuth, GitHub Enterprise support, exportable compliance audits and custom MSA and DPA terms. Sourcedocs.cubic.dev/account/privacy-security and cubic.dev/pricing-plansread 2026-10-28 |
||
|
EllipsisSecurity, Identity & Governance SOC 2 Type I certification is in place, with Type II in progress and no trust page. Access controls cover owner and administrator roles for account settings with per developer spend limits, scoped API keys, per session GitHub credentials minted at the permissions each agent declares and revoked within an hour at teardown, write only secrets, zero source retention, and customer set session data retention from zero hours to one year with deletion within four hours of expiry. There is no SSO, SAML or SCIM support. Sourceellipsis.dev/docs/security, platform/security and docs/api/authenticationread 2026-10-28 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
cubicObservability & Auditability The Analytics API returns per pull request metrics (issues flagged and fixed, AI authored lines, engagement times), the Analytics AI review tab rebuilt on 6 Oct 2026 shows what happens to each issue cubic raises, Pro tracks AI coding usage, and Enterprise exports compliance audits. These report outcomes, and there is no stated per run record of the review agent's steps or tool calls. Sourcedocs.cubic.dev/analytics/api, docs.cubic.dev/changelog and cubic.dev/pricing-plansread 2026-10-28 |
||
|
EllipsisObservability & Auditability Every session is recorded. The dashboard and CLI show messages and tool calls as they happen, session events, turns and records are readable over the API, and an audit trail covers commands, file changes and tool calls. Transcripts are downloadable as unmodified Claude Code, Codex and Gemini CLI output, sessions are searchable and linked to the pull requests they produced, code review history is kept in the dashboard, and cost and token, CPU and memory usage are tracked per session, developer and agent. Sourceellipsis.dev/docs/sessions and platform/observabilityread 2026-10-28 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
cubicDeployment & Data Residency cubic is hosted SaaS installed as a GitHub app, and code is never stored or used for training. There is no stated self hosting, customer cloud or region choice. Sourcecubic.dev/pricing-plans, cubic.dev/enterprise and docs privacy-securityread 2026-09-29 |
||
|
EllipsisDeployment & Data Residency Ellipsis comes in two offerings. With Managed SaaS, each session runs in its own sandbox VM in Ellipsis's cloud, sized by the agent's compute setting, and Your AWS Account deploys the control plane and agent sandboxes into the customer's AWS VPC with no credentials, code or LLM calls leaving it, billed by AWS. Session data retention is set by the customer. No region choice is stated. Sourceellipsis.dev/pricing and docs/environmentsread 2026-10-28 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
cubicPrebuilt Agents, Templates & Packs Teams turn on prebuilt review agents from cubic's agents library, which lists 63 agents, and adopt community and suggested agents with one click. Since 9 October the library runs on all repositories by default. Teams also write their own custom agents in natural language, five on Team and ten on Pro. Sourcecubic.dev/agents and docs.cubic.dev/ai-review/custom-agentsread 2026-10-25 |
||
|
EllipsisPrebuilt Agents, Templates & Packs A code review agent is available as example YAML with documented output settings, Codex sessions take up to ten skills (Claude Code and Gemini skills are not supported), and skills install with npx skills add. The docs describe no template gallery, prebuilt agent library or review rule packs, only use case pages and guides. Sourceellipsis.dev/docs/code-review and docs/agentsread 2026-10-28 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
cubicModel Flexibility & Routing Hosted pull request reviews run on models cubic chooses from OpenAI and Anthropic, so more than one provider is disclosed but the customer does not pick for the reviewer that acts on pull requests. Enterprise offers bring your own API keys without a model or provider selection. The cubic CLI alone lets a developer connect a ChatGPT or Claude Code subscription and switch providers and models for local reviews (changelog 19 Apr 2026), a picker that does not reach the hosted reviewer. Sourcedocs.cubic.dev/account/privacy-security, cubic.dev/pricing-plans and docs.cubic.dev/changelogread 2026-10-28 |
||
|
EllipsisModel Flexibility & Routing The customer picks the harness and model for every agent and session across three makers: Claude models in Claude Code, GPT models in Codex and Gemini models in the Gemini CLI, each priced per million tokens. A Claude or ChatGPT subscription can pay for sessions a user starts. No bring your own key path is documented. Sourceellipsis.dev/docs/models and docs/pricingread 2026-10-28 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
cubicAPIs, SDKs & MCP Extensibility cubic's own MCP server at cubic.dev/api/mcp, signed in with OAuth or an API key, offers 20 tools plus three environment tools, including get_pr_issues, trigger_pr_review, update_pr_issue_status, list_wikis, list_scans and get_scan. Several of them start reviews or change finding status, so outside agents can act through cubic, not only read from it. On Pro, an Analytics API adds a bearer token endpoint, and since 2 October organization API keys and a Members API are available. Sourcedocs.cubic.dev/ide/mcp-server and changelog 2026-10-25, analytics/apiread 2026-09-29 |
||
|
EllipsisAPIs, SDKs & MCP Extensibility A REST API at api.ellipsis.dev/v1 with bearer API keys and a published OpenAPI specification starts, streams, messages and stops sessions and manages agents, environments, secrets and webhooks. Python and TypeScript SDKs and the ellipsis CLI work over the same surface. Sourceellipsis.dev/docs/api and docs/api/authenticationread 2026-09-29 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
cubicTesting, Debugging & Optimization Shadow mode keeps cubic in comment only mode on real pull requests while adding a summary of whether it would have approved each one, so a team tests the agent's approval behavior under its chosen policy before granting it live authority. Bug detection, the product itself, tests the customer's code and not the agent. Sourcedocs.cubic.dev/ai-review/auto-approvalread 2026-09-29 |
||
|
EllipsisTesting, Debugging & Optimization Ellipsis tests the customer's code, not the agent. A code review agent reviews each push to a pull request and runs the project's test suite in its sandbox, an environment validate hook and an Ellipsis environment pull request check confirm the setup, and session records show the tests run. There is no harness, scored test set or optimization loop for evaluating agent behavior. Sourceellipsis.dev/docs/code-review, docs/environments and docs/sessions; ellipsis.dev/docs/agents/code-reviewread 2026-10-28 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
cubicBrowser & Computer Use cubic works through the GitHub API, an isolated review container, a CLI and MCP, with no stated browser control or operation of software through a graphical interface. Sourcedocs.cubic.dev and cubic.dev/pricing-plansread 2026-09-29 |
||
|
EllipsisBrowser & Computer Use Ellipsis does not operate browsers or desktops. Sessions run the Claude Code, Codex or Gemini CLI harness in an isolated cloud Linux sandbox with terminal and file access, which is code execution, no browser, desktop or computer control tool is offered, and Gemini's web search and fetch are turned off. Sourceellipsis.dev/docs/environments and docs/harnessesread 2026-10-28 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | c cubic |
E Ellipsis |
|---|---|---|
|
Entry price Lowest public entry point |
Free plan. Team at $30 per developer per month billed annually, or $40 monthly. | Usage based, with model tokens plus a 10% platform fee and no seat fees. |
|
Pricing confidence How public the numbers are |
Public, exact | Public, exact |
|
Billing Primary billing axis |
Subscription tiers priced per developer per month, each with a monthly allowance of reviewed lines (the added and deleted diff lines cubic reads). The free tier is capped by monthly review count, and Enterprise is custom. | Usage based. Prepaid credits pay model tokens at the published rate per million tokens, with a 10% platform fee on credit purchases, and organization sandbox CPU and memory at cost. Personal compute is free, and there are no per seat fees. |
|
Variable cost Workload / overage exposure |
Medium variable cost | High variable cost |
|
Free tier / trial Try before you buy |
Free tierTrial
|
Free tier
|
|
Buying motion Self-serve vs sales call |
Self-serve | Self-serve |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
cubic
-
· Agent capability
Codebase scan agents in cubic can now check whether production data confirms the bugs and vulnerabilities they find, starting with PostHog, which is switched on per repository under Production evidence.
Source -
· Human approval / guardrails
cubic added a repository policy that allows automatic pull request approval while findings at selected priorities remain unresolved.
Source -
· Agent capability
cubic now supports cross-repo reviews, allowing users to link up to five related repositories for coordinated updates.
Source
More comparisons with cubic or Ellipsis
Other matchups in coding agents
Not the pairing you were after? These compare a different set of coding agents on the same 14 capabilities.