Droplet Provisioning

A Beam agent watches for a provisioning request, whether that is a new droplet, a resize, or a teardown, and reads the account's current resource usage before acting. Where a customer-approved rule allows it, such as spinning up a standard droplet within a project's existing budget, the agent creates the droplet and updates a tracking sheet or ticket with the details. A request that would exceed a spend cap, touch a production cluster, or open new network access gets routed to a human, who approves or declines the change before anything happens to the account.

Billing and Usage Alerts

A Beam agent reads a DigitalOcean account's billing and resource usage on a schedule, comparing current spend against a threshold the customer has set. When usage crosses that threshold, the agent posts a notice to a shared channel or ticket, noting which droplets, databases, or Spaces buckets are driving the increase. Routine notices, like a monthly summary or an early warning at a set percentage, go out without anyone touching them. Any case where spend jumps sharply, a new resource type appears, or the threshold needs changing gets routed to a human for a decision.

Snapshot and Backup Scheduling

A Beam agent checks whether a droplet or volume has a snapshot due, based on the schedule a customer has approved, and confirms the last backup completed before starting the next one. Where the connector and account permissions allow it, the agent starts the snapshot, labels it with the date and source, and updates a log so the team can see backup history at a glance. If a snapshot fails, storage nears its limit, or a droplet is missing from the expected schedule, the agent notes it and routes the exception to a human rather than retrying on its own.