GraQle
Give your AI agents a memory of how your organisation works - and check every decision before they act.
pip install graqle
Website · Quickstart · Decision Assurance · Shared memory · Changelog
What GraQle does
- Remembers. Turns your code, documents, policies and decisions into one connected knowledge graph that lasts beyond a chat session.
- Checks. Before an agent acts, the Decision Assurance Gate checks the action and answers EXECUTE, REPLAN, HOLD, REJECT or ESCALATE - with the reason and a signed record.
- Shares. One graph serves a whole team of agents - Claude Code, Cursor, Codex, Copilot - each with its own permissions and its own files.
Works with any model: Anthropic, OpenAI, AWS Bedrock, Ollama, Gemini and more - or fully offline.
Quickstart
pip install graqle
graq scan docs ./policies # documents, policies, ADRs -> graph
graq scan repo . # code -> the same graph
graq learn knowledge "vendor DPA must be signed before any data access"
graq run "what approval is needed for a large refund?"
# -> answer + confidence + the exact sources it used
Connect it to your AI tool (Claude Code, Cursor, Windsurf, VS Code):
graq init # detects your IDE and wires GraQle in
PDF, DOCX, PPTX and XLSX: pip install "graqle[docs]".
Check every decision
Most AI tools give you one confidence number. GraQle asks separate questions before an agent acts - and a good answer to one never hides a failed answer to another:
- Allowed? Policy valid, actor authorised, evidence current, arguments exactly the approved ones. Any "no" stops the action.
- Consistent? Contradicting facts are tracked in the graph, and a change updates every decision that depends on it.
- Sure enough? Confidence is measured per dimension, not blended into one score.
- On track? Unreliable step sequences are sent back to replan within a retry budget.
- Who approves? Authority is checked for the action's impact level.
| Answer | Meaning |
|---|---|
EXECUTE |
Everything checks out. Impossible after any failed check or error. |
REPLAN |
Make a better plan and try again. |
HOLD |
Something important is missing; wait for it. |
REJECT |
Not allowed, or contradicted by the evidence. |
ESCALATE |
A human decides. |
from graqle.assurance.gate import DecisionAssuranceGate
verdict = gate.evaluate(candidate, ctx)
verdict.outcome # EXECUTE | REPLAN | HOLD | REJECT | ESCALATE
verdict.decisive_rule # which rule decided
verdict.reason_codes # why
Every decision leaves a sealed record: a signed, hash-chained provenance event, exportable to W3C PROV-O and checkable with SHACL, so an auditor can verify it with standard tools. The gate is off by default: installing or upgrading GraQle changes nothing until you switch it on.
Turn it on, per project:
- Set
GRAQLE_DAG_ENABLED=truein the environment where GraQle runs (or in your.env). - Provide the required settings. GraQle ships no thresholds, salts or keys: you choose them. Start from the
GRAQLE_DAG_*section of.env.exampleand fill in every placeholder (salt, thresholds, signing key id and version, calibrator version, and the others listed there). Put the values in the environment, or in a private file atGRAQLE_DAG_SECRETS_PATH(default.graqle/graqle_secrets.yaml); the environment wins. - Start as usual. If a required value is missing, GraQle raises a configuration error that names it the first time the gate settings load. There is no silent fallback.
Check it: python -c "from graqle.assurance.settings import is_dag_enabled; print(is_dag_enabled())" prints True.
To switch it off again, unset the flag or set it to false. Details: operating the gate.
One memory for a team of agents
Several agents on one codebase usually means several copies of the same graph in memory. GraQle can hold it once:
# where the graph lives
graq mcp serve --transport http --port 8765 --config graqle.yaml --allowed-roots /path/to/projects
# in each agent session (.mcp.json)
{ "mcpServers": { "graqle": { "command": "graq", "args": ["mcp", "relay", "--url", "http://127.0.0.1:8765"] } } }
- Less memory. Each session runs a small relay instead of a full copy (measured on a 20,000-node graph: 3 separate servers 687 MB, shared server + 3 relays 493 MB).
- Learning is shared at once across all sessions.
- Each session keeps its own gates and its own files - file work happens on each user's own machine.
- Teammates connect over an SSH tunnel, or HTTPS with a token.
- Several projects, separate graphs on one server (Team and Enterprise).
Trust
- Local-first, no telemetry. The graph is a file you control; nothing phones home.
- Secure by default. The server needs authentication unless you explicitly switch on local development mode; graph uploads can never silently overwrite each other.
- Signed releases. Sigstore-signed wheels, CycloneDX SBOM, reproducible builds.
- Regulated work. Audit trail and evidence exports for your own EU AI Act file - GraQle provides evidence, it does not claim to make you compliant. Details
Report vulnerabilities to security@quantamixsolutions.com · SECURITY.md
Editions
| What you get | |
|---|---|
| Free | Knowledge graph, all core tools, governance gates, Decision Assurance Gate, shared server for one project |
| Pro — $19/mo | Cloud sync, priority models, hosted transparency-log relay |
| Team — $29/dev/mo | Shared graphs across projects (multi-project server), team lessons, audit-log retention |
| Enterprise | On-premise, custom backends, support SLAs - contact us |
Recent releases
- v0.87.0 — Decision Assurance Gate: five-answer decisions, contradiction tracking, confidence per dimension, replanning, signed provenance records.
- v0.86.0 — One memory for a team of agents: shared server, thin relay, per-session gates, file work on each user's machine; secure-by-default server.
Patent & license
Core methods are patent-pending: EP26167849.4, EP26162901.8 and EP26166054.2. Source is fully auditable under the GraQle License - see LICENSE.
Built by Quantamix Solutions · github.com/quantamixsol/graqle
1 maintainer
Metadata
1 maintainer
Release files for graqle 0.87.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| graqle-0.87.0.tar.gz | 5.6 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| graqle-0.87.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 7.9 MB
Release files / graqle-0.87.0.tar.gz
| Download URL | graqle-0.87.0.tar.gz |
|---|---|
| Size | 5.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a731a2df504f6481ef99a6e0f021feab1646330fdd67c851abda03e416ef1787
|
|
BLAKE2b-256 checksum How to use checksums |
4a7f6657fe22b4383d3b4c3ab74eeb7490447f63447abcdde71b8517c5d06f9e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / graqle-0.87.0-py3-none-any.whl
| Download URL | graqle-0.87.0-py3-none-any.whl |
|---|---|
| Size | 2.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9899125b2e711a45e4a4c5bc13df155946b344c9b22106330b20692f642a30e8
|
|
BLAKE2b-256 checksum How to use checksums |
b4b81a546b1ddf25724859b59c991fbff1debef706ea350279c7e5a0c66e6a6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for graqle 0.87.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for graqle-0.87.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
