Jetstack supports two related public-entry mechanisms:
These are tenant-managed definitions that can point to URLs, public modules, public canvases, webhooks, or route payloads.
They allow a tenant to expose controlled entry points without modifying core application code.
A permanent link can represent:
Permanent links are useful when you need a stable reference that can be shared or embedded.
Tenant routes add:
They are useful when public entry should look like a deliberate tenant endpoint rather than a random generated link name.
Links and routes often depend on:
That means link design should be coordinated with module and canvas exposure decisions.
Webhook targets can also be modeled through links and routes. This makes the link system part of the integration story, not just a navigation convenience.