Map cloud IDs to owners and expiry dates
Connect
SPIRITT
DigitalOceanDigitalOcean
Cloud work, carried through
SPIRITT provisions DigitalOcean resources and runs the operations around them. Turn environment requests, DNS changes, and resource cleanup into completed work with a clear record of what changed.
What you can do with DigitalOcean.
Ready-to-use foundations
Create Droplets, managed databases, VPCs, and firewalls from a defined environment brief, with resource IDs and configuration captured for handoff.
Controlled DNS changes
Inspect existing domain records, apply targeted changes, and keep before-and-after values available for verification and rollback.
Accountable cloud resources
Map Droplets, volumes, databases, and clusters to owners, maintain supported resource tags, and retire explicitly approved infrastructure.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for provisioning, DNS management, or ongoing DigitalOcean operations.
02
Connect DigitalOcean
Connect your DigitalOcean account with access appropriate to the resources and changes your mission needs.
03
Delegate an outcome
Specify the environment, resource scope, and operating rules. SPIRITT builds the workflow, executes the work, and records the result.
Hand over a mission.
Choose a mission. Make it yours.
Put DigitalOcean to work.
Give your cloud an operator
Questions
DigitalOcean, with SPIRITT.
01Which DigitalOcean resources can SPIRITT provision?+
SPIRITT can create Droplets, managed database clusters, block storage volumes, VPCs, cloud firewalls, load balancers, and Kubernetes clusters. It can also import custom images, register SSH public keys, and create domains, DNS records, and resource tags.
02What access does DigitalOcean need?+
DigitalOcean supports an API credential or OAuth connection. Use access that matches the mission: inventory work needs resource visibility, while provisioning, DNS changes, tagging, and deletion require the corresponding authority. Resource scope and deletion authorization should be explicit.
03Can it manage DNS without replacing the whole zone?+
Yes. SPIRITT can list and retrieve domains and individual DNS records, then create, update, or delete specific records. A cutover can preserve the original values, target a single hostname, and read back the saved change without treating that as proof of global propagation.
04Can it keep infrastructure operations running across other tools?+
Yes. A recurring workflow can reconcile DigitalOcean inventory against a Google Sheets ownership register, maintain supported tags, send handoffs through Slack, and track unresolved work in Linear. This connects resource changes to owners and delivery tasks rather than leaving them as isolated cloud actions.
05What custom systems can it build around DigitalOcean?+
SPIRITT can build a resource ownership console, an environment request desk, or a sandbox retirement workflow. These systems can use DigitalOcean resource IDs, regions, configurations, tags, and snapshot metadata to give teams a searchable inventory and a traceable operational queue.
06Does provisioning infrastructure also deploy my application?+
Not by itself. The available DigitalOcean actions create infrastructure and can list App Platform apps, but do not create or deploy App Platform apps. Application installation, volume attachment, database migration, and Kubernetes workload deployment are separate steps that need their own execution path; the workflow can track those handoffs explicitly.