Developers
Build on TigerTag.
The TigerTag protocol is open — CC-BY-4.0, with an irrevocable right to implement it in any product, free, forever. Tiger Studio and Tiger-Scale are MIT; the SDKs are Apache-2.0. The mobile app is free to use, but proprietary.
- 1
An open protocol
Any NTAG 213/215/216, any ACR122U reader, bought anywhere. The Pod is 3D-printed — print it yourself.
- 2
TigerTag is 100% offline
The data lives on the chip. No cloud, no account, nothing phones home.
- 3
TigerTag+ adds an optional online layer
The same offline chip, plus a catalogue entry its manufacturer maintains. Optional. Additive. Never a dependency.
- 4
TigerData
For spools with no chip at all: tracked in the app, upgradeable to a real chip anytime.
- 5
The ecosystem
Desktop and mobile apps, the Pod, the Scale. Installs in a minute — no self-hosting required.
- 6
Factory partners
Filament that arrives already knowing what it is, tagged on the production line.
- 7
The tag outlives the spool
Rewrite it onto the next spool, or reflash it as a plain NDEF tag.
What is open, component by component
Verified against the public repositories.
| Component | Licence | Notes |
|---|---|---|
| Protocol spec | CC-BY-4.0 | The protocol specification and the public registry tables. LICENSING.md carries an irrevocable, worldwide, royalty-free implementation grant. |
| Tiger Studio | MIT | The desktop app. Fork it, sell it — just don't call your fork Tiger Studio. |
| Tiger-Scale | MIT | The scale firmware (ESP32). |
| TigerPOD | CC-BY-4.0 | The Pod, presented: free design, free electronics — two ACR122U readers, a printed shell, a splitter. |
| SDK-JS | Apache-2.0 | JavaScript SDK. Apache-2.0 carries an express patent grant. |
| SDK-Python | Apache-2.0 | Python SDK. Same terms as the JS SDK. |
| Firebase integration | CC-BY-4.0 | Integration reference for third parties: security-rules mirror and data model. |
| Mobile app | Proprietary | Free to use. Not open source. |
公开 API
产品目录无需密钥即可读取。这些正是本站自身所使用的接口——目录页和每个产品页都由它们生成，所以你拿到的和我们拿到的完全一样。
- POST
https://api.tigertag.io/api:tigertag/product/get/allThe whole catalogue, paged.
- GET
https://api.tigertag.io/api:tigertag/product/get?product_id=<id>&lang=<xx>One product: EAN, description, print settings, datasheets.
- GET
https://cdn.tigertag.io/img?id=<id>&size=largeProduct image (compact · medium · large).
目录接口没有“一次返回全部”的模式：请按响应中给出的 {nextPage} 逐页翻取，直到它为 null。
打开 API 参考文档（Swagger） ↗Free protocol, guarded name
任何人都可以实现该协议，并声明「兼容 TigerTag」。只有 TigerTag Certified 合作伙伴才能在产品上使用 TigerTag 名称与标志，并签发 TigerTag+ 签名——私钥由 TigerTag 保管。两道门：商标（市场）与签名（技术）。两者都没有对协议本身加上任何限制。
未认证的芯片一样能完美工作——离线、任意 App、所有已支持的打印机。它只是无法证明自己的来源。免费层是真的能用；认证层负责证明。
基于 TigerTag 构建
已经有人在它之上构建了。
这些独立项目读了公开的规范，然后自己做了出来。没有合作关系，没有背书，没有认证——只是一套开放协议在做它该做的事。
关于固件，需要说准确：目前还没有任何原厂打印机固件能原生读取 TigerTag。这个社区固件已经可以。
OpenRFID
github.com/suchmememanyskill
一个社区工具包，能读取多个厂商的料卷标签，TigerTag 是其中之一——开放的数据格式让接入变得很直接。
查看项目 →Spooly Tracker
spoolytracker.com
一个独立的线材库存平台——网页、移动端、Home Assistant、OrcaSlicer，可自建部署。它用 TigerTag 来识别料卷。
查看项目 →Snapmaker U1 Extended Firmware
GPL-3.0 · 850+ ★
第一台原生读取 TigerTag 的打印机
一个面向 Snapmaker U1 的独立社区固件。装上它，U1 就能在机器本身上读取 TigerTag。
查看项目 →
你也在基于 TigerTag 构建？ 告诉我们——如果你希望集成得到验证，TigerTag Certified 就是为此存在的。 加入 Discord →