Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

GETadb.com

every GET request creates a DB

Details

External ID
48065203
Source
HN
Company
—
Product
GETadb.com
Website domain
getadb.com
Launched
May 8, 2026
Cohort
—
Upvotes
39
Upvotes percentile
0.8174474959612278
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

Hey HN! We made GETadb.com, so it's easier to get agents to build you full stack apps. You don't need to give them any credentials. Just by loading a GET request, they get access to a database, a sync engine, and abstractions for auth, presence, and streams.To see what the agent sees, you can load https://getadb.com/newThere's two fun things about how it's implemented:1. If you curl the home page, it the agent content rather than human content. We do this by detecting the 'Sec-Fetch-Mode' header. It's not perfect, but gets the job done for Claude Code et al.2. For an agent to spin up an app, they make _two_ fethes. (1) getadb.com/guide tells them to generate a uuid, and fetch (2) getadb.com/provision/<uuid>. We did this, because just about half of the popular web-based app builders cache URLs globally, even if you return no-store headers. To get around this we just instruct the agent to generate unique URLsYou may wonder: Why GET requests, rather than POST requests? It's because then you can build in surprising places. For example, we get meta.ai to build an app inside the artifact preview: https://artifacts.meta.ai/share/a/b80c7412-c3af-4088-b430-78efdfe8ea2dUnder the hood, this is possible because the whole infra is mult-tenant from ground up. We already announced how that works on HN, but if you're curious here's the essay for it: https://www.instantdb.com/essays/architecture

Enrichment

Theme
database infrastructure and developer tools
Vertical
Horizontal
Function
Data infrastructure
Audience
Developer
AI stance
Not AI
Project type
Commercial product
Normalized one-liner
create database from http requests
Manually corrected
False

Could you build this?

Partial The GET endpoint proxy is simple, but the backing infrastructure providing ephemeral, secure multi-tenant relational databases with real-time sync is complex distributed systems work.

What it would actually take: The front-facing service generates transient tokens, but the back end requires an orchestration layer (like Fly Machines or microVMs) rapidly spinning up lightweight database containers (or SQLite/Postgres schemas) wired to a real-time reactive sync engine and distributed state layer. Developing secure tenancy, sandbox isolation, and reliable zero-latency data synchronization requires senior distributed systems infrastructure engineering.

Discussion

20 comments analyzed.

Competitors mentioned: InstantDB (similar sync engine and database offering), Supabase (managed database backend alternative), SQLite (simpler backend technology)

Concerns raised: Logo identical to InstantDB, LLM giving UI design instructions outside backend responsibility, Why use this over SQLite backend for simple cases, LLMs unreliable at generating random UUIDs for collision prevention, Supabase authentication and scaling issues

Feature requests: Easy data export to Postgres format, Efficient import/export functionality, Web-based editor with Claude Code/Codex terminal integration, Platform combining database with code editor and preview environment

Competitors

Other products that read as similar to this one — 52 launches clear the similarity bar, closest 8 shown.

Attention rank: #10 of 53 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 140 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a data infrastructure tool for Media & entertainment yet.