Documentation | Console | Example Gallery
Tilebox Workflows
Tilebox Workflows, or the Tilebox workflow orchestrator is a parallel processing engine that allows an intuitive creation of dynamic tasks that can be parallelized out of the box and executed across compute environments or on-premise as well as in auto-scaling clusters in public clouds.
Quickstart
Install using pip:
pip install tilebox-workflows
For interactive job progress in Jupyter notebooks, install tilebox-workflows[notebook].
Without this extra, jobs use their plain-text representation.
For S3 client type information, install boto3-stubs[s3] in your development environment.
Create a task:
from tilebox.workflows import Task
class MyFirstTask(Task):
def execute(self):
print("Hello World from my first Tilebox task!")
Submit a job
from tilebox.workflows import Client
# create your API key at https://console.tilebox.com
client = Client(token="YOUR_TILEBOX_API_KEY")
jobs = client.jobs()
jobs.submit("my-very-first-job", MyFirstTask())
And run it:
runner = client.runner(tasks=[MyFirstTask])
runner.run_all()
Concurrent worker execution
A worker runtime can execute multiple tasks concurrently in one Python process. Each execution receives a newly
deserialized task instance and its own ExecutionContext, including task-local subtask and progress state. The
RunnerContext, configured JobCache, and any class or module state are process-level resources shared by those
executions.
Custom runner contexts, caches, and shared task state must therefore support concurrent access from multiple threads. Asynchronous task executions may also run on different event loops. Configure and register these resources before the worker starts; do not mutate runner configuration while tasks are executing. Compound cache operations are not atomic unless the cache implementation explicitly provides that guarantee.
Concurrency in one runtime avoids repeated process initialization and allows overlapping I/O or native code that releases Python's GIL. CPU-bound Python code still needs multiple runtime processes for parallel execution.
Reading automation objects
Storage-event tasks can read objects from Amazon S3, Google Cloud Storage, Azure Blob Storage, or the local filesystem:
content = self.trigger.storage.read(self.trigger.location)
The method returns bytes. Cloud reads use the credentials configured for the runner.
On macOS, GCS or Azure CLI authentication can emit gRPC fork diagnostics even when a read succeeds. These messages alone do not indicate a failed read; do not downgrade gRPC to hide them.
Documentation
Check out the Tilebox Workflows documentation for more information.
License
Distributed under the MIT License (The MIT License).
2 maintainers
Metadata
2 maintainers
Release files for tilebox-workflows 0.63.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 | |
|---|---|---|---|
| tilebox_workflows-0.63.1.tar.gz | 117.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tilebox_workflows-0.63.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 273.2 kB
Release files / tilebox_workflows-0.63.1.tar.gz
| Download URL | tilebox_workflows-0.63.1.tar.gz |
|---|---|
| Size | 117.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
133847ef91cd5831a4c56666d5aa156759a1527a5a06e7fa596ab2854714beb9
|
|
BLAKE2b-256 checksum How to use checksums |
edccee11013f7029772d54f617b808e6d678035f75aace9e67a1d8de7d78388d
|
| 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 Oct 3, 2026.
Transparency logRelease files / tilebox_workflows-0.63.1-py3-none-any.whl
| Download URL | tilebox_workflows-0.63.1-py3-none-any.whl |
|---|---|
| Size | 156.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f9f999303ea7f8ee7963a59d5247549d4dcc7260117452e12a04962447e8d775
|
|
BLAKE2b-256 checksum How to use checksums |
05600fd5146bac9af36e130dd100d21a2a5067611eae2d101943b1730712cbff
|
| 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 Oct 3, 2026.
Transparency log
