inetGeek

Hosting, databases and the infrastructure between them, read from what providers publish — dated, sourced, and never paid for. Plan what your next project needs, or check what you already have.

Find infrastructure for what you're building.
Pick everything your project is made of and needs. The list below narrows to providers that document support for everything picked — nothing here is a guess at what a provider can do. Need the whole stack, not just where it runs?

Connect inetGeek to an AI assistant
Everything on this site — sourced pricing, comparisons, stack recommendations, live DNS tools — is also reachable as an MCP server, so an assistant like Claude or ChatGPT can read it directly instead of guessing from training data that may predate this week's price change.

What it gives an assistant
Nineteen tools. All but one are read-only: send_feedbackrecords a note for the person who maintains the site and can change nothing. Every fact the others return is the same sourced, dated figure published on the matching page here — this is a distribution layer for data already verified, not a place a new claim originates.

What it won't do
compare_providers only answers for the curated pairs already published here — an uncurated pair returns a plain "not published yet," not a guess assembled on the spot. And no tool projects a cost at scale: this site records what a provider documents, not an estimate of what heavy traffic would cost you, because a vendor's own spend estimate is not a price either — see the methodology. An assistant can reason about scaling readiness from the real limits get_provider returns — connection counts, egress pricing, regional coverage — but the dollar figure at your traffic is its arithmetic, not a number this site asserts.