# ONES vs Taiga (slim)

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

- Full: https://www.anchorterminal.com/compare/ones-vs-taiga.md (~4,550 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/ones-vs-taiga.json · canonical https://www.anchorterminal.com/compare/ones-vs-taiga
- 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)

ONES scores 46.9 (D) on agent readiness against Taiga's 31.9 (F), and leads in 4 of 7 scored categories. Taiga leads on agent ergonomics. Both do issues and tasks.

- ONES: D 46.9, rank #1164 of 1510 · https://www.anchorterminal.com/tools/ones.min.md
- Taiga: F 31.9, rank #1414 of 1510 · https://www.anchorterminal.com/tools/taiga.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. Ahead on Reliability, 25 against 17; Schema & documentation, 55 against 35; Security & auth, 65 against 37; Maintenance & community, 68 against 21. Also A hosted endpoint, with nothing to install; Free to start without a card; No incidents deducted, where Taiga loses 3 points for them.
- Taiga, good for Small agile teams that want Scrum and Kanban with a free hosted plan or a self-hosted, open-source install in the EU. Ahead on Agent ergonomics, 49 against 40. Also Open source.

| Category | ONES | Taiga |
| --- | --- | --- |
| Reliability (16%) | 25 | 17 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 55 | 35 |
| Agent ergonomics (13%) | 40 | 49 |
| Security & auth (14%) | 65 | 37 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 68 | 21 |
| Transparency & trust (7%) | 62 | 66 |

| Fact (where they differ) | ONES | Taiga |
| --- | --- | --- |
| Vendor | The Beautiful ONES Technology PTE. LTD. | Taiga Cloud Services, S.L. |
| Hosted endpoint | `https://us.ones.com/mcp` | no (local only) |
| Transports | Streamable HTTP | HTTP |
| Licence | none | MPL-2.0 for the taiga-back source. The hosted service runs under Taiga's Terms and Conditions, which also mention non-open-source modules |
| Tools exposed | 67 | none |
| Read-only variant documented | yes | no |
| llms.txt | yes | no |
| MCP registry | `com.ones/ones` | not listed |
| Last release | 2026-09-30 | 2026-07-02 |
| Terms last updated | 2025-09-08 | 2025-09-01 |
| Privacy policy last updated | 2026-01-07 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 858 stars |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Maintenance & community, ONES +47: 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.); Taiga 21 (The latest tagged backend release is 6.10.2 of 2 July 2026, 99 days before the check (10). No tagged release in the last 90 days. The main branch had merges on 28 September 2026 and the changelog lists 6.10.3 as unreleased (0). Of the 25 open issues on the first page of taigaio/taiga-back, 18 have no reply, some since 2023, and 59 are open in all. The community forum was not sampled (6 of 25). No official SDK and no MCP server were found (0). One CI workflow runs the tests on Python 3.10 only, and issues about outdated packages (August 2025) and Python 3.13 (January 2026) are open. Version 6.10.0 updated dependencies (5).)
- Security & auth, ONES +28: ONES 65 (OAuth for MCP clients with per-scope consent, Personal API keys created with chosen scopes and shown once, organisation credentials, token introspection and revocation, all sent as Bearer headers (30). Scope groups allow a read-only grant, and the docs advise revoking unused clients, but writes run without a confirmation step and the consent page preselects every group (12 of 20). Tools return issue, comment and wiki text written by other users plus `search_external_web` results, and no prompt-injection guidance was found (0). The authorised client list shows each client's grant time and last active time, and on-premises installs document an audit log (8 of 15). security.txt valid until June 2027, and the trust centre lists SOC 2 Type II, ISO 27001 and ISO 27018 without report access or a bug bounty (15 of 20). 30 + 12 + 0 + 8 + 15 = 65.); Taiga 37 (The hosted service has no API key. A client posts the account's user name and password to `/api/v1/auth` and gets a bearer token, 24 hours by the backend default, with an 8-day refresh token. The token has no scopes and travels in the Authorization header. Application tokens need an application registered by an instance administrator (10 of 30). Reach is set by project roles with per-permission lists, so a dedicated account with a narrow role is the least-privilege route. No read-only token and no confirmation step for deletes (10 of 20). Story, issue and wiki text is untrusted content, and no prompt-injection guidance was found (2 of 15). Each object has a history endpoint, projects have timelines and webhooks have a delivery log. No API access log was found (7 of 15). A SECURITY.md and a security page give security@taiga.io, and two advisories with CVEs were published in October 2025. No security.txt, no bug bounty and no certificate held by Taiga were found. The security page cites the hosting provider's ISO/IEC 27001 (8 of 20).)
- Schema & documentation, ONES +20: 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.); Taiga 35 (No OpenAPI or other machine-readable contract was found (0). No llms.txt (the path returned 404). The docs' AsciiDoc source is public in taigaio/taiga-doc but is not served to agents (2 of 10). Each of the 49 sections states what a call does and lists its parameters in a line or two, with nothing on when not to use it (10 of 20). Parameters are listed with a type and a required mark, with no schema, enumerations or constraints (6 of 15). Every call has a curl example and a sample response object. Error responses are not described (9 of 15). The version sits in the path and the backend has a dated changelog. There is no changelog for the API, and the reference's footer is dated 3 April 2024 (8 of 15).)
- Agent ergonomics, Taiga +9: 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.); Taiga 49 (Graded on the REST API. Lists return 30 items a page and use lighter list objects than the detail calls. There is no field selection, and the page-size parameter in the backend settings is not in the reference (12 of 25). Pagination headers, per-resource filters, `order_by`, a `filters_data` call for each work item type and a project search endpoint (16 of 20). The backend returns `_error_message` and `_error_type` fields, which the reference does not document (6 of 20). No idempotency keys. The `version` parameter stops lost updates (10 of 20). No official SDK was found. Creating a task needs only a project and a subject, and a resolver call turns slugs into ids (5 of 15).)
- Reliability, ONES +8: 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.); Taiga 17 (Graded on the hosted REST API at api.taiga.io, with the hosted lines. The same API ships in the open-source backend. No status page is linked from the site, the docs or the terms (0), so there is no incident record to read (0). No request limit is published with numbers. The reference says only that an instance configured with throttling answers 429, and the backend's default settings leave the general rates unset (2 of 15). The backend's 429 message states the seconds to wait, which the reference does not mention, and every modifying request carries a `version` for optimistic concurrency. No idempotency keys and no retry guidance (5 of 15). The pricing page names priority support with an SLA for on-premise contracts by quote, and no SLA text is published (0). The API is version 1 and runs the vendor's own web client, though the terms say it may not always be available (10).)