One typed call instead of a pile of integration glue.
Junctree is a versioned, multi-tenant runtime for the third-party integrations your product depends on. You author an integration once as a junction, test it step by step, promote it through a lifecycle, and call it from your app with a single authenticated request. Junctree owns the credentials, the contracts, and the version history — so your codebase stops carrying scattered SDKs and brittle glue.
Versioned by default
Every junction has immutable versions and a clear lifecycle. Exactly one version is live in production at a time, and promotions are atomic — so rollouts and rollbacks are a pointer move, not a redeploy.
Test before you ship
Run any step in isolation against real config, with no production impact. Promote
draft → testing → published
only once it behaves.
Credentials stay server-side
Configuration and secrets are injected by the runtime at execution time. Your callers never see a vendor key, and secrets are encrypted at rest when you opt in.
Multi-tenant cascade
Settings cascade down a principal hierarchy — platform, organization, sub-account — so a shared integration can be reconfigured per tenant without forking the junction.
The shape of a junction
A junction is a small, typed workflow. A trigger is its entry point; an ordered list of steps does the work, each step's output flowing into the next. Read the vocabulary or see how a run works.
POST /api/v1/execute
Authorization: Bearer jt_org_…
{
"junction": "acmefx.quote",
"trigger": "default",
"input": { "base": "USD", "quote": "EUR", "amount": 100 }
}