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.
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
Markdown
[](/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
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)
- [](https://github.com/alexei-led/spotinfo/actions/workflows/ci.yaml) [](https://github.com/alexei-led/spotinfo/actions/workflows/docker.yaml) [](https://goreportcard.com/report/github.com/alexei-led/spotinfo) [](docs/mcp-server.md)
- # spotinfo
- **Pick a Spot machine on AWS, GCP or Azure from one command line. No credentials. Every price
- ships inside the binary, so `--offline` answers in about a tenth of a second.**
- ## The problem
- Spot capacity is far cheaper than On-Demand — between 40% and 85% off in the snapshots that
- ship with this tool. Finding the right machine does not scale by hand:
- - Each cloud publishes prices in a different place, in a different shape, on a different
- schedule. AWS has a JSON feed and an interruption Advisor. GCP has server-rendered HTML
- pages. Azure has a REST API and a separate documentation site for vCPU and memory.
- - The consoles rank by price. They do not rank by "cheapest machine with at least 4 vCPU and
- 16 GiB that my workload can survive losing".
- - A price page has no memory of yesterday, so a script that reads one is a scraper you now
- own.
- The result is that most teams pick one instance family, hard-code it, and stop looking.
- ## What spotinfo does
- One command ranks real machines against a real requirement, and says where the number came
- from.
- ```console
- $ spotinfo recommend --cloud azure --architecture arm64 --min-vcpu 4 --min-memory-gib 16
- RANK CLOUD REGION MACHINE ARCHITECTURE vCPU MEMORY GiB USD/HOUR SAVINGS RISK WHY
- 1 azure centralindia Standard_D4ps_v6 arm64 4 16.0 0.017076 81% unavailable ARCHITECTURE_MATCH,COST_POLICY,KNOWN_POSITIVE_PRICE,RESOURCE_MINIMUMS_MET
- 2 azure centralindia Standard_D4ps_v5 arm64 4 16.0 0.018665 81% unavailable ARCHITECTURE_MATCH,COST_POLICY,KNOWN_POSITIVE_PRICE,RESOURCE_MINIMUMS_MET
- 3 azure centralindia Standard_D4pds_v5 arm64 4 16.0 0.022361 81% unavailable ARCHITECTURE_MATCH,COST_POLICY,KNOWN_POSITIVE_PRICE,RESOURCE_MINIMUMS_MET
- ```
- Four properties make that output worth trusting:
- **It works with no credentials.** Price snapshots ship inside the binary, and a weekly job
- refreshes them through a reviewed pull request. AWS and Azure additionally read live feeds
- when they can reach them — AWS on every run, Azure when you name one or two regions — and
- fall back to the snapshot when they cannot. `--offline` skips every price and risk request;
- only `--with-score` still reaches a cloud, because no snapshot carries a placement figure.
- **It says what it does not know.** GCP and Azure publish no redistributable interruption
- data, so every candidate reports `RISK: unavailable`. It is never a zero and never a low
- bucket. A cloud that measures nothing must not outrank a cloud that measures honestly. On
- GCP, `--live-risk` fetches a per-project preemption rate for the ranked page — Google
- measures it differently from AWS, so it is shown and never filtered on.
- **It refuses questions it cannot answer, and says why.** `--workload web` caps interruption
- frequency at an AWS Spot Advisor bucket boundary. Ask for it on a cloud that measures
- something else and the command stops before it reads a price, naming the vendor limit rather
- than a feature nobody built:
- ```console
- $ spotinfo recommend --cloud gcp --workload web --architecture x86_64 --min-vcpu 4 --min-memory-gib 16
- 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
- ```
- **Every answer carries its source.** The JSON report names each source URL and the SHA-256 of
- the document that was read, so a reader can fetch it again and compare.
- ## Install
- ```bash
- # 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).
- ## Use it
- ```bash
- # Cheapest Arm machine with 4 vCPU and 16 GiB, on each cloud
- spotinfo recommend --cloud aws --architecture arm64 --min-vcpu 4 --min-memory-gib 16
- spotinfo recommend --cloud gcp --architecture arm64 --min-vcpu 4 --min-memory-gib 16
- spotinfo recommend --cloud azure --architecture arm64 --min-vcpu 4 --min-memory-gib 16
- # A web tier that must survive interruption: AWS only, interruption capped at 5%
- spotinfo recommend --architecture x86_64 --min-vcpu 2 --min-memory-gib 8 --workload web
- # The five cheapest AWS regions for a machine. Every region is the default
- spotinfo recommend --architecture x86_64 --min-vcpu 4 --min-memory-gib 16 --top 5
- # A versioned JSON report for a pipeline
- spotinfo recommend --cloud azure --architecture arm64 --min-vcpu 4 --min-memory-gib 16 \
- --output json
- # Browse what a cloud publishes, with prices and a risk column
- spotinfo list --machine "m5\." --region us-east-1
- # Add AWS placement scores. This one needs AWS credentials
- spotinfo list --machine "m5\." --region us-east-1 --with-score
- ```
- Two commands, on purpose, and both answer on all three clouds. `spotinfo list` requires
- nothing and answers "what is there". `spotinfo recommend` requires an architecture and a size
- floor and answers "what should I run". They share a vocabulary, not a purpose. See
- [Quick start](docs/quick-start.md) and the [Usage guide](docs/usage.md).
- ## Cloud coverage
- | | AWS | GCP | Azure |
- | -------------------- | -------------------- | ----------------------------- | -------------- |
- | `spotinfo list` | yes | yes | yes |
- | `spotinfo recommend` | yes | yes | yes |
- | Interruption risk | published | `unavailable`, or opt-in live | `unavailable` |
- | Workloads | cost, web, ci, batch | cost | cost |
- | Operating systems | linux, windows | linux | linux, windows |
- | Architectures | x86_64, arm64 | x86_64, arm64 | x86_64, arm64 |
- | Credentials | optional | optional | never used |
- Region lists, machine counts and the reasoning behind each limit:
- [Cloud coverage](docs/clouds.md).
- ## MCP server
- spotinfo is a [Model Context Protocol](https://modelcontextprotocol.io/) server, so an
- assistant can ask these questions directly.
- ```json
- {
- "mcpServers": {
- "spotinfo": { "command": "spotinfo", "args": ["--mcp"] }
- }
- }
- ```
- Ask: _"Cheapest arm64 Azure Spot VM with 4 vCPUs and 16 GiB"_, or _"Compare m5.large spot
- prices across US regions"_. Three tools answer: `list_spot_machines`,
- `recommend_spot_machines` and `list_cloud_regions`.
- Setup: [MCP server](docs/mcp-server.md) and [Claude Desktop](docs/claude-desktop-setup.md).
- ## Documentation
- | Document | What is in it |
- | --------------------------------------------------------- | ------------------------------------------------------------ |
- | [Quick start](docs/quick-start.md) | The first five minutes |
- | [Installation](docs/installation.md) | Every install method, and how to check one |
- | [Usage guide](docs/usage.md) | Every flag, every output format |
- | [Cloud coverage](docs/clouds.md) | What each cloud serves, and what it refuses |
- | [Examples](docs/examples.md) | Pipelines, Terraform, CI, cost monitors |
- | [MCP server](docs/mcp-server.md) | Tools, arguments, assistant setup |
- | [API reference](docs/api-reference.md) | The `spotinfo.list/v1` and `spotinfo.recommend/v3` contracts |
- | [AWS placement scores](docs/aws-spot-placement-scores.md) | What a score means, and does not |
- | [Data sources](docs/data-sources.md) | Every feed, snapshot, cache and refresh rule |
- | [Troubleshooting](docs/troubleshooting.md) | Errors, causes, fixes |
- | [Migrating to v2](docs/migration-v2.md) | Every renamed flag, tool, schema and field |
- | [Multi-cloud parity](docs/reviews/multicloud-parity.md) | What GCP and Azure cannot do yet, and why |
- ## AWS credentials
- Credentials are optional. Without them, spotinfo answers from the AWS feeds and the embedded
- snapshot. With them, two more features work:
- | Feature | Permission |
- | ---------------------------------------------------- | ------------------------------ |
- | Live price for machines the static feed prices at $0 | `ec2:DescribeSpotPriceHistory` |
- | Placement scores (`--with-score`) | `ec2:GetSpotPlacementScores` |
- Credentials load through the standard AWS SDK chain. The chain is probed once per run, so a
- machine without credentials skips both calls instead of waiting for each to time out.
- GCP credentials are optional too. Application Default Credentials and a project — from
- `--gcp-project` or `GOOGLE_CLOUD_PROJECT` — are needed for `--live-risk` and for
- `--with-score`, and a Cloud Billing Catalog API key in `--gcp-billing-key` prices GCP regions
- beyond the committed snapshot. Azure needs no credentials at all. See
- [Cloud coverage](docs/clouds.md).
- ## Development
- Go 1.26+, make, golangci-lint.
- ```bash
- make build # hermetic: embeds the committed data, downloads nothing
- make test # unit and end-to-end tests, no credentials, no network
- make lint
- make verify-data # manifests, source contracts, parser contracts, coverage floors
- ```
- Contributions are welcome. Read [CLAUDE.md](CLAUDE.md) for the repository rules. Make sure
- that every test passes before you open a pull request.
- ## License
- Apache 2.0. See [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.