Project

In this sectionHow 10xGraph is run: MIT license, maintained by 10xScale, with a changelog, roadmap, security reporting, support channels and a contributing guide.

  • 7 pages
  • About 46 min to read all

This section covers 10xGraph as a project: who maintains it, how releases are announced, how to report a security problem, where to get help and how to contribute. It is MIT licensed, maintained by 10xScale, at version 1.0, after its October 2026 rename from Agentflow.

Start here

Read the Changelog first to see what has shipped and which versions are current, then the Roadmap for what is missing, partial or deliberately out of scope. The roadmap is where the honest gaps are listed, so it is worth reading before you commit to the project.

If you plan to upgrade across a breaking change, Upgrade to 1.0 explains what to migrate from 0.10 (core), 0.9 (API) and 0.6 (client), and Upgrade to 0.9 covers 0.8. For the package rename (new PyPI and npm names, CLI and GitHub org), see Coming from Agentflow. If something breaks, Support explains what to collect for a bug report that gets fixed, and Security describes private vulnerability reporting. To send a fix or a doc improvement, start with Contributing; the people involved are listed on Maintainers.

Page Answers
Changelog What shipped, and which versions are current
Stability What 1.0 commits to, and how a deprecation works
Upgrade to 1.0 What breaks from 0.10, 0.9 and 0.6, and how to migrate
Upgrade to 0.9 What broke from 0.8 to 0.9, and how to migrate
Roadmap What is missing, partial, or deliberately out of scope
Security How to report a vulnerability, and what is by design
Support Where to ask, and how to file a report that gets fixed
Contributing Local setup, conventions, and the checks that gate a merge
Maintainers Who maintains 10xGraph, and who has contributed to it

At a glance

  • License: MIT, for the framework, the API server and CLI, and the client. No paid tier and no hosted-service requirement.
  • Maintainer: 10xScale, which runs 10xGraph in production across its own products.
  • Stability: from 1.0 the public API does not break before 2.0. Anything removed is deprecated first and removed only in 2.0. See Stability.
  • Requires: Python 3.12 or newer; Node 20 or newer for the TypeScript client.

All pages in Project

  1. Stability and deprecation policyWhat 10xGraph 1.0 commits to. The public API of the framework, the API server and the client does not break before 2.0, and anything removed is deprecated first.2 min
  2. Upgrade from 0.x to 1.0Migration guide from 10xgraph 0.10, 10xgraph-api 0.9 and 10xgraph-client 0.6 to 1.0, with every breaking change grouped by package and what to do about it.30 min
  3. Upgrade to 0.9Migration guide from 10xGraph 0.8 to 0.9, covering the four breaking changes and the new defaults that change runtime behaviour.4 min
  4. Roadmap and known gapsWhat 10xGraph does not do yet, which surfaces are incomplete, and where dated release planning actually lives.3 min
  5. Security policyHow to report a vulnerability in 10xGraph, what response to expect, which versions receive fixes, and which behaviours are by design rather than bugs.2 min
  6. Getting helpWhere to ask questions, how to file a good bug report for 10xGraph, and what information to collect before you do.2 min
  7. ContributingHow to contribute to 10xGraph and to these docs, including the local setup, the writing conventions, and the checks that must pass before a pull request merges.3 min