Supabase offers InstantDB migration path

This is a useful off-ramp for InstantDB users, but the migration caveat is significant: Supabase says InstantDB’s closed sign-ups prevented full end-to-end testing.

• –Requires a fresh, blank Supabase project, reducing the risk of overwriting an existing database
• –Preserves the source app and backup while importing data into Postgres, Auth, and Storage
• –Generated SQL migrations make the resulting schema easier to version-control and review
• –InstantDB’s cloud sunset gives existing users a concrete reason to evaluate migration options
• –Developers still need to validate permissions, application behavior, and feature parity after import