Build & Run Agents·production

IAM.Hosting

Serverless runtime and lifecycle management for hosted agents in Kubernetes.

Landing Application
IAM.Hosting interface
Current public IAM.Hosting surface. The screenshot was verified when the documentation was published.

Key capabilities

  • Scale-to-zero agent workloads
  • Execution isolation and scoped credentials
  • Wake, reap, quota and runtime-health lifecycle

Role in the ecosystem

IAM.Hosting turns the published AgentPackage into a managed runtime session based on the Rust engine iam-agent and Kubernetes. The service is responsible for launching isolation, health, quotas, stopping idle workloads and sending the result back in Marketplace.

Execution life cycle

install → wake → hydrate scoped config → execute → persist result → reap

A user request wakes up a workload or creates a new instance. Runtime gets the required version of the package and links to allowed credentials, publishes running state, and after a period of inactivity is scaled to zero.

Isolation and data

  • separate identity and resource envelope for launch;
  • prohibition of undescribed capabilities and network directions;
  • secrets are mounted only during execution;
  • logs should not contain credential material;
  • user artifacts are saved separately from the ephemeral container.

Observability

The operating minimum includes the run queue, wake latency, execution time, OOM/timeout, number of retries, reaper state and cost per tenant. Correlation id associates the Marketplace action with the pod/runtime event and delivered result.

Limit of responsibility

IAM.Hosting is not a standalone directory or visual builder. The public control surface is located at IAM Marketplace, and capability contracts can be resolved via IAM.Core.