hephkit

Stop setting up.
Start building.

Hephaestus is the kit every NeoForge project is built from: one correctness core for money, hashing, signatures and errors, and a local stack that comes up with one command. You write the part that is actually yours.

uv add hephkitPython 3.12+. The CLI is a separate install.

hephkit on PyPI · spec v0.3.0 · MIT · every module experimental

What you get instead of a week of setup

Money that cannot quietly lose a cent
Integer minor units end to end, strict ASCII parsing that refuses excess precision, and the full ISO 4217 table generated from its published source. Floating point never touches an amount. Pinned by the specification and shared conformance vectors, not by one language’s tests.
Errors with an address
Every failure carries a code from one registry and a type URL that resolves to a page explaining it — 12 of them, all documented. The wire format is a MUST in the spec, so a client can rely on it across every language in the kit.
One core, bound everywhere
The hard parts live once, in Rust that does no I/O and never panics on input. Python binds to it, Go calls it, and nothing is hand-ported between languages — so the three cannot disagree about what a rounded split or a canonical hash is.
A local stack, not a wiki page of prerequisites
Postgres, Redis, object storage, mail and the full telemetry pipeline are Compose fragments you switch on per project. Traces, metrics and logs are already wired to the same conventions.

What is actually built

The kit is in Phase 1 of seven. This is the whole inventory, read from the registry the code is checked against — not a highlight reel.

Runs today21

Compose
mailobjectspostgresredisstripetelemetry
Images
nodepython
Go
clicomposefragmentshephingot
Python
errorshashingmoneyobservabilitysettingssignatures
Rust
hephkit-corehephkit-py

Not yet9

Phase 2
authidempotency
Phase 3
lab.repro
Phase 4
billingledgeroutboxregistrywebhooks
Phase 5
heph new

Every module above is experimental: usable, not yet promised. Nothing reaches stable without the coverage gate, two production projects and passing ecosystem CI — the criteria in ADR 0015. The planned column lists the headline modules per phase, not the full scope; the roadmap has that.

Where it is going

  1. 1Core and local stackyou are here
  2. 2Product core
  3. 3Research core
  4. 4Money movement, UI and product AI
  5. 5Infrastructure, the CLI and ML infra
  6. 6Adapters
  7. 7Second consumers

Start

uv add hephkit
go install github.com/Neoforge-Labs/hephaestus/go/cmd/heph@latestThe heph CLI, for the local stack.

Then read the docs, or go straight to the specification if you would rather see the contract before the prose.