Tango VisionBuild modules for cognitive buildings

The 60-second mental model ​

A module is a vertical slice — its own frontend and (optionally) backend — that plugs into the Tango Vision platform. Every module:

1. Declares a manifest (module-manifest.json) the platform validates.
2. Reads platform state through a single injected PlatformContext — never raw tokens or URLs.
3. Optionally publishes/subscribes to events on the platform bus.
4. Optionally contributes Copilot tools the platform AI can call.
5. Reports liveness so the shell knows it's running.

You build against the SDK; the platform enforces the contract. When something doesn't work, the seven contracts make it unambiguous whose side the problem is on.

To see the shape in real code, open tv-module-example — the reference implementation of the contract, kept deliberately minimal — or browse the catalog of 30 production modules built on it.

Not building a module? ​

If you already run a facility-management system, a BMS or a monitoring platform and you just want that data on the building graph, you are in the wrong half of this site. Pushing data in is one endpoint and a few hours — no SDK, no module, no release cycle.

→ Integrations: configuration or development?

Install ​

pnpm add @tv/extension-sdk

The @tv scope is on a private registry that requires a token — see Getting started for the .npmrc setup, including the Docker build-secret pattern.

This is the same contract we build on ​

Thirty modules ship on this SDK today — CAFM, leases, wayfinding, BIM, WiFi-based occupancy, and more. There is no privileged internal API: the first-party modules use the same manifest, the same PlatformContext, and the same federation entry point you get.

→ Browse the module catalog

Where to go next ​

• Getting started — the lay of the land
• Integrations — connect a system you already run
• Your first module — hello-world in 30 minutes
• On-demand sandboxes — your private dev tenant
• Manifest reference — every field explained