Answers for evaluating Armoury.

Armoury connects test design, Test Runs, API Testing, Daily Reports, Equipment Management, dashboards, Work Reports, Defects, Jira Cloud, and governed AI access in one quality operations platform. Enterprise SAML SSO is provided through KEENLITY ID.

Start with one representative workflow that is causing friction: a release, API suite, daily review, shared-device process, Jira handoff, migration, or AI-assisted testing task. That is enough to identify the relevant capabilities and controls.

Free provides a one-user personal space with basic capacity and AI MCP for test engineers to learn and evaluate; Reports and Jira integration are not included. All paid plans are annual subscriptions: 1X supports 10 users at US$1,200 per year. The 5X annual list price is US$6,000, with a 2027 joining price of US$3,000 per year. The 10X annual list price is US$12,000, with a 2027 joining price of US$6,000 per year. Subscribe to a paid plan by December 31, 2027 to keep your annual joining price for life, unaffected by future price changes or newly added capabilities.

Yes. Armoury supports CSV and XLSX import with field mapping, preview, validation, and atomic commit, plus XLSX export of the active suite.

Armoury supports approved MCP-compatible clients, including registered ChatGPT and Claude clients. Organization and system policy determine which OAuth clients are accepted.

Depending on assigned scopes, AI can inspect and author test structure and cases, perform safe case updates, prepare Test Runs, inspect reports and Defects, and create, execute, and investigate API tests.

Daily Reports and Equipment are not exposed through MCP. AI also cannot use the current tool set to archive, delete, import, export, or perform secret-only API Testing writes.

Armoury validates the KEENLITY ID token, approved client, account and organization state, MCP policy, assigned scopes, membership, and normal Project permissions, then records tool activity for audit.

No. Manual Test Case work uses normal Armoury Projects. API Testing uses standalone organization-level API Projects with their own hierarchy, permissions, histories, dashboards, and reports.

Teams can build API Projects, nested Collections, Requests, environments, typed variables, authentication, runtime modules, assertions, extractors, conditional execution, reports, HTTP history, versions, and replay.

No. The current product does not provide scheduled API execution or Postman/OpenAPI import. Requests and Collections can be run manually or through approved MCP execute tools.

A Test Run stores its own Section and Run Case snapshots. Result submissions add history without rewriting the source Test Case.

Yes. A failed Test Run result can become an Armoury Defect with its execution evidence. Jira Cloud ticket data can then be imported or explicitly synchronized.

Members submit organization or Project updates for progress, blockers, risks, questions, decisions, support, or absence. Managers review current, unresolved, and tracked items through Pending, Needs Reply, Tracking, and OK states.

It tracks configurable assets, responsibility, current holder, availability, condition, loans, approvals, reservations, pickup, extensions, returns, transfers, notifications, attachments, and immutable events.

Organization roles govern shared operations, Project roles govern normal testing data, API Projects have local API permissions, and AI access adds a separate organization policy and OAuth scope layer.

No. Enterprise SAML SSO is included with paid subscriptions at no separate fee. After subscribing, contact KEENLITY to have it enabled in KEENLITY ID.

KEENLITY ID accepts a configured SAML 2.0 identity provider for SP-initiated sign-in. Current setup guidance covers Microsoft Entra and Google Workspace.

An Identity Owner verifies the exact corporate domain through DNS, configures the IdP and certificates, tests the current revision, previews affected accounts, and explicitly confirms SAML-only enforcement.

No. SAML authenticates the KEENLITY ID account; it does not create Armoury Organizations, memberships, Project roles, or entitlements. The current release also does not provide SCIM, IdP-initiated SSO, directory group mapping, or SAML Single Logout.