What is Service Artifact Registry & Extension Runtime?
When a built-in service integration isn’t enough, the Extension Runtime lets you upload your own code without touching the platform’s own runtime. Every uploaded artifact goes through deterministic validation and scanning, is versioned and checksummed in the Service Artifact Registry, and executes in a separate runner process — isolated, deployable, and rollback-able independently of the core platform.
- Upload, validate, version, and publish JAR extensions with no-classload static validation before anything runs
- Isolated execution in a dedicated runner process — uploaded code never runs inside the main platform JVM
- Deploy / invoke / undeploy / rollback lifecycle with per-tenant isolation
- Provider registration so custom extensions plug directly into SERVICE_CALL flow steps