GitHub • LinkedIn • X • Discord
Telekinesis Deployment
Telekinesis Deployment provides the installation tooling and backend delivery workflows for the Telekinesis platform.
It includes:
- Cloud deployment to Amazon EKS using Helm
- Local, single-node, and evaluator deployment using Docker Compose
- A command-line interface for installing and managing Telekinesis services
- Shared configuration, health checks, licensing, and provisioning utilities
Release Model
Telekinesis Deployment is currently in active development (pre-1.0). Features and interfaces may evolve between minor releases. Use the version specified by the Telekinesis development team for production deployments.
Installation
-
Install Miniconda or another Python environment manager.
-
Clone this repository:
git clone -b develop https://gitlab.com/telekinesis/deployment.git cd deployment
-
Create and activate a supported Python environment:
Telekinesis Deployment supports Python 3.11 and 3.12.
conda create -n telekinesis-deployment python=3.11 conda activate telekinesis-deployment
-
Install the CLI and its dependencies in editable mode:
pip install -e .
-
Verify the installation:
telekinesis server --help
Example
Initialize a local deployment and start its services:
telekinesis server init
telekinesis server install
telekinesis server status
Use telekinesis server init --profile developer to initialize a developer
environment. Run telekinesis server --help to see all available commands.
Deployment Modes
| Mode | When to use |
|---|---|
| Cloud deployment | Deploy backend services to Amazon EKS with Helm |
| Compose deployment | Run the backend locally, on a single server, or for evaluator installations |
Resources
Support
For issues and questions, contact the Telekinesis development team at support@telekinesis.ai or join the Telekinesis Discord.
License
This repository is proprietary and confidential. See LICENSE.txt for details.
Metadata
Release files for telekinesis-deployment 0.0.1
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 |
|---|---|---|---|---|
| telekinesis_deployment-0.0.1.tar.gz | 31.1 kB | Without provenance | Details for telekinesis_deployment-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| telekinesis_deployment-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for telekinesis_deployment-0.0.1-py3-none-any.whl |
Total release size: 69.7 kB
Release files / telekinesis_deployment-0.0.1.tar.gz
| Download URL | telekinesis_deployment-0.0.1.tar.gz |
|---|---|
| Size | 31.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
22d22e811b5f3f25bb976e6524513864f6b62fef3d176644ddfd20d9401c38b6
|
|
BLAKE2b-256 checksum How to use checksums |
83717680014443a3127b9614ff4c014c20dfd5d3c170f0382fa5229104d1ac5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / telekinesis_deployment-0.0.1-py3-none-any.whl
| Download URL | telekinesis_deployment-0.0.1-py3-none-any.whl |
|---|---|
| Size | 38.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a0f5b6749856010ad00c3794dad05e04e61fb18375b9e71faef5ee5f6a20209d
|
|
BLAKE2b-256 checksum How to use checksums |
3ea14b4b4cb4a0ce2a03c50974c73dd7c7488838033aea5c6b1e95b2ab7e39e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for telekinesis-deployment 0.0.1
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.