Skip to content
Back to search

spotinfo

CLI for exploring Spot instance pricing across AWS, GCP and Azure. Inspect Spot instance types, savings, price, and AWS interruption frequency — offline, from embedded data.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/alexei-led/spotinfo with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/alexei-led/spotinfo'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/alexei-led--spotinfo/badge.svg)](/listings/alexei-led--spotinfo)

HTML

<a href="/listings/alexei-led--spotinfo"><img src="/api/listings/alexei-led--spotinfo/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

# macOS with Homebrew
brew install alexei-led/tap/spotinfo

# Linux and Windows
curl -L https://github.com/alexei-led/spotinfo/releases/latest/download/spotinfo_linux_amd64.tar.gz | tar xz

# Docker
docker pull ghcr.io/alexei-led/spotinfo:latest

macOS, Linux and Windows, on AMD64 and ARM64. Full instructions: [Installation](docs/installation.md).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 195 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. [![CI](https://github.com/alexei-led/spotinfo/actions/workflows/ci.yaml/badge.svg)](https://github.com/alexei-led/spotinfo/actions/workflows/ci.yaml) [![Docker](https://github.com/alexei-led/spotinfo/actions/workflows/docker.yaml/badge.svg)](https://github.com/alexei-led/spotinfo/actions/workflows/docker.yaml) [![Go Report Card](https://goreportcard.com/badge/github.com/alexei-led/spotinfo)](https://goreportcard.com/report/github.com/alexei-led/spotinfo) [![MCP Compatible](https://img.shields.io/badge/MCP-Compatible-blue)](docs/mcp-server.md)
  2. # spotinfo
  3. **Pick a Spot machine on AWS, GCP or Azure from one command line. No credentials. Every price
  4. ships inside the binary, so `--offline` answers in about a tenth of a second.**
  5. ## The problem
  6. Spot capacity is far cheaper than On-Demand — between 40% and 85% off in the snapshots that
  7. ship with this tool. Finding the right machine does not scale by hand:
  8. - Each cloud publishes prices in a different place, in a different shape, on a different
  9. schedule. AWS has a JSON feed and an interruption Advisor. GCP has server-rendered HTML
  10. pages. Azure has a REST API and a separate documentation site for vCPU and memory.
  11. - The consoles rank by price. They do not rank by "cheapest machine with at least 4 vCPU and
  12. 16 GiB that my workload can survive losing".
  13. - A price page has no memory of yesterday, so a script that reads one is a scraper you now
  14. own.
  15. The result is that most teams pick one instance family, hard-code it, and stop looking.
  16. ## What spotinfo does
  17. One command ranks real machines against a real requirement, and says where the number came
  18. from.
  19. ```console
  20. $ spotinfo recommend --cloud azure --architecture arm64 --min-vcpu 4 --min-memory-gib 16
  21. RANK CLOUD REGION MACHINE ARCHITECTURE vCPU MEMORY GiB USD/HOUR SAVINGS RISK WHY
  22. 1 azure centralindia Standard_D4ps_v6 arm64 4 16.0 0.017076 81% unavailable ARCHITECTURE_MATCH,COST_POLICY,KNOWN_POSITIVE_PRICE,RESOURCE_MINIMUMS_MET
  23. 2 azure centralindia Standard_D4ps_v5 arm64 4 16.0 0.018665 81% unavailable ARCHITECTURE_MATCH,COST_POLICY,KNOWN_POSITIVE_PRICE,RESOURCE_MINIMUMS_MET
  24. 3 azure centralindia Standard_D4pds_v5 arm64 4 16.0 0.022361 81% unavailable ARCHITECTURE_MATCH,COST_POLICY,KNOWN_POSITIVE_PRICE,RESOURCE_MINIMUMS_MET
  25. ```
  26. Four properties make that output worth trusting:
  27. **It works with no credentials.** Price snapshots ship inside the binary, and a weekly job
  28. refreshes them through a reviewed pull request. AWS and Azure additionally read live feeds
  29. when they can reach them — AWS on every run, Azure when you name one or two regions — and
  30. fall back to the snapshot when they cannot. `--offline` skips every price and risk request;
  31. only `--with-score` still reaches a cloud, because no snapshot carries a placement figure.
  32. **It says what it does not know.** GCP and Azure publish no redistributable interruption
  33. data, so every candidate reports `RISK: unavailable`. It is never a zero and never a low
  34. bucket. A cloud that measures nothing must not outrank a cloud that measures honestly. On
  35. GCP, `--live-risk` fetches a per-project preemption rate for the ranked page — Google
  36. measures it differently from AWS, so it is shown and never filtered on.
  37. **It refuses questions it cannot answer, and says why.** `--workload web` caps interruption
  38. frequency at an AWS Spot Advisor bucket boundary. Ask for it on a cloud that measures
  39. something else and the command stops before it reads a price, naming the vendor limit rather
  40. than a feature nobody built:
  41. ```console
  42. $ spotinfo recommend --cloud gcp --workload web --architecture x86_64 --min-vcpu 4 --min-memory-gib 16
  43. spotinfo: gcp: unsupported capability: risk: the web workload caps interruption frequency at 5%, an AWS Spot Advisor bucket boundary, and gcp publishes no figure measured that way; workload cost applies no ceiling and answers on every cloud
  44. ```
  45. **Every answer carries its source.** The JSON report names each source URL and the SHA-256 of
  46. the document that was read, so a reader can fetch it again and compare.
  47. ## Install
  48. ```bash
  49. # macOS with Homebrew
  50. brew install alexei-led/tap/spotinfo
  51. # Linux and Windows
  52. curl -L https://github.com/alexei-led/spotinfo/releases/latest/download/spotinfo_linux_amd64.tar.gz | tar xz
  53. # Docker
  54. docker pull ghcr.io/alexei-led/spotinfo:latest
  55. ```
  56. macOS, Linux and Windows, on AMD64 and ARM64. Full instructions:
  57. [Installation](docs/installation.md).
  58. ## Use it
  59. ```bash
  60. # Cheapest Arm machine with 4 vCPU and 16 GiB, on each cloud
  61. spotinfo recommend --cloud aws --architecture arm64 --min-vcpu 4 --min-memory-gib 16
  62. spotinfo recommend --cloud gcp --architecture arm64 --min-vcpu 4 --min-memory-gib 16
  63. spotinfo recommend --cloud azure --architecture arm64 --min-vcpu 4 --min-memory-gib 16
  64. # A web tier that must survive interruption: AWS only, interruption capped at 5%
  65. spotinfo recommend --architecture x86_64 --min-vcpu 2 --min-memory-gib 8 --workload web
  66. # The five cheapest AWS regions for a machine. Every region is the default
  67. spotinfo recommend --architecture x86_64 --min-vcpu 4 --min-memory-gib 16 --top 5
  68. # A versioned JSON report for a pipeline
  69. spotinfo recommend --cloud azure --architecture arm64 --min-vcpu 4 --min-memory-gib 16 \
  70. --output json
  71. # Browse what a cloud publishes, with prices and a risk column
  72. spotinfo list --machine "m5\." --region us-east-1
  73. # Add AWS placement scores. This one needs AWS credentials
  74. spotinfo list --machine "m5\." --region us-east-1 --with-score
  75. ```
  76. Two commands, on purpose, and both answer on all three clouds. `spotinfo list` requires
  77. nothing and answers "what is there". `spotinfo recommend` requires an architecture and a size
  78. floor and answers "what should I run". They share a vocabulary, not a purpose. See
  79. [Quick start](docs/quick-start.md) and the [Usage guide](docs/usage.md).
  80. ## Cloud coverage
  81. | | AWS | GCP | Azure |
  82. | -------------------- | -------------------- | ----------------------------- | -------------- |
  83. | `spotinfo list` | yes | yes | yes |
  84. | `spotinfo recommend` | yes | yes | yes |
  85. | Interruption risk | published | `unavailable`, or opt-in live | `unavailable` |
  86. | Workloads | cost, web, ci, batch | cost | cost |
  87. | Operating systems | linux, windows | linux | linux, windows |
  88. | Architectures | x86_64, arm64 | x86_64, arm64 | x86_64, arm64 |
  89. | Credentials | optional | optional | never used |
  90. Region lists, machine counts and the reasoning behind each limit:
  91. [Cloud coverage](docs/clouds.md).
  92. ## MCP server
  93. spotinfo is a [Model Context Protocol](https://modelcontextprotocol.io/) server, so an
  94. assistant can ask these questions directly.
  95. ```json
  96. {
  97. "mcpServers": {
  98. "spotinfo": { "command": "spotinfo", "args": ["--mcp"] }
  99. }
  100. }
  101. ```
  102. Ask: _"Cheapest arm64 Azure Spot VM with 4 vCPUs and 16 GiB"_, or _"Compare m5.large spot
  103. prices across US regions"_. Three tools answer: `list_spot_machines`,
  104. `recommend_spot_machines` and `list_cloud_regions`.
  105. Setup: [MCP server](docs/mcp-server.md) and [Claude Desktop](docs/claude-desktop-setup.md).
  106. ## Documentation
  107. | Document | What is in it |
  108. | --------------------------------------------------------- | ------------------------------------------------------------ |
  109. | [Quick start](docs/quick-start.md) | The first five minutes |
  110. | [Installation](docs/installation.md) | Every install method, and how to check one |
  111. | [Usage guide](docs/usage.md) | Every flag, every output format |
  112. | [Cloud coverage](docs/clouds.md) | What each cloud serves, and what it refuses |
  113. | [Examples](docs/examples.md) | Pipelines, Terraform, CI, cost monitors |
  114. | [MCP server](docs/mcp-server.md) | Tools, arguments, assistant setup |
  115. | [API reference](docs/api-reference.md) | The `spotinfo.list/v1` and `spotinfo.recommend/v3` contracts |
  116. | [AWS placement scores](docs/aws-spot-placement-scores.md) | What a score means, and does not |
  117. | [Data sources](docs/data-sources.md) | Every feed, snapshot, cache and refresh rule |
  118. | [Troubleshooting](docs/troubleshooting.md) | Errors, causes, fixes |
  119. | [Migrating to v2](docs/migration-v2.md) | Every renamed flag, tool, schema and field |
  120. | [Multi-cloud parity](docs/reviews/multicloud-parity.md) | What GCP and Azure cannot do yet, and why |
  121. ## AWS credentials
  122. Credentials are optional. Without them, spotinfo answers from the AWS feeds and the embedded
  123. snapshot. With them, two more features work:
  124. | Feature | Permission |
  125. | ---------------------------------------------------- | ------------------------------ |
  126. | Live price for machines the static feed prices at $0 | `ec2:DescribeSpotPriceHistory` |
  127. | Placement scores (`--with-score`) | `ec2:GetSpotPlacementScores` |
  128. Credentials load through the standard AWS SDK chain. The chain is probed once per run, so a
  129. machine without credentials skips both calls instead of waiting for each to time out.
  130. GCP credentials are optional too. Application Default Credentials and a project — from
  131. `--gcp-project` or `GOOGLE_CLOUD_PROJECT` — are needed for `--live-risk` and for
  132. `--with-score`, and a Cloud Billing Catalog API key in `--gcp-billing-key` prices GCP regions
  133. beyond the committed snapshot. Azure needs no credentials at all. See
  134. [Cloud coverage](docs/clouds.md).
  135. ## Development
  136. Go 1.26+, make, golangci-lint.
  137. ```bash
  138. make build # hermetic: embeds the committed data, downloads nothing
  139. make test # unit and end-to-end tests, no credentials, no network
  140. make lint
  141. make verify-data # manifests, source contracts, parser contracts, coverage floors
  142. ```
  143. Contributions are welcome. Read [CLAUDE.md](CLAUDE.md) for the repository rules. Make sure
  144. that every test passes before you open a pull request.
  145. ## License
  146. Apache 2.0. See [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.