[HN Gopher] Instant 1.0, a backend for AI-coded apps
___________________________________________________________________
Instant 1.0, a backend for AI-coded apps
Author : stopachka
Score : 33 points
Date : 2026-04-09 18:30 UTC (4 hours ago)
(HTM) web link (www.instantdb.com)
(TXT) w3m dump (www.instantdb.com)
| ladon86 wrote:
| Looks very nice! I'll give it a spin for prototypes.
|
| Would love to check out /docs but it's currently a 404.
| nezaj wrote:
| Docs should be working now! If anyone else has issues please
| let us know!
| chrysoprace wrote:
| Is InstantDB no longer about local-first or is the AI angle just
| a marketing thing?
| dghlsakjg wrote:
| This looks like a blog post highlighting that this can be used
| for vibecoded apps, not necessarily a pivot on the product.
| nezaj wrote:
| We built Instant to optimize for two things:
|
| We wanted to make a tool that (a) would make it easy to build
| delightful apps, and that (b) builders would find easy to use.
|
| This got us into making things that touch both local-first and
| AI.
|
| On the local-first side, we took on problems like offline-mode,
| real-time, and optimisitc updates.
|
| On the AI side, we built a multi-tenant abstraction, so you can
| spin up as many apps as you like, and focused on great DX/AX so
| agents found Instant easy to use too.
| jamest wrote:
| They actually deliver on the promise of "relational queries &&
| real-time," which is no small feat.
|
| Though, their console feels like it didn't get the love that the
| rest of the infra / website did.
|
| Congrats on the 1.0 launch! I'm excited to keep building with
| Instant.
| stopachka wrote:
| Thank you! We spent a lot of time with the demos on the home
| page, the essays page, and upgrading the docs.
|
| We're going to redesign the dashboard in the next few weeks.
|
| One interesting observation from our users: though they use the
| dashboard less in some ways (the AI agents spin up apps and
| make schema changes for them), we found people use them _more_
| in other ways. Instant comes with an Explorer component, which
| lets you query your data. We found users want to engage with
| that a lot more.
| asdev wrote:
| I wonder if people really need this. How many people are really
| building multiplayer apps like Figma, Linear etc? I'm guessing
| 99% are CRUD and I doubt that will change. Even if so, would you
| want to vendor lock into some proprietary technology rather than
| build with tried and tested open source components?
| nezaj wrote:
| For what it's worth, Instant is 100% open source!
|
| https://github.com/instantdb/instant
| stopachka wrote:
| > really building multiplayer apps like Figma, Linear
|
| I think there's two surprises about this:
|
| 1. If it was easier to make apps multiplayer, I bet more apps
| would be. For example, I don't see why Linear has to be
| multiplayer, but other CRUD apps don't.
|
| 2. When the abstraction is right, building apps with sync
| engines is easier than building traditional CRUD apps. The
| Linear team mentioned this themselves here:
| https://x.com/artman/status/1558081796914483201
| risyachka wrote:
| Yeah I kinda agree. Considering llms write most of the code
| today, the need for fancy tech is lower than ever. A good old
| crud app looks like a perfect fit for ai - its simple,
| repetitive and ai is great at sql. Go binary for backend and
| react for frontend - covers 99.9% use cases with basically zero
| resource usage. 5 usd node will handle 100k mau without
| breaking a sweat.
| ghm2199 wrote:
| For people like me -- who are kind of familiar with how
| react/jetpack compose/flutter like frameworks work -- I recall
| using react-widget/composables which seamlessly update when these
| register to receive updates to the underlying datamodel. The
| persistence boundary in these apps was the app/device where it
| was running. The datamodel was local. You still had to worry
| about making the data updates to servers and back to get to other
| devices/apps.
|
| Instant crosses that persistence boundary, your app can propagate
| updates to any one who has subscribed to the abstract datastore
| -- which is on a server somewhere, so you the engineer don't have
| to write that code. Right?
|
| But how is this different/better than things like, i wanna say,
| vercel/nextjs or the like that host similar infra?
| stopachka wrote:
| I would say NextJS focuses a lot more on server-rendering. If
| you use the app router, the default path is to render as much
| as you can on the server.
|
| This can work great, but you lose some benefits: your pages
| won't work offline, they won't be real-time, and if you make
| changes, you'll have to wait for the server to acknowledge
| them.
|
| Instant pushes handles more of the work on the frontend. You
| make queries directly in your frontend, and Instant handles all
| the offline caching, the real-time, and the optimistic updates.
|
| You can have the best of both worlds though. We have an
| experimental SSR package, which to our knowledge is the first
| to combine _both_ SSR and real-time. The way it works:
|
| 1. Next SSRs the page
|
| 2. But when it loads, Instant picks it up and makes every query
| reactive.
|
| More details here: https://www.instantdb.com/docs/next-ssr
| nharada wrote:
| This is super cool and exactly what I've been looking for for
| personal projects I think. I wanna try it out, but the "agent"
| part could be more seamless. How does my coding agent know how to
| work this thing?
|
| I'd suggest including a skill for this, or if there's already one
| linking to it on the blog!
| nezaj wrote:
| We do have a skill!
|
| npx skills add instantdb/skills
|
| Would recommend doing `bunx/pnpx/npx create-instant-app` to
| scaffold a project too!
| LoganDark wrote:
| Can I view the source code of this skill / install it
| manually? I am incredibly not a fan of automated installers
| for this type of stuff.
| nezaj wrote:
| You can! The skill lives here
|
| https://github.com/instantdb/skills
| minantom wrote:
| how is this better than vercel?
___________________________________________________________________
(page generated 2026-04-09 23:00 UTC)