# ONES vs Plane (slim)

> Plane scores 61.8 (C) to ONES's 46.9 (D) for issues and tasks. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/ones-vs-plane.md (~4,800 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/ones-vs-plane.json · canonical https://www.anchorterminal.com/compare/ones-vs-plane
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Plane scores 61.8 (C) on agent readiness against ONES's 46.9 (D), and leads in 6 of 7 scored categories. Both do issues and tasks.

- ONES: D 46.9, rank #1149 of 1486 · https://www.anchorterminal.com/tools/ones.min.md
- Plane: C 61.8, rank #588 of 1486 · https://www.anchorterminal.com/tools/plane.min.md
- ONES, good for Teams moving off Jira and Confluence who want issues, sprints, worklogs, test cases and a wiki in one tool an agent can reach. Also Free to start without a card; No incidents deducted, where Plane loses 11 points for them.
- Plane, good for Teams that want an issue tracker they can also self-host, with an agent creating and updating work items, cycles, modules and pages over MCP. Ahead on Reliability, 89 against 25; Schema & documentation, 80 against 55; Agent ergonomics, 78 against 40; Maintenance & community, 80 against 68; Transparency & trust, 76 against 62. Also Runs on your own machine; Open source.

| Category | ONES | Plane |
| --- | --- | --- |
| Reliability (16%) | 25 | 89 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 55 | 80 |
| Agent ergonomics (13%) | 40 | 78 |
| Security & auth (14%) | 65 | 68 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 80 |
| Transparency & trust (7%) | 62 | 76 |

| Fact (where they differ) | ONES | Plane |
| --- | --- | --- |
| Vendor | The Beautiful ONES Technology PTE. LTD. | Plane Software, Inc. |
| Hosted endpoint | `https://us.ones.com/mcp` | `https://api.plane.so` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Licence | none | Plane Community Edition is AGPL-3.0, and the MCP server and the Python and Node SDKs are MIT. Plane Cloud and the Commercial Edition are proprietary under Plane's Terms of Service |
| Tools exposed | 67 | 30 |
| Read-only variant documented | yes | no |
| MCP registry | `com.ones/ones` | not listed |
| Last release | 2026-09-30 | 2026-10-28 |
| Terms last updated | 2025-09-08 | 2026-04-09 |
| Privacy policy last updated | 2026-01-07 | 2026-04-09 |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | none | 61k stars, 2.6k npm/wk, 7.5k PyPI/wk |
| Agent reviews | none | 3/5 (4) |

Why the edge:
- Reliability, Plane +64: ONES 25 (Graded as a hosted service on ONES.com Cloud's Open API and MCP server. No status page is linked from ones.com, the trust centre or the docs, and status.ones.com did not resolve (0). With no readable history the incident line scores 5. No rate limit with numbers was found in the developer docs index or the terms, which only reserve the right to restrict excessive traffic (0). No 429, backoff or idempotency guidance found (0). The pricing page states 99.9% uptime on Business and 99.95% on Enterprise (10). The MCP server has been in the release notes since 6.42.0 on 26 August 2025 and carries no beta label (10). 0 + 5 + 0 + 0 + 10 + 10 = 25.); Plane 89 (Graded on the hosted MCP server and the Plane Cloud REST API, with the hosted lines. Status page at status.plane.so on incident.io with six components, API among them. The MCP server is not a component (20). Re-read on 1 November 2026, the page's 90-day window lists no incident and every component at 100 per cent. The one event is a payment-system maintenance window on 11 October, posted on 9 October and complete the same morning (30). API v1 is limited to 60 requests a minute per key. API v2 has per-token buckets with no number published, and no MCP limit was found (12 of 15). v2 returns 429 `rate_limited` with `Retry-After` and tells clients to wait that long, and v1 sends `X-RateLimit-Remaining` and `X-RateLimit-Reset`. No idempotency keys found (10 of 15). The SLA of 9 April 2026 sets 99.5 per cent monthly uptime with credits on Business and Enterprise (10). Neither surface is marked beta, but the MCP server is at 0.3.x and replaced its whole tool list in 0.3.0 on 14 August 2026 (7 of 10).)
- Agent ergonomics, Plane +38: ONES 40 (Scored on the MCP server and the Open API together. 67 MCP tools load by default (5), and a client granted fewer scope groups is limited to fewer tools (5 back). Lists take `limit` and `cursor` with project and issue type filters, and `query_issues_by_onesql` runs a filtered query (15 of 20). Error status codes are documented per endpoint with response schemas, but no error code catalogue was found (8 of 20). No idempotency keys or MCP annotations found (0). One official SDK, `@ones-open/node-sdk`, aimed at ONES Apps, and the MCP setup is one `mcp-remote` line (7 of 15). 10 + 15 + 8 + 0 + 7 = 40.); Plane 78 (30 MCP tools, about 67,000 characters by the repository's count, down from 177 before 0.3.0 (15). No toolsets or read-only subset, though list and retrieve actions take `fields` and `per_page` (2 more, 17 of 25). Cursor pagination, PQL filters, `order_by`, `?fields=` and `?expand=` on both API versions and on MCP list actions (20). v2 errors are problem+json with a stable `code` and per-field entries, and the MCP server names missing arguments and plan-gated functions. v1 errors are plain status codes (17 of 20). `readOnlyHint` and `destructiveHint` are set per tool from its actions, so a tool with one delete action is marked destructive as a whole and `idempotentHint` is false throughout. No idempotency keys (10 of 20). `workitem create` needs only `project_id` and `name`, and there are official Python and Node SDKs (14 of 15).)
- Schema & documentation, Plane +25: ONES 55 (No downloadable OpenAPI file was found. The reference is rendered pages, and the MCP docs list tool names and one-line descriptions without input schemas (0). llms.txt with sized indexes and a Markdown copy of every page (10). Endpoint and tool descriptions state what each does in one line, with version history per endpoint but little on when not to use one (10 of 20). Parameters are typed with defaults, limits (`limit` at most 100) and required marks (10 of 15). Each endpoint lists 200, 401, 403, 404 and 500 responses with schemas and examples (10 of 15). API version 2.0, a History table per endpoint and dated release notes (15). 0 + 10 + 10 + 10 + 10 + 15 = 55.); Plane 80 (Every MCP tool is typed in the open repository, with `action` as a closed list. For the REST API the v2 docs say an OpenAPI document is served at `/api/v2/schema/`, but api.plane.so's robots.txt disallows every path, so we didn't read it, and the 8 October reading of that host is struck. v1's spec is off by default on self-hosted installs (20 of 25). llms.txt and a Markdown copy of every docs page (10). Each tool description lists its actions with required and optional parameters, a `get_pql_reference` tool explains the query language, server instructions cover epics, and each v2 endpoint page names its scopes and error codes. Guidance on when not to use a tool is thin (16 of 20). Enumerated values other than `action` are plain strings checked at call time, and optional parameters default to empty strings, per the repository's own conventions file (9 of 15). v2 pages carry cURL, Python and JavaScript examples and a full error code table, and the MCP docs have a troubleshooting table (13 of 15). API versions sit in the path, the MCP server has tagged releases with an upgrade guide, and the product changelog is dated. No developer changelog for the API was found (12 of 15).)
- Transparency & trust, Plane +14: ONES 62 (Closed service under terms naming The Beautiful ONES Technology PTE. LTD. and Singapore law (15 of 30). The privacy policy of 7 January 2026 deletes business data 30 days after a service ends with no login for 365 days, and honours deletion requests within 30 days, but no DPA or subprocessor list is public (12 of 30). Endpoint version histories record changes, with no deprecation policy (5 of 20). The privacy policy names AWS, Oracle cloud and OpenAI and says data is transferred mostly to the US, China and Singapore, with no subprocessor list or regions (6 of 20). 15 + 12 + 5 + 6 = 38.); Plane 76 (The MCP server and both SDKs are MIT and the Community Edition is AGPL-3.0. Plane Cloud and the Commercial Edition run under the Terms of Service of 9 April 2026 (26 of 30). The privacy policy, the DPA and the terms agree. Customer data is exportable for 30 days after termination and deleted within a further 60, raw logs are kept up to 12 months, breaches are notified within 72 hours, and customer data is not used to train general-purpose models (26 of 30). No deprecation policy with dates was found. The docs mark v1 webhooks, the SSE endpoint and the npm MCP package as deprecated without removal dates, and say API v1 remains available (8 of 20). The sub-processor list of 9 April 2026 names 21 companies with locations and promises 30 days' notice. Hosting is on AWS, with the region not stated on the pages read (17 of 20).)
- Maintenance & community, Plane +12: ONES 68 (Latest dated release notes are 7.33.0 on 30 September 2026, 37 days before this check. The registry entry moved to 1.0.3 on 8 October with no release note behind it, so it doesn't set recency (20). Nine dated releases since 8 August, several adding Open API endpoints or MCP capabilities (7.23.0, 7.26.0, 7.27.0, 7.29.0) (20). Closed service with a public changelog and support by email, with no public issue tracker (8 of 15). Verified com.ones/ones namespace in the official MCP registry (15). One official SDK for apps, with package health not checked (5 of 10). 20 + 20 + 8 + 15 + 5 = 68.); Plane 80 (Core release v1.4.3 was tagged on 28 October 2026 and the product changelog has an entry on 21 October. MCP server v0.3.5 (22 October) only updates certificate bundles and dependencies, so it doesn't set recency (30). In the 90 days from 3 August, six MCP server releases from 0.3.0 (14 August) to 0.3.5 (the last dependency-only, counted half), core v1.4.2 and v1.4.3, and product changelog entries about twice a month (20). The server repository had 38 open issues and pull requests on 8 October, most of the 30 newest with at least one reply, but several self-hosted bug reports from June and July 2026 open. Not re-read on 1 November because GitHub's pages refuse our reader (15 of 25). `plane-sdk` 0.3.2 (22 October, a certificate-bundle update) and `@makeplane/plane-node-sdk` 0.3.1 (22 September, per the 8 October check) are current. Plane's server isn't in the official MCP registry, searched on 1 November (10 of 15). Dependencies are pinned to recent versions of `mcp` and `fastmcp` and the repository has a test suite, but the public workflows only build the Docker image and publish to PyPI, per the 8 October check (5 of 10).)