Foundation

One foundation under everything you build.

Tray iPaaS and Tray Helix run on the same repository, artifacts, credentials, and access control, so governance, security, and reuse are consistent across both products, not reinvented per tool.

See the platform

Built as one, not bolted together

Two products. One set of rules underneath.

Most stacks govern integration, automation, and the apps teams build with AI as separate systems, each with its own store, its own secrets, and its own access model. Tray iPaaS and Tray Helix share one Foundation instead. Whatever your teams build, it lives in the same repository, ships the same artifacts, authenticates through the same managed credentials, and answers to the same access control.

Repository

One versioned home for every workflow, agent, and app built across Tray iPaaS and Tray Helix. Branch, review, and roll back with a full history, not scattered exports and one-off scripts.

Artifacts

The built outputs (workflows, connectors, agents, and apps) packaged and versioned so the same thing that passed review is what ships, and can be promoted across environments reliably.

Credentials

Authentication managed once, centrally. Every product and every deployed app inherits managed credentials instead of hardcoding secrets. Rotate in one place, with nothing baked into code.

Access control

One access model across both products. Decide who can build, deploy, and govern, and scope what each app and user can reach, so the same policy holds whether work runs in iPaaS or Helix.

What it powers