ResolveDB

Built for Real-World Use

ResolveDB turns DNS infrastructure into a globally distributed data layer. Explore how teams use it to solve real problems.

Model Registry Without the Bottleneck

10,000 GPU nodes query your registry simultaneously. DNS caching means 1 origin request. Not 10,000.

dig TXT
get.llama-70b.models.inference.v1.resolvedb.net
  • Zero thundering herd - autoscaling events don't flood your registry
  • 10,000 nodes = 1 origin request per TTL period
  • Sub-5ms discovery from cache (vs 50-200ms API calls)
Explore

Factory Floor Config Without HTTP Stacks

Push configuration to thousands of PLCs, sensors, and edge devices using only the DNS they already have.

dig TXT
get.bdt-a7f3b2c4e8d9f012a7f3b2c4e8d9f012.config.acme-factory.v1.resolvedb.net
  • Zero information leakage - tokens are random 128-bit hashes (2^128 search space)
  • Per-device encryption - config encrypted with device-specific key via AES-256-GCM
  • Works on any device with DNS - HMAC-SHA256 is hardware-accelerated on most MCUs
Explore

Feature Flags That Cost Nothing at Scale

DNS caching means 10,000 users checking a flag = 1 origin request. Works in shell scripts, cron jobs, edge functions - anywhere DNS works.

dig TXT
get.payments-v2.flags.myapp.v1.resolvedb.net
  • 10,000 users = 1 origin request per TTL (DNS caching multiplier)
  • Zero cold start - DNS resolution is in every language stdlib
  • Works everywhere: bash, cron, edge functions, any language
Explore

Tenant-Isolated Config at Global Scale

Serve per-tenant configuration to millions of users with cryptographic namespace binding.

dig TXT
get.sig-a3f2e8c1d4b5a678-t-1704067200.config.acme-corp.v1.resolvedb.net
  • Cryptographic isolation - cross-tenant access is mathematically impossible
  • Bug-proof - works even if authorization code has bugs
  • Auditable - namespace hash in signature enables forensics
Explore

CMS Content at Edge Cache Speed

Serve headless CMS content from the DNS caching layer. NULL records for up to 64KB. Global TTL, zero origin load, sub-5ms delivery.

dig TXT
get.h-a3f2e8c1d4b5a678901234567890abcd.homepage.content.myblog.v1.resolvedb.net
  • Content-addressed integrity - SHA-256 hash prefix prevents cache poisoning
  • Zero origin load for popular content - DNS caching handles traffic spikes
  • 64KB per record (NULL) - most articles fit in a single query
Explore

Have a different use case?

ResolveDB works anywhere DNS works. If you can make a TXT query, you can use ResolveDB.

Start BuildingRead the Docs