The platforms beneath the work. Software we build once, refine across projects, and maintain for the life of every installation.

Interactive works that have to run for a decade or more can’t be built from scratch every time. Sitara’s installations ship on shared platform infrastructure — content, behavior, and operations layers that carry the lessons of every previous project into the next one.

Galaxy — content management for public space

Galaxy is the content layer: what appears on an installation’s displays, and who controls it. It’s built for the realities of public space rather than the web — accessibility in the content model, editorial governance in the publishing workflow, and content institutions update for years without a developer. It runs daily at the Yale Peabody Museum, the Port of Long Beach, and the Dana-Farber Cancer Institute, and it screened every visitor submission at Genesis House’s Manifesting Marilyn before it reached the wall. About Galaxy →

Fusion — public computing on Unreal Engine

Fusion is Sitara’s custom toolkit for public computing — computing you inhabit with strangers — built on top of Unreal Engine: the layer that makes a game engine behave like public infrastructure: interfaces that voice themselves because a kiosk has no screen reader, experiences that reset for every visitor, content the institution controls, and the serviceability a 12+ year life demands. About Fusion →

Starwatch — operations and observation

Starwatch is the operations layer: it monitors installations, recovers them when something goes wrong, updates them safely — every update reversible — and reports on their health — so a gallery doesn’t need a technician in the room. It’s how a nine-week exhibition ran daily with no on-site technical staff, and it’s the same platform beneath installations designed for a 12+ year operational life. About Starwatch →

Kepler — museum-controlled AI for collections

Kepler is an upcoming open-core recognition engine for museum collections: point a camera at an object and get back which object it is — or an honest “not confident enough,” never a confident wrong answer. Shaped the way the field needs its tools: reusable like a product, calibrated to each institution’s own collection, and open-core so it outlives any single steward. About Kepler →

Why platforms

Our thesis is that exhibits are long-lived infrastructure. Platforms are how we practice it: a shared, maintained foundation means each installation inherits years of hardening instead of starting over — and keeps working long after opening day. It’s the same principle behind how we work and the discipline we practice.

Have a commission in mind? Start the conversation →