A previous release had provenance metadata, but this release does not. 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.72rc101
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| truss-0.9.72rc101.tar.gz | 307.9 kB | Without provenance | Details for truss-0.9.72rc101.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| truss-0.9.72rc101-py3-none-any.whl | Python 3 | none | any | Details for truss-0.9.72rc101-py3-none-any.whl |
Total release size: 720.5 kB
Release files / truss-0.9.72rc101.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | truss-0.9.72rc101.tar.gz |
|---|---|
| Size | 307.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
75596a5a4a2d72e89a59ec1e0bb988c19105ce308f8ffb15a66d0cff521d0e63
|
|
BLAKE2b-256 checksum How to use checksums |
49563b1f8e5b17b9c8ed761581d19fae700b3b81a5f836b518c7ea3d699a5879
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.0 CPython/3.11.0 Linux/6.8.0-55-generic
|
Release files / truss-0.9.72rc101-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | truss-0.9.72rc101-py3-none-any.whl |
|---|---|
| Size | 412.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c1e110a80b97edf4d8ccb768925664c657245b75c1651719d2fdde5845f714f1
|
|
BLAKE2b-256 checksum How to use checksums |
77fd0fbfe844a8bb5bbac5e4315b02ed36ab8b56dcfaea76d8275f0ba4890e0c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.0.0 CPython/3.11.0 Linux/6.8.0-55-generic
|
Security for truss 0.9.72rc101
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.9.72rc1 2 files With provenance
- Added 0.9.72rc101 2 files Without provenance
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.
