mngr Vultr Provider
Vultr provider backend plugin for mngr. Runs agents in Docker containers on Vultr VPS instances.
See mngr_vps_docker for the base architecture and shared infrastructure.
Setup
Set VULTR_API_KEY in your environment or add api_key to the provider config in ~/.mngr/config.toml:
[providers.vultr]
backend = "vultr"
api_key = "YOUR_VULTR_API_KEY"
Usage
mngr create my-agent --provider vultr
mngr create my-agent --provider vultr -b --region=sjc -b --plan=vc2-2c-4gb
mngr list
mngr exec my-agent "echo hello"
mngr stop my-agent
mngr start my-agent
mngr destroy my-agent
Vultr-specific configuration
These fields extend the base VpsDockerProviderConfig (see mngr_vps_docker):
| Field | Default | Description |
|---|---|---|
api_key |
None (falls back to VULTR_API_KEY env var) |
Vultr API key |
default_region |
ewr |
Default Vultr region |
default_plan |
vc2-2c-4gb |
Default Vultr plan |
default_os_id |
2136 | Default Vultr OS ID (Debian 12 x64) |
Implementation details
- Uses raw HTTP calls to the Vultr API v2 (
https://api.vultr.com/v2), no third-party SDK - VPS instances are tagged with
mngr-provider=<name>andmngr-host-id=<id>for discovery - SSH keys are uploaded to the Vultr SSH key store and referenced by ID during instance creation
- Discovery works by listing all Vultr instances with matching tags, then SSH-ing to each VPS to read host records from the state volume
Metadata
Release files for imbue-mngr-vultr 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| imbue_mngr_vultr-0.1.10.tar.gz | 18.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| imbue_mngr_vultr-0.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 25.4 kB
Release files / imbue_mngr_vultr-0.1.10.tar.gz
| Download URL | imbue_mngr_vultr-0.1.10.tar.gz |
|---|---|
| Size | 18.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5057d084d0b1c370993a363c1e14f26bc25ba156527b242d31294b8ca998d58c
|
|
BLAKE2b-256 checksum How to use checksums |
6149f2cc09feb3bd382eeb1c714367062bc512d9f5a7fbeeaddc7eff32f81217
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency logRelease files / imbue_mngr_vultr-0.1.10-py3-none-any.whl
| Download URL | imbue_mngr_vultr-0.1.10-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
883bcaf0897c736fa3f50ec59e3aa098dd906c8c63b6427ff3a55e1fe25487ae
|
|
BLAKE2b-256 checksum How to use checksums |
df9c3762565749e7205c7828237fabf543acb5cc3f238d94a54e3ff1215fc216
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 18, 2026.
Transparency log