BARRYBARRY

Developers

Transports as version-controlled YAML.

Describe pipelines as clear, name-based YAML and manage them in your own Git repository.

A pipeline built by clicking is hard to review, hard to promote and hard to reconstruct after someone leaves. BARRY adds config-as-code as a layer over the same runtime, so nothing is given up to gain it. Transports, connections and firewall rules can be described as readable YAML that lives in your own Git repository, referenced by name rather than by internal identifier. One repository with a branch per environment gives you the usual workflow: propose a change, review the diff, promote it forward. Promotion is selective, so a change to one transport does not drag everything else with it, and you can see the resulting graph before applying anything. Secrets never enter the repository.

  • Human-readable, reviewable YAML definitions
  • One repository, a branch per environment
  • Selective, upstream-friendly promotion
  • Diff and graph the change before you apply it
  • Secrets stay as references, never in the repo
Reviewable
Pipelines go through the same review as code.
Promotable
Dev to prod without click-by-click rebuilds.
Secret-safe
Vault references, never literals.

Ready to unlock your data?

See how BARRY brings your on-premises data to the cloud — safely, and on your terms.