Since this discussion pops up in both ChatGPT and Manus for this topic… I’ll chime in with the feature request I just submitted… it includes the cases here…
Name of app or file format and URL:
Supabase — real-time / bidirectional integration
Use case:
We are building an immersive, participatory storytelling platform that crosses AI experiences (including ChatGPT), live events, community activities, media, wearables, and in-person experiences.
We would like to use Fibery as the business-user control plane for the live experience, while Supabase serves as the production backend for player/user accounts, session state, interactions, research data, and other runtime data.
For our use case, periodic synchronization would not be sufficient. We need authorized nontechnical operators in Fibery to be able to make certain changes and have them reflected in the live product immediately or near-immediately, without waiting for a scheduled sync or requiring a developer deployment.
Examples include:
-
publishing or updating story/world content, lore, prompts, activities, and configuration;
-
changing content or configuration in an active projection-screen display/app, game, or immersive theater experience while participants are using it;
-
opening, closing, replacing, or modifying participant research/data-collection questions;
-
viewing relevant live player/session state and correcting an individual participant’s state when something goes wrong;
-
pausing or changing a broken experience affecting an active group;
-
publishing time-sensitive announcements or interventions;
-
seeing whether a change successfully reached the production system;
-
versioning and rolling back changes quickly when necessary.
The operational environment makes latency especially important. Some experiences will run at live conferences and in-person community events, where organizers may have paying participants physically waiting while they diagnose and correct an experience. “Change it now and know that it worked” is a core requirement, not just a convenience.
We do not necessarily need every piece of high-volume product telemetry copied into Fibery in real time. Supabase can remain the source of truth for production/runtime data. What we need is a reliable real-time path for the subset of data and commands that business users need to observe and operate the live experience from Fibery.
Ideally, the integration would support:
Fibery → Supabase
Real-time create/update actions or explicit publish/command actions, with success/failure confirmation.
Supabase → Fibery
Real-time or event-driven updates for selected records/events that require human visibility or intervention.
Operational safety
Stable IDs, relationships, timestamps, version information, permissions, error reporting, and enough support for rollback/audit history that operators can safely make live changes.
The larger reason we’re requesting this integration is organizational: we want developers to build the underlying product capabilities and integration contracts once, while writers, researchers, producers, community organizers, and other business users can operate and evolve the experience without requiring engineering work for every content, configuration, research, or live-operations change.
Traditional CRM/customer-support integrations such as Zendesk or Intercom do not fit this use case. We aren’t primarily managing support tickets. We’re managing the continuity and operation of a live participatory world in which story state, AI interactions, participant state, research, real-world events, and human interventions can affect one another.
A native Supabase integration with strong real-time/event-driven support would make Fibery substantially more viable as the operational workspace for this kind of product.
