Kinetic
Run Keras and JAX workloads on cloud TPUs and GPUs with a simple decorator. No infrastructure management required.
import kinetic
@kinetic.run(accelerator="tpu-v5e-1")
def train_model():
import keras
model = keras.Sequential([...])
model.fit(x_train, y_train)
return model.history.history["loss"][-1]
# Executes on a TPU v5e-1 slice, returns the result locally
final_loss = train_model()
Why Kinetic
- Simple remote execution. A
@kinetic.run()decorator runs the function on the accelerator you ask for and returns the result. Nothing else changes about your code. - Detached jobs. Use
func.run_async()for long runs. You get aJobHandleback — poll status, tail logs, collect the result later, or reattach from another machine entirely. - Data and checkpoint support. Wrap inputs in
kinetic.Data(...)to ship local files (or stream from GCS) into the job. Write durable outputs and resumable checkpoints underKINETIC_OUTPUT_DIR.
Documentation
Comprehensive documentation is available at: https://kinetic.readthedocs.io
Install
uv pip install keras-kinetic
This installs the @kinetic.run() decorator and the kinetic CLI,
which provisions and manages infrastructure.
One-time setup
kinetic init
This detects your local environment, then either joins an existing Kinetic cluster in the project (your own or a teammate's — discovery goes through the shared state bucket) or walks you through creating a new one. It ends by saving a profile that becomes your active context — subsequent commands pick up project, zone, and cluster automatically.
Behind the scenes, the Create path runs kinetic up to enable APIs,
provision a GKE cluster with an accelerator node pool, and configure
local Docker / kubectl access. Run kinetic down when you're done.
Recommended first run
python examples/fashion_mnist.py
No environment variables needed — kinetic init set an active
profile. The first run takes ~5 minutes (it builds a container image
with your dependencies via Cloud Build). Subsequent runs with
unchanged dependencies start in under a minute.
For the full first-run walkthrough, see the Getting Started guide.
Where to go next
| Question | Where to look |
|---|---|
| How do I get my first job running? | Getting Started |
When should I use run_async() instead of run()? |
Detached Jobs |
| How do I ship data and persist outputs? | Data and Checkpointing |
| Bundled vs prebuilt vs custom image — which one? | Execution Modes |
| Something's broken; where do I start? | Troubleshooting |
Configuration
The recommended way to configure Kinetic is via a profile — the named
context that kinetic init creates and kinetic profile ls | use
manages. For ad-hoc overrides, every profile field also has a
KINETIC_* env-var equivalent (KINETIC_PROJECT, KINETIC_ZONE,
KINETIC_CLUSTER, KINETIC_NAMESPACE) and a matching CLI flag.
Precedence is: CLI flag > KINETIC_* env var > active profile >
built-in default.
The full surface — every variable, every CLI flag, and the profile model — lives in the Configuration reference.
Contributing
See the Contributing guide.
License
Metadata
Release files for keras-kinetic 0.0.4
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 | Actions |
|---|---|---|---|---|
| keras_kinetic-0.0.4.tar.gz | 308.6 kB | Without provenance | Details for keras_kinetic-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| keras_kinetic-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for keras_kinetic-0.0.4-py3-none-any.whl |
Total release size: 551.4 kB
Release files / keras_kinetic-0.0.4.tar.gz
| Download URL | keras_kinetic-0.0.4.tar.gz |
|---|---|
| Size | 308.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af658c897869ec2bba9b3b8cc77bb126c75d61fb54c74041aacab67bb1c8ed4c
|
|
BLAKE2b-256 checksum How to use checksums |
8dfb391a00099b862307730ccdb54d87583bd6c59de17013c6842b209456e5c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / keras_kinetic-0.0.4-py3-none-any.whl
| Download URL | keras_kinetic-0.0.4-py3-none-any.whl |
|---|---|
| Size | 242.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52a9ac385c8e51d8985b34fbb3497b497499fd9a099e6cdea6c1bcbe9d11ef96
|
|
BLAKE2b-256 checksum How to use checksums |
c36045a39e436566363b280914ac2438e0b1c5c78a341103cac648740837dc89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for keras-kinetic 0.0.4
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.