CSA LoomCSA Loom
Home
Ctrl K
Sign in
HomeWorkspacesBrowse
Lakehouse catalogSearchMarketplaceData productsConnectionsGovernance
Real-Time IntelligenceData ScienceOrchestration (Warp)Estate builderAgent MeshDeveloper
DeploymentWorkload hubScheduler
LineageAssetsMonitorReportsCopilot
  1. Home

  3. Admin portal

Tenant-wide settings, capacity, governance, audit, and usage for everyone in your organization.
Reliability & performanceHealth & ReliabilityPerformance & benchmarksReal-user monitoringReadinessDiagnosticsIncident console
Capacity & costCapacity & computeScale by SKUFinOps & chargeback
Configuration & gatesTenant settingsRuntime configurationGate registryRuntime flagsAPI Management
Catalog & domainsExternal-engine federation (Iceberg)DomainsCustom attributes
Access & security governanceSecurity & governancePolicy as codeFeature permissionsAccess governanceBatch labelingEmbed codesOrganizational visualsDSPM for AI
AI operationsAI operationsAutopilotMCP Servers
Audit & usageAudit logsUsage metricsEvent subscriptionsAPI tokens
Platform (network / updates)MigrateDeployment plannerLanding zonesUsers & licensesWorkspacesNetwork & DNSUpdates & version sync

Updates & version sync

In-place updates, no rebuildApplying an update rolls your Container Apps straight onto the published release images — no repo clone, no CI run. Review the release notes between your version and upstream first, then apply. If the images for a release are not yet published, the update refuses with a clear message rather than breaking anything.Releases on GitHub
Loom is open source and continuously updated. This page shows your running build, the latest version published upstream, and any release notes between them. When an update is available you can apply it in place — Loom rolls your Container Apps to the new release's images in the registry they already pull from, with no repo clone or CI run required.