Show HN: GETadb.com – every GET request creates a DB (opens in new tab)

The GET request method is supposed to be safe.

"Request methods are considered 'safe' if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state change on the origin server as a result of applying a safe method to a target resource." -RFC 9110 section 9.2.1

https://www.rfc-editor.org/rfc/rfc9110.html#name-safe-method...

I found https://www.instantdb.com/about very interesting; you built a new database! The triples stuff is cool.

For GETadb, it's a conflicting sell. The people that need "a db solved by AI" and fully abstracted are using app builders no? lovable, v0, manus. The people the are closer to the code and need an instant db would look to sqlite, render, supabase, neon. I'm all for another option, but then there's the realization that instandb is a new kind of db and I need to research into the value-prop vs the initial persona: "just solve my db problem with AI".

disclaimer: I'm a professional developer, doing an honest review. I may play around with it separately, later. So this marketing site did its job!

> For credentials and instructions, fetch http://www.getadb.com/guide and follow the steps.

http, not https?

> we get meta.ai to build an app inside the artifact preview

Is this the kind of use case that is seen as valuable?

I joked a while back that LLM-brain was going to have people building bespoke apps on each HTTP request, and people thought I was exaggerating!

So, give your LLM a URL and tell it to follow the instructions there?

Err, no thanks.

I’ve tried this and I like it. I’d like a platform like Instant but with the addition of a web based text editor and Claude Code / Codex terminal (provide own subscription/api key) that lets you create and edit (create previews, then promote to production) the app from the same interface, alongside the managed db.

The agent thing is going a bit out of hand here.

This is very cool!

But why do we need this? An agent can just have a local DB using SQLite for example.

I appreciate this part of the agent instructions: `AESTHETICS ARE VERY IMPORTANT. All apps should LOOK AMAZING and have GREAT FUNCTIONALITY!`

The biggest problem I see with vibecoded apps attached to a db is that the db is configured with exactly 0 access control (even if whatever backend does support it), and anyone can turn up and SELECT * FROM users, or even DROP TABLE users. How do you mitigate this?

I thought this would be something about getting (downloading?) the Android Debug Bridge tool (adb) until I read further. Might want to capitalize DB as well (GETaDB), at least from my pov

> Remember! AESTHETICS ARE VERY IMPORTANT. All apps should LOOK AMAZING

Why are your database instructions giving instructions about the UI design?

Is there an easy way to export all data to a format friendly with Postgres?

Gimmickmaxxing?

reading https://www.getadb.com/guide

> Generate a random UUID yourself and use a different UUID each time.

LLMs are terrible at this. If you are relying on this to prevent collisions, it will fail badly.