Available
ForgeShield
$9 one-time
One-time exposure map that ranks public clues, cleanup priorities, and what to scrub or escalate before removal work starts.
Order Map
Autonomy, Engineered.
Greyforge Labs
A public workbench for software products, open utilities, technical Chronicles, and governed media systems.
Greyforge is built around a simple operating rule: absorb the complexity inside disciplined systems, then expose only the interface, proof, and boundaries a user can trust.
ProductsPaid software and service surfaces with clear scope, limits, and delivery boundaries.ChroniclesTechnical records that explain what was built, why it matters, and what changed.OpenForgePublic utilities released when a private pattern becomes useful outside the forge.Trust SurfacePrivacy doctrine, security audits, public proof notes, and boundary-setting records.
Operating Thesis
Greyforge is a builder system with a public edge.
The public site is not only a brochure. It is the inspectable edge of a working forge: finished products in the store, open utilities in OpenForge, and technical records in the Chronicles.
Each surface has a different job. Products should solve a narrow problem cleanly. OpenForge should release small tools that stand on their own. Chronicles should preserve the reasoning, proof, and consequences behind the work.
The private side stays private where it should: runtime details, credentials, internal machine topology, customer data, and methods that would create avoidable risk if published. The public side should still give a serious reader enough evidence to decide whether the work is real.
Public Surfaces
What leaves the forge.
Greyforge ships commercial products, source packages, open utilities, and proof records. The shared standard is the same: narrow scope, visible limits, and links back to the relevant context.
Licensed Package
ForgeStrike
$29 one-time
Licensed self-hosted customer kit for data broker opt-out workflow planning after ForgeShield shows what deserves action first.
Buy PackageStock Scanner
ForgeQuant
$199 one-time
Stock market research software that scans a watchlist and surfaces candidates worth a closer look.
Buy ScannerFinal Deck
Agent Cards
$19 to $399
Final collectible role kits with approved card art, ability scores, rarity pricing, and the full-power Complete Forge Deck.
Browse CardsPackage Deal
Chronicle Package
$149 package
One lifetime package unlock for the current premium full-edition Chronicle set, with research value estimates for every included article.
View PackageComing Soon
ForgeVideo
$599 suggested
Coming-soon autonomous YouTube production pipeline that turns a prompt into a governed review package with script, narration, visuals, captions, audio, and QC.
Preview PipelineCustom Engagement
ForgeClaw
By inquiry
Private autonomous operations stack offered as a custom engagement for serious operator workflows and infrastructure design.
Discuss Build
Proof Trail
The work should point to its record.
Chronicles are the long-term memory of Greyforge public work. Some are fully open. Some are premium records with public teaser pages. The important part is that each one routes through the public Chronicle surface first.
Operating system history
Factory Fabric
How code, media, documentation, review, and release work became one controlled production fabric.
Read recordPremium operator edition
Vault Lattice
A paid operator record with the deeper lattice architecture behind the public doctrine.
Read recordPremium builder dossier
Harness Reliability
Reliability treated as a harness property: task contracts, tool boundaries, traces, and verification.
Read recordPublic alignment note
Retiring the Fork
Why ForgeClaw became a private engagement surface while public alignment moved through OpenForge.
Read recordCouncil Model
Specialist roles, one accountable surface.
Greyforge uses named specialist roles for architecture, implementation, review, content, doctrine, and scrub work. The names are part of the house language, but the important point is operational: work is routed to the role that can judge it best.
The public record follows the same shape. Product pages state scope. OpenForge pages link repositories and releases. Chronicle pages preserve the technical arc and the public proof trail.
Merlin
Implementation
Turns scoped work into production code, refactors, and shipped changes.
Nabu
Architecture
Plans systems, migrations, tradeoffs, and technical direction before buildout.
Vulcan
Quality
Reviews risk, tests behavior, and hardens systems before public release.
Seshat
WebForge
Keeps Chronicles, paywall routes, public proof, and site discoverability coherent.
Maat
Doctrine
Checks public artifacts against house rules, privacy boundaries, and intent.
Argus
Scrub
Looks for secrets, license risk, and unnecessary exposure before work leaves the forge.
Boundaries
Public when useful. Private when exposure would create risk.
Greyforge publishes evidence without publishing secrets. The line is deliberate: useful context, clear constraints, no unnecessary operational detail.
Privacy Doctrine
Why exposure tools must respect local control, minimal retention, and clear user ownership.
Read boundaryAdversarial Protocol
A public look at structured debate, source discipline, and decision stress-testing.
Read boundaryPicoClaw Audit
A defensive audit record showing how Greyforge writes public proof without leaking private mechanics.
Read boundaryFor the commercial rules, read the Terms. For data handling, read the Privacy Policy.
Start Here
Choose the public surface that matches the job.
Read a technical record, inspect an open utility, browse the product catalog, or contact Greyforge directly for private work.