vantage-sh/ec2instances.info

★ 5,716TypeScriptAudience · ops devopsComplexity · 3/5Setup · moderate

Mindmap

mindmap
  root((repo))
    What it does
      Cloud price comparison
      Instance filtering
      Multi-provider
    Providers
      AWS EC2
      Azure VMs
      Google Cloud
    Tech stack
      Next.js frontend
      Go scraper
      Cloudflare hosting
    Use cases
      Cost optimization
      Instance selection
      Self-hosting

mindmap root((repo)) What it does Cloud price comparison Instance filtering Multi-provider Providers AWS EC2 Azure VMs Google Cloud Tech stack Next.js frontend Go scraper Cloudflare hosting Use cases Cost optimization Instance selection Self-hosting

Click or tap to explore — scroll the page freely

Things people build with this

USE CASE 1

Compare EC2 instance types and prices across regions to find the cheapest option for a given amount of CPU and memory.

USE CASE 2

Run your own fork of the site with custom scraped data for internal cloud cost analysis.

USE CASE 3

Contribute updated pricing or new instance specs when cloud providers add new hardware.

Tech stack

TypeScriptNext.jsGoCloudflareCloudflare Workers

Getting it running

Difficulty · moderate Time to first run · 30min

Scraping live pricing data requires cloud provider API credentials, but pre-built data files can be downloaded to run the front end without them.

In plain English

EC2Instances.info is the codebase behind a website that lets you compare cloud server types and pricing across Amazon Web Services, Microsoft Azure, and Google Cloud. Amazon's own documentation makes these comparisons awkward, so this site pulls the data together in a single filterable table. It was originally built by an individual developer and is now maintained and hosted by a company called Vantage, with ongoing contributions from the open-source community. The project has two main pieces. A scraper written in Go fetches instance specifications and pricing data from the cloud provider APIs. A Next.js web front end displays that data. Running the scraper requires API credentials for whichever providers you want data from, and the README includes detailed permission requirements for each. For most contributors who are not changing the scraper, pre-built data can be downloaded directly so the Next.js development server can be started without setting up cloud credentials at all. Building a full production release takes around 30 minutes and produces a static folder that can be served from any web host. The project uses Cloudflare for hosting and includes a small Cloudflare Worker for redirect logic. Several optional environment variables control things like error tracking with Sentry, analytics via Google Tag Manager, and whether search engines are allowed to index the deployment. Vantage maintains several related open-source tools linked from the README, including a similar site for comparing large language model pricing, a reference for AWS billing codes, and a cloud cost handbook covering best practices. The project is community-driven. Pull requests target a develop branch for staging review before being merged to main for production. A Slack community channel is available for discussion.

Copy-paste prompts

Prompt 1

I need to choose an EC2 instance for a memory-intensive Node.js workload. Using ec2instances.info data, help me filter for instances with at least 32GB RAM in us-east-1, exclude burstable types, and sort by price per GB of memory.

Prompt 2

I want to run the ec2instances.info Next.js front end locally without setting up AWS credentials. Walk me through downloading the pre-built data files and starting the dev server.

Prompt 3

I want to add Azure VM pricing to my local fork of ec2instances.info. Explain what API credentials I need and where in the Go scraper code I should add a new provider data source.

Open on GitHub → Explain another repo

← vantage-sh on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.