Skip to content
ARTEX.sh

ARTEX vs ARIA-X:shared ideas, separate implementations.

ARIA-X credits ARTEX, Cairn and PentAGI for design ideas. Its NOTICE says it did not copy their source. This comparison covers the documented architecture and control defaults, checked on 2026-11-20. The site has not run either tool for this comparison or audited its security.

Data as of 2026-11-20

Architecture and controls

AspectARTEXARIA-X
RelationshipOriginal Go platform, continued by separate forks after the original repository was deleted.Independent Python implementation inspired by three projects; classified as a rebuild in this inventory.
State and storageThe original and RuoJi6 line use PostgreSQL and linked exploration and asset graphs. Other forks can differ.Python standard library, SQLite state, Fact/Intent/Hint blackboard and linked graph records.
Planner and executionPlanner generates intents; workers use tools and write findings back into the graphs.Planner generates intents; workers collect evidence; reports use persisted state. The docs identify ARTEX as an influence on this design.
Approval defaultsRuoJi6 v0.3.30: optional LLM judge is off; judge failure defaults to ask and approval timeout to deny.Security docs: auto is the default for high-risk tools. ask waits for human approval; deny rejects execution.
Scope and isolationDepends on the fork and saved settings. BaaRai documents an optional target gate, off by default.Documents checks before network-tool requests, but terminal scope checks are heuristic. Sandbox and network policy remain necessary.
Console and authenticationGo binary embeds a Next.js console; console exposure and authentication depend on the selected build.Documents a local console on 127.0.0.1 with optional Bearer-token authentication.
Public evaluationThis site records public contest scores with the original scoring context.README provides a deterministic offline demo. No comparable public contest result was found in the reviewed documentation.

A rebuild, not copied upstream code

The NOTICE distinguishes architecture reuse from source reuse. ARIA-X attributes dual graphs, planner-owned intent generation and persistent traces to ARTEX; it also credits Cairn and PentAGI. Its AGPL-3.0-or-later choice does not itself establish copied code.

The original ARTEX architecture is Go plus PostgreSQL and a Next.js console. ARIA-X uses the Python standard library and SQLite. Those differences describe implementation choices, not evidence that one system is safer or more capable.

Read the defaults and the stated limits

An approval feature is not necessarily active. RuoJi6 and ARIA-X both offer approval controls, but the defaults shown above do not require a person to approve every call. Inspect the exact version and saved configuration.

ARIA-X documentation expressly limits its terminal scope checks and does not treat command matching as full isolation. Its redaction is best effort, and model providers can see the context sent to them. These are important boundaries when reviewing an authorized test environment.

No performance ranking follows from a demo

ARIA-X describes a repeatable offline demonstration with a local teaching target. That helps explain its workflow, but it is not a comparable contest score, a real intrusion result or independent security validation. This page does not rank the tools.

More comparisons

Compare
  • AntiFox vs ARTEX

    AntiFox is a public fork that says it was built on ARTEX and adds report delivery. What changed, how active it is and its license.

  • ARTEX vs PentestGPT

    A Go platform with a web console against a Python command-line agent from a USENIX Security 2024 paper.

  • ARTEX vs Strix

    A self-hosted Go platform against an Apache-2.0 Python agent with a Docker sandbox, a cloud edition and CI support.

  • ARTEX vs CAI

    An AGPL platform still maintained in forks against CAI from Alias Robotics, now archived with a commercial successor.

  • ARTEX vs HexStrike AI

    A self-contained agent platform against an MCP server that lets your own AI client call more than 150 security tools.

  • ARTEX vs PentAGI

    Two self-hosted multi-agent systems written in Go: an AGPL platform kept alive in forks and VXControl's MIT system with a Docker sandbox.

  • ARTEX vs Cairn

    Cairn is the one project the ARTEX README lists as its reference. Both grow a graph of facts and intents; one is a Go platform, the other a Python engine.

  • ARTEX vs CyberStrikeAI

    Two Go platforms with a web console and human approval. CyberStrikeAI is Apache-2.0 and also ships WebShell management and a built-in C2.

  • ARTEX vs Shannon

    Both AGPL-3.0. ARTEX runs open-ended assessments from a console; Shannon reads an app's source and only reports what it can prove.

  • ARTEX vs T3MP3ST

    Both AGPL-3.0. ARTEX gates every tool call; T3MP3ST drives the coding agent you already use and has been quiet since 2026-09-08.

  • ARTEX vs AgenticPentest

    ARTEX is AGPL-3.0 and gates every tool call; AgenticPentest is a two-week-old MIT workbench that fences work by scope and approves state-changing actions.

Follow the ARTEX story.

New forks, releases and reports, dated and sourced.

Isometric plane with glowing light columns