Daestro

Blog Documentation Changelog FAQ Pricing Instances
Login
Blog Documentation Changelog FAQ Pricing Instances
Login
skip to the main content
Getting Started About Cloud Auth Compute Environment Job Queue Container Registry Auth Job Definition Job Compute Spawn Features Cron Jobs Schedule Jobs Cloud Providers Amazon Web Services DigitalOcean Linode / Akamai Vultr Self-hosted Compute Docker API Create API Key Job Submit Job Detail Cancel Job
Home/Documentation/Cloud Providers/

Vultr

Table of Contents
  1. Step 1: Get Your Personal Access Token from Vultr
  2. Step 2: Add Your Vultr Token to Daestro
  3. Step 3: Create Your First Vultr Compute Environment

Vultr has powerful infrastructure and consistent performance at a competitive price. You can deploy resources close to your users, wherever they are.

Daestro can manage Vultr instances next to your other cloud providers, from one dashboard. You can schedule, run, and oversee batch jobs on Vultr without talking to their API yourself. Daestro handles the instance lifecycle, so you can focus on the applications and workloads.


Step 1: Get Your Personal Access Token from Vultr

Daestro needs your Vultr Personal Access Token (API Key) to manage servers in your account.

  1. Log in to your Vultr account.

  2. In the left-hand menu, click Account, then API.

  3. On the API page you will see a Personal Access Token. That is your API Key.

    • If you have not enabled the API before, you may need to click Enable API first.
    • Click the Copy icon to copy the token. Store it in a password manager. You will need it in the next step.
  4. Configure Access Control:

    • Vultr requires you to whitelist which IP addresses can use your API token.
    • Daestro runs in the cloud and may connect from various IP addresses, so the most reliable approach is to allow access from any IP.
    • In the Access Control section on the same page, find the IPv4 and IPv6 Access Control lists.
    • Add 0.0.0.0/0 to the IPv4 list and ::/0 to the IPv6 list. That lets Daestro connect from any address.
    • Enter 0.0.0.0 in the text box, select /0 from the dropdown, and click Add. Do the same for :: and /0 for IPv6.

Security Note: Allowing access from any IP (0.0.0.0/0) means your account’s security relies entirely on keeping the API token secret. Store the token somewhere safe and do not share it publicly.


Step 2: Add Your Vultr Token to Daestro

  1. Log in to your Daestro Console.
  2. Open Cloud Auth from the main menu.
  3. Click Add New and select Vultr from the list of providers.
  4. Fill in the form:
    • Cloud Auth Name: a name you will recognize, like My Vultr Account.
    • API Token: the Personal Access Token you copied from Vultr.

Credentials you save in Daestro are encrypted with AES-256 when stored (at rest) and sent over TLS (in transit).

  1. Click Save.

Your Vultr account is now linked to Daestro.


Step 3: Create Your First Vultr Compute Environment

A Compute Environment in Daestro is the server where your jobs run. On Vultr, that server is a Cloud Compute instance.

  1. In the Daestro Console, open Compute Environment.
  2. Click Create New.
  3. Configure the Vultr instance:
    • Name: something descriptive, like vultr-sjc-worker.
    • Cloud Auth: the Vultr credential you just created (for example, My Vultr Account).
    • Instance Type: the server plan. This sets CPU, RAM, storage, and price. Vultr has a range of options, including High Frequency and High Performance plans.
    • Location: the Vultr data center to launch in (for example, Silicon Valley, Tokyo, Amsterdam).
    • Storage (GB): usually set by the plan you pick.
    • Assign Public IPv4: check this if the job needs to be reachable from the public internet.
  4. Click Create.

Daestro provisions a Cloud Compute instance in your Vultr account. When the status is Ready in the Daestro dashboard, you can assign jobs to it.

Previous

Linode / Akamai

Daestro © 2026

Contact

hello@daestro.com

Legal
Terms of UsePrivacy Policy
Resources
Blog Documentation FAQ Changelog Instances
Helpful Articles
Batch Jobs Cron Jobs BYOC vs AWS Batch
Social
X (Twitter)Discord
2026-09-11T10:40:32.368556062Z