SV Premium

The Silicon Valley premium, priced

Know what you’re paying extra for.

Enter your usage and see what 237 services across 18 categories, from DNS and CDNs to LLM APIs, would charge. Filter by parent-company jurisdiction and EU data residency, and find a migration guide if you decide to switch. Every service links to the vendor’s pricing page and the date we last checked it.

Compare your costsPlan a migration →

Choose a category

Infrastructure

Developer services

AI APIs

Same usage, different bills

Each pair is estimated at the same usage. The services don’t include the same things, and the note under each pair says what differs.

Sources last checked 2026-10-06 to 2026-10-09. Estimates exclude some costs and can change. How we compare.

Use the numbers, then check the fit

  1. Enter your usage and current provider. Add a migration cost to see how long a switch could take to pay for itself.
  2. Check the plan’s features, data residency and extra charges. Self-hosted options are listed separately.
  3. Try the new service on a small workload. The migration guides cover testing and how to switch back if needed.

Managed services are sorted by estimated cost, lowest first. Affiliate links, if any, don’t affect the order. See how we calculate costs or read about the project.

What the premium is

“The Silicon Valley premium” is our shorthand for the extra you may pay for a familiar infrastructure vendor. Some of that difference buys support, certifications, features and a track record. Some may reflect packaging, sales overhead or the convenience of staying put. A price table cannot isolate those causes or tell us the vendor’s production cost. It can show which alternatives are worth investigating.See the premium in numbers, category by category.

The name doesn’t mean US vendors always cost more. At our default usage, a US-based company has the lowest estimate (or ties for it) in 16 of 18 categories. In 4 categories the highest estimate is from a non-US company. Ownership and data residency are separate questions, with their own filters.

Why prices differ

Hard-to-compare bills and hard-to-replace APIs

One vendor charges per host, another per compute-hour. Comparing them means translating your usage into both billing systems. Replacing a proprietary API takes engineering time too, which can make staying put easier even when the bill is higher.

The enterprise premium

Some of the hardest bills to compare are negotiated, not published. Enterprise contracts can also change the commitments, support and features you are buying. Check your contract for:

DNS: a reported contract and a separate worked scenarioIBM NS1 Connect, median contract (Vendr)$49,714/yrAmazon Route 53 at 50 hosted zones, 1B queries / month$5,100/yrDifferent buyers, usage and features: these figures cannot establish savings for the same workload. Read the migration guide →

28 vendor pages here show what companies report paying, with sources.

When it’s worth paying

The cheapest row isn’t always the right one. Stay where you are when:

A higher bill can be worth it. You should be able to explain what the extra money buys.

Migration guides

Migrate site search from Algolia to Typesense Cloud

Move records and search settings to Typesense, connect your InstantSearch UI through an adapter, and compare relevance before switching traffic.

Migrate authentication from Auth0 to self-hosted Keycloak

Move users and passwords, set up production Keycloak, and update your apps to use it. Includes staged cutover and the limits of rolling back to Auth0.

Migrate Linux servers from AWS EC2 to Hetzner Cloud

Check your AWS dependencies, build the Hetzner network and servers, copy data, and switch traffic. Plan database rollback separately from DNS.

Migrate logs, host metrics and APM from Datadog to Grafana Cloud

Send telemetry to both platforms with Grafana Alloy, rebuild dashboards and alerts, and verify coverage before retiring Datadog.

Migrate text-to-speech from ElevenLabs to Inworld TTS

Rebuild voices and streaming calls, check pronunciation and audio formats, and run a blind listening test before a staged rollout.

Move GitHub Actions jobs to Ubicloud runners

Try Ubicloud on one workflow, check images and caching, and compare cost per build. Use a repository variable to switch back without a commit.