Anycloud for Slack

Cloud operations alerts where your team already works

Send delayed VM-release alerts, GPU spend-cap alerts, daily deployment summaries, and new release notes from your Anycloud server straight to a channel your team chooses. No hosted notification relay and no access to your Slack messages.

Add Anycloud to Slack Read the notification docs

One permissionLocal deliveryNo Slack data reads

Delayed VM release

anycloudAPP4:42 PM

anycloud: VM release delayed

3 VMs across 2 deployments remain unreleased; the oldest has been waiting 18m since Anycloud requested removal.
The provider may continue billing until release is confirmed. Anycloud will keep retrying cleanup.
Affected deployments: training-h100-west, model-eval-42.

API: production.anycloud.sh · @alice

Three steps

Install once, deliver locally

A workspace administrator authorizes the destination channel. Slack creates a channel-specific webhook, and your Anycloud operator connects it to the server that already knows about your deployments and spend.

Start from your server

Run anycloud notifications connect slack on the machine hosting your API. The CLI opens Slack or prints the installation URL.

Choose a channel

Authorize Anycloud in your workspace, copy the channel webhook, then paste it into the CLI's hidden prompt.

Receive useful alerts

Anycloud posts a test message immediately, followed by daily summaries, actionable spend-cap notifications, delayed VM-release warnings, and new-release updates.

Local-first architecture

Your cloud credentials never enter the Slack integration

Installation uses a small OAuth service. Notification delivery does not: the Anycloud API reads its local activity database and sends the resulting message directly to Slack.

Your infrastructureAnycloud APICalculates deployment activity and compute spend locally.

Outbound HTTPSSlack incoming webhookUses the secret URL created for the channel you selected.

Your workspaceSelected Slack channelReceives only the alerts and summaries Anycloud sends.

Minimal permission

Permission for one job only

Required Slack scope

incoming-webhook

Post messages to the channel selected during installation.
No permission to read messages, users, files, or channels.
No slash commands, events, interactive actions, or App Home.
No cloud-provider credentials pass through the Slack installation service.

What your team sees

Operational context without another dashboard

Messages are derived from the same local deployment records used by the Anycloud CLI. Inactive sections and zero-value lines are omitted.

Daily summary

anycloudAPP4:42 PM

anycloud: daily cloud activity

Compute spend: $132.47👤 alice• Jobs: 18 completed · 2 preempted👤 bob• Services: $24.12 compute spend

Spend control

anycloudAPP4:42 PM

anycloud: deployments waiting on spend cap

blocked by daily budget (agent-session 'csp-rank'): spent $4,224 / $4,000 - resumes 2026-05-29 00:00 UTC

Ready to connect?

Add Anycloud to Slack

The Slack integration has no separate charge. Your Anycloud plan and cloud-provider charges still apply.

Add Anycloud to Slack Setup and support Privacy