The repository or configuration that created this release differ from a previous release. View details.
This release is a pre-release and may not be stable for production use.
Truss
The simplest way to serve AI/ML models in production
Why Truss?
- Write once, run anywhere: Package and test model code, weights, and dependencies with a model server that behaves the same in development and production.
- Fast developer loop: Implement your model with fast feedback from a live reload server, and skip Docker and Kubernetes configuration with a batteries-included model serving environment.
- Support for all Python frameworks: From
transformersanddiffuserstoPyTorchandTensorFlowtoTensorRTandTriton, Truss supports models created and served with any framework.
See Trusses for popular models including:
- 🦙 Llama 2 7B (13B) (70B)
- 🎨 Stable Diffusion XL
- 🗣 Whisper
and dozens more examples.
Installation
Install Truss with:
pip install --upgrade truss
Quickstart
As a quick example, we'll package a text classification pipeline from the open-source transformers package.
Create a Truss
To get started, create a Truss with the following terminal command:
truss init text-classification
When prompted, give your Truss a name like Text classification.
Then, navigate to the newly created directory:
cd text-classification
Implement the model
One of the two essential files in a Truss is model/model.py. In this file, you write a Model class: an interface between the ML model that you're packaging and the model server that you're running it on.
There are two member functions that you must implement in the Model class:
load()loads the model onto the model server. It runs exactly once when the model server is spun up or patched.predict()handles model inference. It runs every time the model server is called.
Here's the complete model/model.py for the text classification model:
from transformers import pipeline
class Model:
def __init__(self, **kwargs):
self._model = None
def load(self):
self._model = pipeline("text-classification")
def predict(self, model_input):
return self._model(model_input)
Add model dependencies
The other essential file in a Truss is config.yaml, which configures the model serving environment. For a complete list of the config options, see the config reference.
The pipeline model relies on Transformers and PyTorch. These dependencies must be specified in the Truss config.
In config.yaml, find the line requirements. Replace the empty list with:
requirements:
- torch==2.0.1
- transformers==4.30.0
No other configuration is needed.
Deployment
Truss is maintained by Baseten, which provides infrastructure for running ML models in production. We'll use Baseten as the remote host for your model.
Other remotes are coming soon, starting with AWS SageMaker.
Get an API key
To set up the Baseten remote, you'll need a Baseten API key. If you don't have a Baseten account, no worries, just sign up for an account and you'll be issued plenty of free credits to get you started.
Run truss push
With your Baseten API key ready to paste when prompted, you can deploy your model:
truss push
You can monitor your model deployment from your model dashboard on Baseten.
Invoke the model
After the model has finished deploying, you can invoke it from the terminal.
Invocation
truss predict -d '"Truss is awesome!"'
Response
[
{
"label": "POSITIVE",
"score": 0.999873161315918
}
]
Truss contributors
Truss is backed by Baseten and built in collaboration with ML engineers worldwide. Special thanks to Stephan Auerhahn @ stability.ai and Daniel Sarfati @ Salad Technologies for their contributions.
We enthusiastically welcome contributions in accordance with our contributors' guide and code of conduct.
7 maintainers
Metadata
7 maintainers
Release files for truss 0.9.106rc101
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| truss-0.9.106rc101.tar.gz | 336.4 kB | With provenance | Details for truss-0.9.106rc101.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| truss-0.9.106rc101-py3-none-any.whl | Python 3 | none | any | Details for truss-0.9.106rc101-py3-none-any.whl |
Total release size: 786.6 kB
Release files / truss-0.9.106rc101.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | truss-0.9.106rc101.tar.gz |
|---|---|
| Size | 336.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
35ffa01804f99c2289ab13d35a120cbe1f15b8fac7ec5e21534b3f63fc26ab7b
|
|
BLAKE2b-256 checksum How to use checksums |
d1a3527e95c93e7bbfa1fce65bd869d709cb768dce4d4f1f830ccde3fec70b32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 18, 2025.
Transparency logRelease files / truss-0.9.106rc101-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | truss-0.9.106rc101-py3-none-any.whl |
|---|---|
| Size | 450.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ec44315d509af7748879b0abccbd9f7dab789b72ddc248fa6a94d4933e963c92
|
|
BLAKE2b-256 checksum How to use checksums |
05103570f3f2a5e07b5cb5ca032548cd42a4b81a7bb461af47783f3892377fb3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Jun 18, 2025.
Transparency logSecurity for truss 0.9.106rc101
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.
Change of provenance
The configuration that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Attestation for truss-0.9.106rc101.tar.gz
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 Jun 18, 2025.
Transparency logA 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.
