Deployment Bindings – Experimental Support
Automating deployments by linking pipelines directly to artifacts
Published on 21/08/2025 by igor.kolomiyets in Announcements

Today we are introducing experimental support for Deployment Bindings.

“Experimental” means the feature is available and supported, but it may change or be removed in future releases.

What is a Deployment Binding?

Since the beginning, artifactz.io has worked in push mode. Clients decide what to put into the artifactz.io registry and when to use it in their workflows.

In practice, this meant running a task or starting a pipeline to deploy an artifact. artifactz.io acted as the source of truth for which version was deployed.

With Deployment Bindings, you can connect a pipeline to an artifact at a specific stage. When an artifact is pushed to that stage, artifactz.io triggers the pipeline.

This allows deployments to happen automatically on push or rollback.

Which pipelines are supported?

Currently, three types of pipelines are supported:

  • GitOps (e.g., ArgoCD)artifactz.io updates version details in deployment manifests
  • Jenkins
  • GitHub Actions

Pipelines are triggered by agents running in the artifactz.io stack. This requires your pipeline to be accessible from the internet.

What if my environment is not internet-accessible?

You can use self-hosted agents in your own environment.

Create an agent pool and link your Deployment Bindings to it. Self-hosted agents support both gRPC and HTTP communication.

Next steps

We will publish detailed instructions on our blog showing how to configure and use Deployment Bindings in your workflows.