Skip to content

Open ecosystem philosophy

Every layer of TigerSystem is published — hardware, firmware, SDKs, apps, docs:

Layer Project License
Desktop app Tiger Studio Manager MIT
JS SDK (npm tigertag) TigerTag-SDK-JS Apache-2.0
Python SDK TigerTag-SDK-Python Apache-2.0
Scale hardware + firmware (V3, current) Tiger-Scale-V3 MIT
Scale hardware + firmware (V2) Tiger-Scale MIT
Reader stand (STL + docs) TigerPOD CC BY 4.0
Chip format guide TigerTag-RFID-Guide CC BY 4.0
Cloud integration docs TigerTag_Firebase_Integration CC BY 4.0
This documentation TigerSystem-Docs CC BY 4.0

The whole user-facing ecosystem is deliberately a laboratory, not the destination. Every product — Tiger Studio, the mobile app, TigerScale, TigerPOD — is a working demonstration of what open, documented technology makes possible once a spool can identify itself: live printer telemetry across six brands, physical rack mapping, sensors, shared inventories. Some of it will mature, some of it exists to prove a point, and all of it is readable, forkable and free to copy. Every product — current and future — is a proof of concept of an open-source, standard, agnostic, cross-platform protocol: its only job is to show the potential, so that anyone can take our integration work as inspiration and imagine the features of tomorrow.

TigerTag is an open protocol, not a platform you have to join:

  1. Read the chip format (TigerTag-RFID-Guide).
  2. Pick up an SDK.
  3. Connect to the cloud — or don’t; chips work offline.
  4. Ship the software, the hardware or the business you actually want.

Your app can be something else entirely — it will still speak the same chips. An NFC phone, an ACR122U USB reader — or a DIY ESP32 with a PN532/RC522 module, TigerScale-style — is all the hardware it takes: plug spool identity into an ERP, an internal stock tool, a tracking workflow, a fablab lending system, a private or public R&D project — anything.


Related: Developer overview, Products