Hugpy Core
Core is the Flask console, API and fleet coordinator. It registers Wrapper hosts, mirrors their inventory and execution evidence into PostgreSQL, and routes work. Wrapper owns execution, loading, memory admission, worker settings and local model copies. Core uses Wrapper's reported feasibility; it does not run a second sizing solver. See model data ownership.
This source is staged 0.4.75. Source, prepared artifacts, registry releases and running services are separate states. No deployment is implied by this README.
Start and install
With the package and its dependencies installed and a prepared Core PostgreSQL
DSN in HUGPY_CORE_DB, the HTTP entry point is:
hugpy-core serve --host 127.0.0.1 --port 7020
Startup checks migrations and initializes Core services; use an isolated database
for development. serve uses the threaded Werkzeug server. A bare hugpy-core
uses the older Flask startup sequence with additional startup jobs.
The Debian package supplies an offline wheelhouse and invokes
hugpy-core install --system to provision PostgreSQL, migrate Core and install
Core/intake systemd units. This is a mutating installation action. Inspect the
bundle README and installer contract
for build prerequisites, DSN precedence and upgrade behavior. Installer verbs
without --system use a distinct per-user path.
Core currently depends on Wrapper, Storage, Abstract Toolserver and the shared Flask/database/utilities libraries as well as Flask, aiohttp, psycopg and Flask-Sock. Exact floors and optional extras are in pyproject.toml. Media and Video are optional: their distributions own their APIs and UI assets. Toolserver provisions databases; Core queries PostgreSQL directly.
API, UI and operations
- Operator guide: configuration, intake, optional apps, Identity readiness and verification boundaries.
- Documentation index: current contracts and historical designs.
- Route convention: category catalogs, explicit addon
blueprints and UI middleware.
/routesis not an exhaustive endpoint inventory. - Console source and component API: app and library builds.
- Intake deployment: independent collection and bounded model-fact exchange between registered workers.
The retired Basic aiohttp server, console and training extension are preserved in archive/basic-runtime, outside the installable package. The active Flask application uses native Core readers; the compatibility flag and Basic CLI dispatch were removed. Existing databases are not migrated or deleted merely by this source change.
Downloads and feature gallery
Get the Debian packages, architecture details, SHA-256 checksums and installation commands from Hugpy Downloads. The feature gallery shows the console, Agent, Station, Media and Video interfaces. Screenshots reflect the versions captured; the current interface may differ.
Compute resources
Model placement, GPU process usage, memory plans and per-model controls.
Worker model plans
Compare models, context windows and allocation modes across workers.
Inference metrics
Explore recorded model activity and throughput by worker.
Built-in documentation
Quickstarts and guides for models, workers, clients and integrations.
The Hugpy overview
The shared entry point for the console, media tools and fleet.
Fleet terminal compatibility release — 2026-10-22
Supports per-request alloc.workers selection in native chat, OpenAI chat and task routes. Selection is enforced before resident, allocation and wildcard ranking. The optional terminal extra selects the updated Fleet arm. The published UI bundle is retained.
1 maintainer
Metadata
1 maintainer
Release files for hugpy-core 0.4.74
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hugpy_core-0.4.74.tar.gz | 13.9 MB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hugpy_core-0.4.74-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 27.9 MB
Release files / hugpy_core-0.4.74.tar.gz
| Download URL | hugpy_core-0.4.74.tar.gz |
|---|---|
| Size | 13.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2d25112fabb80600c13a1cbb846526f8989d993edf3cf686be72009bfb480529
|
|
BLAKE2b-256 checksum How to use checksums |
2d4c6642020819c4d653711caee10f28a3a082bc99d7133c8e45617ea962e1cd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / hugpy_core-0.4.74-py3-none-any.whl
| Download URL | hugpy_core-0.4.74-py3-none-any.whl |
|---|---|
| Size | 14.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7102e42c7445ccf8ba311a62ddcab8b7fd9dd5cd5f474ca05d73e969cd474c74
|
|
BLAKE2b-256 checksum How to use checksums |
863fdf6dad9d5fb1588af859011ddd2629a95d3ac120ea269304ce44f7114b24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for hugpy-core 0.4.74
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
