# How to use a Righthand with DigitalOcean

Use Righthand to prepare a DigitalOcean Droplet ownership review from a limited resource inventory.

By Righthand Team · 2026-10-12

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-digitalocean

## Quick answer

Use Righthand to prepare a DigitalOcean Droplet ownership review from a limited resource inventory. Keep IDs, regions, and tags together before suggesting cleanup.

Start with a reviewable deliverable, keeping DigitalOcean as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

## Evidence and access

DigitalOcean documents tagging Droplets and related resource operations. See the [official DigitalOcean reference](https://docs.digitalocean.com/products/droplets/how-to/tag/). Provider capabilities and Righthand's available tools are separate checks.

Use the owner's limited account and region inventory with resource IDs, labels, observed states, and supplied purpose or ownership records. Verify the required tools and owner-approved scope through [Righthand integrations](/integrations); use the supplied packet when a native read is unavailable.

## Define the objects and authority

Include these fields in the working input: team, Droplet ID, region, state, tags, owner, intended environment. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Tags are evidence to inspect, not sufficient proof a resource can be destroyed. Retention and infrastructure changes need operator approval.

| Responsibility | Owner |
| --- | --- |
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the infrastructure operator |

## Illustrative first-run brief

> Use the owner-provided DigitalOcean snapshot or approved read-only view. Compare the supplied development Droplet inventory with the owner list. Flag missing ownership and uncertain environment tags. Do not destroy or resize resources. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the infrastructure operator to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

## Expected result and verification

A Droplet tagged test can still support an active workflow. The report asks for owner confirmation rather than scheduling removal.

Match a resource ID and region in the original console and confirm its responsible owner. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.


### Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

| Source item | Supplied observation | Draft conclusion |
| --- | --- | --- |
| Resource A | Purpose and owner known | Apply supplied criteria |
| Resource B | Low use, owner unknown | Request review |
| Volume C | Retention unresolved | Preserve pending decision |

## Common failure and recovery

Stale tags can misclassify production dependencies. Ask the operator to review active use and dependencies before changing the inventory classification.

If an apparently unused resource lacks an owner, classify it for review and request clarification rather than treating it as safe to remove.

## FAQ

### What should the reviewer verify first?

Verify resource identity, region, lifecycle state, owner, and supporting dependencies. A low-use observation is not evidence that an application or backup no longer needs it.

### How should a repeat run be scoped?

Keep resource IDs and inventory cutoff between runs. Refresh dependencies before any separate retirement decision and preserve unique data or recovery evidence.

For connection and permission details, use [Righthand Docs](https://docs.righthand.ai). Review [Pricing](/pricing) alongside any separate provider charges before expanding the workflow.