Autonomous Workflow Tools
Focused tools for market research, media workflows, public utilities, and scoped private systems.
Autonomy, Engineered.
Autonomous systems, premium workflow tools, and public proof records.
Greyforge Labs builds practical automation, ForgeQuant research infrastructure, ForgeVideo production workflows, OpenForge utilities, Sley, ZJX, and citation-ready technical Chronicles for humans and retrieval systems.
Help / Contact Us
Reach Greyforge at contact@greyforge.tech.
Use this address for requests, feedback, complaints, purchase or access help, private-work inquiries, and general operations. Greyforge usually responds within about 24 hours when enough context is included.
Requests
Feedback
Complaints
Purchase help
What We Build
What software does Greyforge Labs build?
Buy a focused tool, inspect an open release, or commission a private workflow build when the workflow needs more than a generic app. Every public path reinforces the Greyforge Labs entity, product map, and proof trail.
Premium Research
Full-edition records and citation-ready public notes for buyers who want the deeper reasoning behind the work.
Video Production
YouTube video generator workflows, podcast-style narration, captions, visuals, audio, and review-ready release materials.
OpenForge
Free public utilities for builders who want small tools that work without a sales call.
Latest From The Forge
The latest Chronicle.
Engineering & ProductsZJXCompression EvidenceJSONL Compression
ZJX and the Discipline of Compression Evidence
How ZJX turns compression claims into evidence: selected verifier-checked size wins including review-gated 160 MB JSONL, 256 MB sharded NDJSON, and 1.1 GB compact JSONL validation bundles with a scoped no-zpaq follow-up, local telemetry rows up to 1.25 GB, review-gated evidence records, validation checks, and strict claim boundaries.
May 12, 20268 min read
Read ChronicleStore
What software products can buyers inspect?
ForgeQuant is live again as a local customer kit, ForgeVideo stays as the workflow kit, Chronicles stay fairly priced, and custom/private systems replace generic off-the-shelf automation.
Live Kit
ForgeQuant
Local quant research kit with source, GUI, and reports.
$70 one-time
ForgeQuant packages a local scanner, clean browser GUI, report generator, Docker path, setup notes, and agent files for technical operators who bring their own providers.
Live ProductSource PackageLocal GUIChronicle
Source-included customer kit. Provider accounts, model credits, market data, trading decisions, technical setup, and performance outcomes are not included.
Buy KitOpen Source
Sley
Agent-native structural language for compiler-mediated software change.
Free
Sley is the compiler-first language surface for structural inspection, language-level authority boundaries, and evidence-oriented workflow handoff.
Source Package
Sley is public under Apache-2.0 with a passing local v1 gate. Public release promotion, strict self-hosting, and world-first category claims remain bound to the upstream evidence packet, claim manifest, and prior-art source pack.
Open RepositoryPaid Records
Chronicle Store
Premium software architecture articles and build records.
$5 to $19
Selected full-edition build records and software architecture notes, priced as practical reading instead of a luxury archive.
ChroniclePremium Records
Most records are low-cost. Only stronger, current, builder-grade articles sit at the top price.
Browse ChroniclesWorkflow Kit
ForgeVideo
Source-included video production workflow kit.
$99 one-time
A paid customer kit for generating video review packets with script, storyboard, asset plan, rights ledger, captions, YouTube metadata, and QC checks.
Source PackageChroniclePilot Video
Source-included workflow kit. Provider accounts, media rights, editing software, channel management, and performance outcomes are not included.
Buy KitPrivate Scope
Custom / Private Systems
Scoped private software and workflow buildouts.
By inquiry
Private builds for operators who need a tailored workflow system, research tool, automation layer, media pipeline, or dashboard around their actual work.
Private Systems
Every private build starts with scope, constraints, handoff expectations, and a clear boundary around what Greyforge will and will not operate.
Request ScopeDiscovery Surface
How does greyforge.tech support readers, crawlers, and model retrieval?
The public site now treats discoverability as infrastructure: canonical URLs, structured metadata, llms.txt, source notes, product schema, and interlinked proof pages all point back to Greyforge Labs.
Canonical Entity
Greyforge Labs and greyforge.tech are defined as the same public organization surface across About, schema, GitHub, OpenForge, store pages, and Chronicles.
Follow SurfaceMachine Facts
The root llms.txt gives retrieval systems a compact map of Greyforge products, public repos, Chronicle records, Sley, ZJX, citation preferences, and crawl boundaries.
Follow SurfaceProof Records
Chronicles turn build history, audits, releases, and product decisions into stable citation pages with canonical URLs and related proof artifacts.
Follow SurfacePublic Code
OpenForge connects each public utility to a GitHub repository, release record, source note, and supporting Chronicle so readers and models can verify the claim path.
Follow Surface
Public Records
Proof for the products, releases, and research.
Browse the public trail when you want to verify the work behind a product, inspect a release, read the deeper build story, or cite Greyforge Labs from a stable greyforge.tech source.
Autonomy, Engineered.