Deployment Process
When you click Deploy, Archway runs through several steps automatically:
Save — Any unsaved changes are saved first
Security Review — Your code is scanned for vulnerabilities
Critical issues block deployment entirely
High severity issues show a warning — you can choose to deploy anyway
Medium/Low issues are informational only
Secret Validation — All linked secrets must have values (no pending secrets allowed)
Limit Check — Your organization must have available bridge slots
Approval Check — If your org requires admin approval and you're not an admin, the bridge enters Pending Approval status instead of going live
Deployment — A version snapshot is created, an API key is generated (first deploy only), and the bridge goes Active
After Deployment
Once deployed, your bridge receives:
An endpoint URL where it can be invoked via HTTP
An API key for authentication (shown once — save it!)
A webhook URL for webhook-triggered bridges
Redeployment
If you make changes to an already-active bridge, the Deploy button changes to "Redeploy". Redeploying preserves your existing API key and webhook token — no need to update client configurations.
Deploy Approval Workflow
If your organization has enabled "Require admin approval for deploys" in Settings:
Admin users can deploy directly — no approval needed
Non-admin users (SEs, Viewers) will see the bridge enter Pending Approval status
An admin can then Approve (triggers the real deployment) or Reject (reverts to Draft with an optional reason)
The rejection reason is shown on the bridge detail page so the SE knows what to fix