Skip to main content

jammi-server

CPU build of the Jammi engine server, packaged as a pip-installable wheel that ships the compiled jammi-server binary behind a jammi-server console script.

pip install jammi-server
jammi-server --help

The wheel bundles a prebuilt Linux x86_64 binary (manylinux_2_28 glibc floor) compiled with the broker and cloud-storage backends. For GPU-accelerated inference and fine-tuning, install jammi-server-cu12 instead — it provides the same jammi-server command built against the CUDA backend.

Metadata

Release files for jammi-server 0.50.0

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

Built distributions (wheels)

Table of built distributions (wheels) for jammi-server 0.50.0
File Interpreter ABI Platform
jammi_server-0.50.0-py3-none-manylinux_2_28_x86_64.whl Python 3 none Linux glibc 2.28+ x86-64 Details
jammi_server-0.50.0-py3-none-manylinux_2_28_aarch64.whl Python 3 none Linux glibc 2.28+ ARM64 Details

Total release size: 197.6 MB

Release files / jammi_server-0.50.0-py3-none-manylinux_2_28_x86_64.whl

Download URL jammi_server-0.50.0-py3-none-manylinux_2_28_x86_64.whl
Size 102.5 MB
Tags Linux glibc 2.28+ x86-64 Python 3
SHA-256 checksum
How to use checksums
2795d78e5b7dbf98193a7898d603b5f894b66c9df2e506a9d1e860bca072e07e
BLAKE2b-256 checksum
How to use checksums
6ee909917a786023cef8684ce8f6e4f31e6a92b8b0a52f882cbad4dbbe6a59bb
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 Sep 29, 2026.

Transparency log

Release files / jammi_server-0.50.0-py3-none-manylinux_2_28_aarch64.whl

Download URL jammi_server-0.50.0-py3-none-manylinux_2_28_aarch64.whl
Size 95.1 MB
Tags Linux glibc 2.28+ ARM64 Python 3
SHA-256 checksum
How to use checksums
d562a493f76b6f4aeea84b5657f7fbd8a8c817d3748aff602fa1702609a3526d
BLAKE2b-256 checksum
How to use checksums
8c73e767a827f511c51cf52add4cb86883cd8dbb9c6d6ec578023ec7342ecfda
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 Sep 29, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.50.0 This release

2 release files

0.49.1

1 release file

0.49.0

1 release file

0.48.0

1 release file

0.47.0

1 release file

0.46.0

1 release file

0.45.0

1 release file

0.44.0

1 release file

0.43.0

1 release file

0.42.0

1 release file

0.41.0

1 release file

0.40.0

1 release file

0.39.0

1 release file

0.38.0

1 release file

0.37.0

1 release file

0.36.0

1 release file

0.35.0

1 release file

0.34.0

1 release file

0.33.0

1 release file

0.32.1

1 release file

0.32.0

1 release file

0.31.0

1 release file

0.30.0

1 release file

0.29.0

1 release file

0.28.0

1 release file

0.26.5

1 release file

0.26.4

1 release file

0.26.3

1 release file

0.26.2

1 release file

0.26.1

1 release file

0.26.0

1 release file

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