SaaS
Instant
Instant, the open-source realtime database and backend-as-a-service, is winding down its hosted Instant Cloud after the team joins OpenAI — new signups are closed and all cloud apps shut down on 31 August 2027, with self-hosting the migration path
departs 31 Aug 2027
Quick answers
- Is it true that InstantDB (Instant Cloud) is shutting down after the team joins OpenAI?
- Yes. Instant has officially announced it, effective 31 Aug 2027. Instant (InstantDB) is a realtime, client-side database and backend-as-a-service — a Firebase-style stack with a reactive database, auth, storage, a sync engine, and admin SDK, consumed through the `@instantdb/react`, `@instantdb/core`, `@instantdb/admin`, and `@instantdb/react-native` packages.
- When does it take effect?
- 31 Aug 2027. Verified against the vendor's own announcement.
- What should I use instead?
- You have real runway — until 31 August 2027 for live apps, and backups through 31 August 2028 — but the safe move is to plan the migration now rather than in the final months.
What this means for you
Instant (InstantDB) is a realtime, client-side database and backend-as-a-service — a Firebase-style stack with a reactive database, auth, storage, a sync engine, and admin SDK, consumed through the `@instantdb/react`, `@instantdb/core`, `@instantdb/admin`, and `@instantdb/react-native` packages. The team has announced it is joining OpenAI, and the hosted **Instant Cloud** service is winding down. New signups are already closed. **On 31 August 2027 all cloud apps shut down**; existing users are told to migrate off Instant Cloud within roughly the next 12 months. Backups stay available for a further 12 months, until **31 August 2028**, and any subscription started after 31 July 2026 is being fully refunded. The important nuance is that only the *hosted* service is ending: Instant is fully open source, so this is a hosting shutdown, not a dead product. Any app that reads and writes through Instant Cloud — the default hosted backend most Instant apps use — stops working on the cloud cutoff unless it has been moved to a self-hosted Instant instance or another backend first. Because the SDKs point at Instant Cloud by default, a project can depend on it without anyone having flagged it as a hosted dependency, which is exactly the kind of thing that surfaces late.
Where to go
You have real runway — until 31 August 2027 for live apps, and backups through 31 August 2028 — but the safe move is to plan the migration now rather than in the final months. Because all of Instant is open source, the vendor's recommended path is to **self-host Instant**: they have published a self-hosting and migration guide, and the SDK surface (`@instantdb/react`, `@instantdb/core`, `@instantdb/admin`) stays the same, so the change is repointing your app at your own Instant server rather than rewriting your data layer. Stand up a self-hosted instance (VPS, AWS, or your own infra), migrate your data and verify auth/storage/sync against it, then cut the client config over well before the cloud shutdown. If you would rather leave Instant entirely, budget for a larger rewrite onto another realtime BaaS or database (see alternatives), since that means re-implementing the reactive queries, auth, and sync your app relies on. Either way, export and keep a copy of your data before the 31 August 2028 backup deadline.
- Self-host Instant — it is fully open source; the official guide keeps the same SDKs and repoints them at your own server (the vendor-recommended path)
- Another realtime backend-as-a-service (e.g. Supabase, Firebase / Firestore, Convex, PocketBase, Appwrite) — a larger rewrite of queries, auth, and sync
- A conventional database plus your own sync/realtime layer, if you want full control over hosting and data
If you build with Instant (InstantDB) — the open-source realtime database that gives a React or React Native app a reactive backend with auth, storage, and sync out of the @instantdb/react and @instantdb/core packages — the hosted side of it is ending. In an official announcement, the Instant team said it is joining OpenAI, and that Instant Cloud is winding down.
The dated facts, straight from Instant: new signups are closed, existing users should migrate off Instant Cloud within about the next 12 months, and on 31 August 2027 all cloud apps shut down. Backups stay available for a further year, until 31 August 2028, and any subscription started after 31 July 2026 is being fully refunded. If your app talks to Instant Cloud — which is the default hosted backend most Instant apps use — that connection stops on the cloud cutoff unless you have moved first.
The saving grace is that this is a hosting shutdown, not a dead product. All of Instant is open source, and the team’s recommended path is to self-host it: they’ve published a self-hosting and migration guide, and because the SDK surface is unchanged, the migration is mostly standing up your own Instant server and repointing the client, not rewriting your data layer. Stand up a self-hosted instance, move and verify your data, then cut over well before the 2027 deadline.
If you’d rather leave Instant altogether, that’s a bigger job — another realtime backend such as Supabase, Firebase/Firestore, Convex, PocketBase, or Appwrite means re-implementing the reactive queries, auth, and sync you get from Instant today. Whichever route you take, the one hard deadline that’s easy to forget is the backup window: export and keep your data before 31 August 2028.
This one sat on our watch list for weeks as an unverified, email-only rumor — we don’t publish shutdowns off a forwarded email. It’s here now because Instant has said it publicly, on its own site, with dates.
Entry changelog
- — last reviewed.
- — Entry created from Instant's official announcement, "The Instant team joins OpenAI," and the site-wide sunset banner. Primary source states: the team is joining OpenAI; new signups closed; existing users should migrate off Instant Cloud within ~12 months; subscriptions started after 31 July 2026 fully refunded; all cloud apps shut down 31 August 2027; backups available until 31 August 2028; self-hosting is the recommended migration (Instant is open source). This confirms a wind-down that had previously circulated only via a forwarded email (watch item B-071) — now sourced to Instant's own site.
Put this countdown in your README
Building on Instant? Drop this badge into a project’s README or docs — it shows the days left and
refreshes on its own every night from this page. 
[](https://lastcall.dev/entries/instantdb-cloud-shutdown)Spot an error or a changed date? Tell us and it’s corrected the same night.