Skip to main content

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 and the fleet execution direction.

The package metadata defines the source version. Check the installed distribution and running service separately when diagnosing an installation.

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.

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

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.

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.

Compute resources

Worker model plans

Compare models, context windows and allocation modes across workers.

Worker model plans

Inference metrics

Explore recorded model activity and throughput by worker.

Inference metrics

Built-in documentation

Quickstarts and guides for models, workers, clients and integrations.

Built-in documentation

The Hugpy overview

The shared entry point for the console, media tools and fleet.

The Hugpy overview

Metadata

Release files for hugpy-core 0.4.81

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hugpy-core 0.4.81
File Size Uploaded Provenance Actions
hugpy_core-0.4.81.tar.gz 5.7 MB Without provenance Details for hugpy_core-0.4.81.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hugpy-core 0.4.81
File Interpreter ABI Platform Actions
hugpy_core-0.4.81-py3-none-any.whl Python 3 none any Details for hugpy_core-0.4.81-py3-none-any.whl

Total release size: 11.5 MB

Release files / hugpy_core-0.4.81.tar.gz

Download URL hugpy_core-0.4.81.tar.gz
Size 5.7 MB
Tags Source
SHA-256 checksum
How to use checksums
1ae004a9dafb0b1663bacd83f8e777e91f581cf9f1767ae64e56c23eec01c544
BLAKE2b-256 checksum
How to use checksums
0a9b8c776d8e7d64fc6b0312764b89801291fbff6d678400410b335f4a6e928f
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.81-py3-none-any.whl

Download URL hugpy_core-0.4.81-py3-none-any.whl
Size 5.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
85dc5227e84f2fb09f762d5b196cfab97c04f01c7fcc32d4afb7456001432d27
BLAKE2b-256 checksum
How to use checksums
ad582474e753b8a8b581f57b2ecbaf1f9ce66fd2bef629274592c84b98355753
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.81

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.

Release history Release notifications | RSS feed

This release

0.4.81 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page