Skip to main content

TSS' Open Architecture

We’re introducing an open architecture that makes TSS more flexible, stable, and ready for interactive experiences. It lays the foundation for easier integrations and gives every role more freedom to build, run, and scale experiences over time.

Our open architecture is the foundation for the next phase of The Storytelling Suite. It is designed to give creators, room leads, and organisations more freedom to build interactive and immersive experiences, while keeping the platform stable, predictable, and easy to evolve.

This is not a single feature or release. It is a deliberate shift in how TSS is structured, so future capabilities become possible, scalable, and sustainable.


Why an Open Architecture

As TSS grows, so does the diversity of use cases, rooms, and integrations. To support this, the platform needs to be more open, more modular, and less complex behind the scenes.

The open architecture is designed to:

  • Enable easier connections with sensors, triggers, and external tools.

  • Allow teams and organisations to build integrations themselves.

  • Reduce dependency on the core product team for custom setups.

  • Create a more predictable and reliable platform for daily operation.

  • Provide a strong foundation for future roadmap items that rely on interaction and integration.


Strategy: Fewer, Clearer Building Blocks

We are moving away from a spread of overlapping components toward a simpler set of building blocks, each with a clear responsibility.

This approach:

  • Reduces coupling between components.

  • Makes the platform easier to maintain and troubleshoot.

  • Improves stability across setups and locations.

  • Allows changes and extensions without affecting unrelated parts of the system.

At the center of this setup is the Gateway.


The Role of the Gateway

The Gateway acts as the central communication hub within TSS.

It provides a consistent way to:

  • Connect sensors and physical triggers.

  • Integrate external tools and data sources.

  • Exchange requests and events between components.

By routing interactions through a single, well-defined entry point, the platform becomes more flexible without becoming more complex.


What This Unlocks

With this foundation in place, a wide range of possibilities becomes realistic over time. What this means differs slightly per role:

For the Story Builder

  • More freedom to compose stories that react to audience input and context.

  • Less friction when combining content, triggers, and interactions.

For the Experience Builder

  • Easier orchestration of interactive elements.

  • Greater flexibility to evolve experiences without reworking the entire setup.

For the Experience Engineer

  • Clear integration points for sensors, external sources, and custom logic.

  • A predictable architecture with well-defined responsibilities per component.

For the Experience Center Manager

  • Improved stability and predictability across setups and locations.

  • A foundation that supports growth while maintaining control and reliability.

These outcomes will be delivered incrementally. The open architecture ensures that when new capabilities are introduced, they fit naturally into the platform.


What to Expect

The open architecture is a long-term investment in flexibility, stability, and growth.

You may not always see it directly, but it enables:

  • More confidence when scaling experiences across rooms and locations.

  • More room for experimentation and innovation.

  • A platform that grows with your ambitions, rather than limiting them.

This foundation allows TSS to support increasingly interactive, connected, and immersive storytelling experiences, now and in the future.

Did this answer your question?