Two products, one author
How GraQle and CrawlQ relate.
CrawlQ is your AI research and content workspace. GraQle is a separate open-source SDK from the same author. CrawlQ does not run on GraQle; it includes one small module adapted from it, and that module is what lets you prove a recorded approval was not changed.
The problem
AI tools forget. That is expensive.
Context decays between prompts, people, and model versions — and when it does, no one can reconstruct why an output was produced or whether it was on-brand.
Prompt amnesia
Essential context gets retyped from scratch every session, thinner each time.
Document fragmentation
Knowledge exists, but the relationships and authority behind it are unclear.
Decision opacity
Teams cannot explain which evidence or policy shaped an output.
Model drift
Swap the model and results change — with no stable organisational anchor.
Two products
Separate products. One shared module.
CrawlQ keeps your team's research, brand context and approvals in its own workspace. GraQle is a developer SDK you can use on its own.
GraQle — the SDK
An open-source memory and reasoning SDK for developers.
Holds concepts, evidence, versions, policies, decisions, and outcomes as a live graph — so context is portable across models and never has to be retyped. Open-core; a developer can drive it directly over MCP.
CrawlQ — the application
The workspace your team uses every day.
Audience research, brand memory, strategy, and content, with a named reviewer’s approval recorded on each output when human review is switched on. Its own product and codebase; it does not run on GraQle.
The proof
Not a claim — a public record.
This is the part CrawlQ uses the shared module for: an approval record anyone can verify, without taking our word for it.
When a human approves AI content in CrawlQ, the root of that record is written to a public transparency log CrawlQ cannot edit or delete from — the same kind of log that secures the world’s open-source software. You export the trail from your own CrawlQ workspace and hand it to your auditor; they then confirm it against the public record — and that verification step needs no access to CrawlQ at all. Only a fingerprint is ever public — never your content, your reviewers’ names, or your workspace.
Where to go next
Two ways in.
Use the CrawlQ workspace, or use the GraQle SDK on its own.
Use CrawlQ
The full workspace — Brand Memory, Research, Governance, Canvas — with the audit trail built in. For teams that want the product.
See CrawlQ plansIntegrate GraQle
The separate open-core SDK — an MCP-compatible memory and reasoning layer for your own stack. For developers.
See the engineering pageCommon questions
The questions people ask first.
- Is GraQle the same thing as CrawlQ?
- No. They are separate products from the same author. CrawlQ is the workspace your team uses; it does not run on GraQle. GraQle is an open-source SDK that developers can use on its own.
- What does CrawlQ use from GraQle?
- One small tamper-evidence module: Merkle hashing and public-log anchoring, adapted into CrawlQ's own codebase. It is what makes a recorded human approval checkable against a public log. Nothing else is shared.
- How is the audit trail verifiable?
- When a human approves AI content, the root of that record is written to a public transparency log CrawlQ cannot edit or delete from. An auditor confirms your exported trail against that public log without needing any access to CrawlQ. Only a fingerprint is ever public — never your content or your people.
- Can I use GraQle on its own?
- Yes. GraQle is an Apache-2.0 open-core SDK that exposes its tools over MCP, so a developer can drive it directly from any compatible IDE or agent. See the engineering page for the install steps.