This release is a pre-release and may not be stable for production use.
Prehnite
Local-first, quality-gated visual asset production. No mandatory SaaS or platform fees.
Source and project README · Roadmap · Changelog · Issues
Prehnite is an MIT-licensed Python CLI and optional MCP integration for batch image generation, masks/cutouts, technical validation, targeted repair, stateful replay, quality evidence, and reproducible export. It orchestrates image models; it does not include model weights, a photorealistic image generator, or a subscription service.
Quick start: no-cost local test
Requires Python 3.11 or later.
python -m pip install prehnite
prehnite init --destination my-first-batch
prehnite doctor
prehnite --help
The init command creates local starter configuration, but does not run model inference or incur fees. For a sample batch, follow the source repository's two-minute demo.
For a sample zero-cost batch, follow the up-to-date project README and onboarding guide.
What is actually implemented
- CLI, strict manifest/profile validation, stage journal, bounded attempts and safe archive/export paths.
- Offline synthetic demo flow, reports and reproducible zero-cost validation.
- Experimental local ComfyUI adapter and opt-in
prehnite-microrecipe binding with immutable batch identity. You must separately install ComfyUI and supply licensed checkpoints and compatible graphs. No real GPU model/cutout quality or 4K VRAM tier is certified. - Optional paid inference connectors require explicit operator-selected profiles, permissions and budgets. Installing Prehnite does not authorize any cloud uploads or paid API calls.
prehnite-macrois currently a read-only workflow blueprint, not an installed or benchmarked high-quality image pipeline.
See the implementation/evidence roadmap, recipe contract and public release history.
Release quality and licensing
The initial 0.1.0 alpha is an early developer preview, not production certified. Passing synthetic CI does not prove realistic image quality, legal rights to separate checkpoints, accepted cutout accuracy, stable public APIs or physical GPU suitability.
Prehnite code: MIT. Checkpoint weights, providers and third-party assets are governed by their own licenses and usage terms. The package contains no bundled checkpoint/model weights.
Metadata
Release files for prehnite 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| prehnite-0.1.0a1.tar.gz | 126.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| prehnite-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 271.1 kB
Release files / prehnite-0.1.0a1.tar.gz
| Download URL | prehnite-0.1.0a1.tar.gz |
|---|---|
| Size | 126.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d2eb9e662933b334e6be55b449850ec04b2bcbe29db810b74bec6167c549e4c2
|
|
BLAKE2b-256 checksum How to use checksums |
e3e541ab312f6b13e75247d30d68543514b45bccbbc07170099edae77dcf1696
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 17, 2026.
Transparency logRelease files / prehnite-0.1.0a1-py3-none-any.whl
| Download URL | prehnite-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 144.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
098560a9de1c06afa01a605c5a7d8d3a02f3197a0c00c2e9fbba8914f6637908
|
|
BLAKE2b-256 checksum How to use checksums |
a33f62a29353ff081fa83f4f8384e799628176ce365a452dceeb308c89f387eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 17, 2026.
Transparency log