# Competitive Landscape | Category | Example Projects | How TaτsuOS Differs | | ------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | | DePIN networks | Helium, IoTeX, DIMO | Those projects pay devices to produce data. TaτsuOS gates the capabilities a user paid for. Complementary, not competitive. | | Device-as-NFT identity | Various NFT-based device registries | TaτsuOS is concerned with feature entitlements, not with tokenizing the device itself. | | Fleet management SaaS | Particle, Memfault, Golioth | These are excellent products, but their entitlement model is a centralized account. TaτsuOS makes entitlements cryptographic and portable. | | License-server middleware | Sentinel, FlexLM-style stacks | These are exactly the model TaτsuOS is designed to replace: revocable, server-bound, vendor-captured. | The closest philosophical analogue is the open-firmware movement (OpenWrt, Tasmota, ESPHome). TaτsuOS is sympathetic to that movement, and the firmware is permissively licensed. The difference is that TaτsuOS is the first to attach a cryptographically enforceable economic primitive to that openness. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://tatsu.gitbook.io/tatsu-whitepaper/competitive-landscape.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.