数据包测试
一个简单的问题决定了您是否需要商业许可证：您的数据来自哪里？
在无限个设备上免费使用许可软件，用于任何目的，包括商业用途。
联系Anka Labs商讨商业安排。定价、部署范围和服务级别协议将单独协商。
非Sandstar设备可以与Sandstar控制器共存于同一建筑内——重要的是它们的数据是否流入许可软件。如果Mobilytik仅显示Sandstar源数据，走廊里的BACnet冷却机与您的许可证无关。
此许可证涵盖的应用
Anka Labs为Project Sandstar生态系统发布的每个应用都受PSSL v1.1管制——包括下面列出的所有当前和未来应用。
Mobilytik
用于Haystack数据浏览、仪表板构建、设备条形码扫描和离线计量的移动应用。
Visualytik
使用Haystack块编程方法的仪表板和可视化生成器。
Sandstar Port Manager
硬件I/O抽象、记录编辑和通道到标签映射工具。
Sandstar Web Editor
基于浏览器的Sedona块编程环境，使用WebSocket通信。
Sandstar Sox WebSocket应用
Sox UDP到WebSocket网桥和实时设备通信应用。
Axon MCP服务器
可AI查询的Axon知识库，具有语义搜索、嵌入和SkySpark集成。
MCP Fantom
Fantom文档、语义代码搜索和通过MCP的SkySpark迁移协助。
Sedona MCP服务器
对Sedona、Sandstar和SkySpark数据的多协议统一MCP访问。
Anka Labs为Project Sandstar生态系统发布的所有应用——当前和未来——都受PSSL v1.1管制。Project Sandstar引擎本身（Sedona Framework + Haystack集成）仍然是完全开源的，不受此许可证管制。
符合条件的使用 vs 不符合条件的使用
哪一个适用于您？流入许可软件的数据决定了这一点。
许可软件消费的每个数据包都可以追溯到运行Project Sandstar Sedona + Haystack的控制器。您将获得：
- 允许商业使用——在生产中部署、向客户收费、在Sandstar上建立业务
- 研究源代码——学习、检查、调试和理解它的工作方式
- 修改和扩展——使其成为您自己的、添加功能、为您的工作流进行自定义
- 分发衍生作品——与第三方共享（收件人也必须符合条件）
- 无限部署——没有设备限制、没有座位限制、没有费用
无版税。无需将修改内容贡献回来的义务。只需继续使用Sandstar数据。
任何非Sandstar数据到达许可软件的时候——直接地或通过网关、代理或Haystack服务器。非Sandstar数据示例：
- BACnet控制器（BACnet/IP、MS/TP、SC）
- Modbus控制器（TCP、RTU）
- LonWorks / LonTalk设备
- KNX设备
- Niagara Framework（作为主要控制平台）
- 专有或供应商特定的控制器
- MQTT / OPC-UA设备作为主要接口
源头很重要，而不是格式。将BACnet数据重新标记为Haystack不会改变其源头——它仍然是非Sandstar数据。
场景指南
真实的部署，真实的答案。找到与您相匹配的场景。
全Sandstar建筑
建筑有20个Sandstar控制器。Mobilytik显示来自所有控制器的数据。每个数据包都来自Sandstar。符合免费使用条件。
混合建筑、过滤视图
同一建筑有Sandstar + 5个BACnet控制器。Mobilytik仅显示Sandstar数据；BACnet通过其他工具管理。共存没有问题。
单一窗格统一视图
Mobilytik显示来自所有25个控制器的数据。非Sandstar数据流入许可软件。需要商业许可证。
重新标记的网关数据
(re-tag) → Visualytik
网关将BACnet数据转换为Haystack标记的记录。Visualytik使用它们。源头很重要——重新标记不会使BACnet数据成为
SkySpark混合、过滤查询
SkySpark聚合混合源，但Visualytik配置为仅查询Sandstar源记录。没有非Sandstar数据到达Visualytik。符合条件的使用。
SkySpark混合、所有记录
相同的SkySpark设置，但Visualytik查询所有记录并显示所有内容。Modbus数据到达Visualytik。需要商业许可证。
Full License Text
The complete PSSL v1.1. Click any section to expand.
Preamble
Project Sandstar merges two open-source technologies — the Sedona Framework and Project Haystack — into a unified, hardware-agnostic control and data platform for smart buildings and IoT devices. Anka Labs, Inc. ("Licensor") has developed a suite of applications that operate northbound of this open foundation.
This license governs the use of those northbound applications. It is designed to keep the Sandstar ecosystem open and accessible to those who build within it, while requiring a commercial arrangement for those who use these applications to consume, display, or interact with data that did not originate from the Project Sandstar hardware-agnostic controls ecosystem.
This is a Source-Available License. It is not an Open Source license as defined by the Open Source Initiative (OSI). The source code is visible, readable, and modifiable, but usage rights are conditional based on the origin of data consumed by the Licensed Software.
1. Definitions
1.1 "Licensed Software" means the following applications, including their source code, binaries, documentation, and any updates published by the Licensor under this license:
- (a) Mobilytik — Mobile application for Haystack data browsing, dashboard building, equipment barcode scanning, and offline metering.
- (b) Visualytik — Dashboard and visualization builder utilizing Haystack block programming methodologies.
- (c) Sandstar Port Manager — Hardware I/O abstraction, record editing, and channel-to-tag mapping tool.
- (d) Sandstar Web Editor — Browser-based Sedona block programming environment utilizing WebSocket communication.
- (e) Sandstar Sox WebSocket Apps — Sox UDP-to-WebSocket bridge and real-time device communication applications.
1.2 "Project Sandstar" means the open-source control engine that merges the Sedona Framework with Project Haystack, as maintained at the official Project Sandstar repositories, including the Sandstar C/C++ engine, the eacio Sedona kit, device templates, and Zinc grid configurations.
1.3 "Sedona Framework" means the open-source software environment for building smart, networked, embedded devices, including the Sedona Virtual Machine (SVM), the Sox protocol, Sedona component model, and associated kits, as maintained by the Sedona Alliance or its successors.
1.4 "Project Haystack" means the open-source semantic data modeling standard for IoT data, including Haystack tag definitions, Zinc data format, filter syntax, and the Haystack REST API (Ops), as maintained by Project Haystack or its successors.
1.5 "Sandstar-Origin Data" means any data packet, record, point value, command, or data stream that originates from a controller or device running the Project Sandstar engine with both:
- (a) The Sedona Framework (SVM) for control programming; and
- (b) Project Haystack tags and the Haystack REST API as the data model and communication interface; and
- (c) Hardware-agnostic control logic consistent with the eacio kit model, where control programming is separated from hardware-specific definitions.
For a data packet to qualify as Sandstar-Origin Data, the physical device or controller that generated the underlying sensor reading, control output, or computed value must itself be running the Project Sandstar engine with Sedona and Haystack as specified above.
1.6 "Non-Sandstar Data" means any data packet, record, point value, command, or data stream that originates from a device, controller, or system that is NOT running the Project Sandstar engine with Sedona and Haystack — regardless of whether that data has been subsequently converted, translated, imported, proxied, or re-tagged into Haystack format by an intermediary system. Non-Sandstar Data includes, but is not limited to, data originating from:
- (a) BACnet controllers or devices (BACnet/IP, BACnet MS/TP, BACnet SC)
- (b) Modbus controllers or devices (Modbus TCP, Modbus RTU)
- (c) LonWorks / LonTalk devices
- (d) KNX devices
- (e) Niagara Framework controllers (when operating as the primary control platform rather than as a transparent pass-through for Sandstar controllers)
- (f) Any proprietary or vendor-specific controller or device
- (g) Any device communicating via MQTT, OPC-UA, or other protocols as its primary control interface, where the device itself does not run the Sandstar engine
1.7 "Qualifying Use" means use of the Licensed Software in which the Licensed Software exclusively consumes, displays, interacts with, and operates upon Sandstar-Origin Data. A deployment constitutes Qualifying Use when every data packet rendered, visualized, browsed, edited, or acted upon by the Licensed Software can be traced back to a Project Sandstar hardware-agnostic controller running Sedona and Haystack.
1.8 "Non-Qualifying Use" means any use of the Licensed Software in which the Licensed Software consumes, displays, interacts with, or operates upon any Non-Sandstar Data — whether exclusively or in combination with Sandstar-Origin Data. This includes, without limitation:
- (a) Displaying Non-Sandstar Data on a Mobilytik dashboard alongside Sandstar-Origin Data.
- (b) Creating a unified visualization in Visualytik that includes data points from both Sandstar controllers and BACnet or Modbus devices.
- (c) Routing Non-Sandstar Data through a Haystack server (such as SkySpark) and then consuming that re-tagged data in the Licensed Software.
- (d) Using the Licensed Software as a single-pane-of-glass view that aggregates data from both Sandstar and non-Sandstar systems.
- (e) Feeding data from legacy protocols into the Licensed Software via any translation, gateway, or proxy layer.
1.9 "You" / "Licensee" means the individual or legal entity exercising rights under this license.
1.10 "Licensor" means Anka Labs, Inc., or its authorized successors and assigns.
2. Grant of Rights — Qualifying Use
Subject to the terms of this license, the Licensor grants You a worldwide, non-exclusive, royalty-free, non-transferable right to:
(a) Use the Licensed Software for any purpose, including commercial purposes, provided the Licensed Software exclusively consumes Sandstar-Origin Data (Qualifying Use).
(b) Study the source code of the Licensed Software, inspect its operation, and learn from its design.
(c) Modify the Licensed Software and create derivative works for use within Qualifying Use deployments.
(d) Distribute the Licensed Software and derivative works to third parties, provided that:
- (i) This license (PSSL v1.1) is included with all copies and derivative works.
- (ii) The recipient's use also constitutes Qualifying Use.
- (iii) You do not misrepresent the origin of the Licensed Software.
- (iv) You include prominent notice of any modifications You have made.
(e) Deploy the Licensed Software on an unlimited number of devices and servers within a Qualifying Use deployment at no charge.
3. Commercial License Requirement — Non-Qualifying Use
3.1 Any use of the Licensed Software that does NOT meet the definition of Qualifying Use (Section 1.7) requires a separate commercial license from Anka Labs, Inc.
3.2 The Packet Rule. The determining factor for whether a deployment requires a commercial license is the origin of data consumed by the Licensed Software — not the mere presence of non-Sandstar devices in the same building or facility. Specifically:
- (a) Non-Sandstar devices (BACnet chillers, Modbus meters, legacy controllers, etc.) may coexist in the same building as Sandstar controllers without triggering a commercial license requirement — provided that data from those non-Sandstar devices does not flow into the Licensed Software.
- (b) However, if any Non-Sandstar Data reaches the Licensed Software — whether directly, through a gateway, through a Haystack server that aggregated the data, or through any other intermediary — the use of the Licensed Software becomes Non-Qualifying Use, and a commercial license is required.
- (c) The test is applied at the data consumption layer: if the Licensed Software renders, displays, browses, or acts upon a data packet, that packet must trace its origin to a Sandstar hardware-agnostic controller.
3.3 No Unified View Without Full Sandstar Ecosystem. The Licensed Software may not be used as a single-pane-of-glass interface that unifies data from both Sandstar and non-Sandstar systems without a commercial license.
3.4 For clarity, the following scenarios require a commercial license: consuming data from BACnet, Modbus, LonWorks, KNX, or other legacy protocols in the Licensed Software; operating the Licensed Software as a unified dashboard combining Sandstar-Origin Data with Non-Sandstar Data; proxying Non-Sandstar Data through a Haystack server and then consuming it in the Licensed Software; and any deployment in which the Licensed Software does not exclusively consume Sandstar-Origin Data.
3.5 To obtain a commercial license, contact: Anka Labs, Inc. — 6800 West Gate Blvd, Suite 132-577, Austin, TX 78745, USA — Email: [email protected] — Phone: +1 (512) 540-3010
3.6 Commercial license terms, including pricing, deployment scope, support, and SLA provisions, are negotiated separately and are not governed by this document.
4. Data Origin Verification
4.1 The Licensor may, at its sole discretion, define technical mechanisms within the Licensed Software or the Project Sandstar engine to verify the origin of data packets consumed by the Licensed Software. Such mechanisms may include, but are not limited to:
- (a) Origin tagging at the Sandstar engine level.
- (b) Cryptographic signing of data packets by the Sandstar engine.
- (c) Verification queries against the source controller's Haystack REST API to confirm it is running the Sandstar engine.
4.2 Licensees shall not circumvent, disable, modify, or bypass any data origin verification mechanism implemented in the Licensed Software or the Project Sandstar engine. Circumvention of such mechanisms constitutes a material breach of this license.
4.3 In the absence of technical verification mechanisms, Licensees are responsible for ensuring that their deployment meets Qualifying Use conditions through architectural controls, configuration, and operational procedures.
5. Modification and Enhancement Rights
5.1 Licensees operating under Qualifying Use may freely modify, extend, enhance, and customize the Licensed Software without restriction on the nature of their modifications, provided the resulting deployment continues to meet Qualifying Use conditions.
5.2 There is no obligation to contribute modifications back to the Licensor or to the Project Sandstar community. Contributions are welcome but voluntary.
5.3 If a modification causes the Licensed Software to consume Non-Sandstar Data, the deployment immediately becomes Non-Qualifying Use and is subject to the Commercial License Requirement (Section 3).
5.4 Modifications must not remove, alter, or obscure this license, any copyright notices, or any attribution to the Licensor.
6. No Time-Based Conversion
6.1 This license does NOT include any provision for automatic conversion to a permissive open-source license (such as MIT, Apache 2.0, or similar) after any period of time.
6.2 The Qualifying Use condition applies permanently to every version of the Licensed Software released under this license, without exception.
6.3 The Licensor reserves the right to release future versions under different license terms at its sole discretion, but such changes will not retroactively alter the terms of previously released versions.
7. Attribution and Notices
7.1 All copies of the Licensed Software, whether original or modified, must include:
- (a) This license in its entirety.
- (b) The following copyright notice: "Copyright (c) 2026 Anka Labs, Inc. Licensed under the Project Sandstar Source-Available License (PSSL v1.1)."
- (c) The following acknowledgment: "Project Sandstar integrates the Sedona Framework and Project Haystack, which are independent open-source projects."
7.2 You may not use the names "Anka Labs," "Project Sandstar," "Mobilytik," "Visualytik," "Ankalytik," or related trademarks to endorse or promote derivative works without prior written permission from the Licensor.
8. Intellectual Property
8.1 The Licensor retains all right, title, and interest in and to the Licensed Software, including all intellectual property rights.
8.2 This license does not grant any rights to patents, trademarks, trade secrets, or other intellectual property of the Licensor except the limited rights expressly stated herein.
8.3 If You create modifications or derivative works, You own the intellectual property in Your original contributions, but the underlying Licensed Software remains the property of the Licensor.
9. Compliance and Enforcement
9.1 Self-Assessment. Licensees are responsible for determining whether their deployment constitutes Qualifying Use or requires a commercial license.
9.2 Audit Right. The Licensor reserves the right, upon reasonable notice, to verify that deployments using the Licensed Software comply with the terms of this license.
9.3 Cure Period. If the Licensor determines that a deployment is in violation of this license, the Licensee will be notified in writing and granted a period of sixty (60) days to either:
- (a) Reconfigure the deployment so that the Licensed Software exclusively consumes Sandstar-Origin Data (Qualifying Use);
- (b) Enter into a commercial license agreement with the Licensor; or
- (c) Cease all use of the Licensed Software.
9.4 Failure to cure within the 60-day period constitutes copyright infringement and the Licensor may pursue all remedies available under applicable law.
10. Disclaimer of Warranty
THE LICENSED SOFTWARE IS PROVIDED "AS IS," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
11. Limitation of Liability
IN NO EVENT SHALL THE LICENSOR'S TOTAL LIABILITY UNDER THIS LICENSE EXCEED THE AMOUNT OF LICENSE FEES ACTUALLY PAID BY THE LICENSEE TO THE LICENSOR IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM. FOR QUALIFYING USE DEPLOYMENTS WHERE NO FEES HAVE BEEN PAID, THE LICENSOR'S LIABILITY SHALL NOT EXCEED ZERO DOLLARS ($0).
12. Termination
12.1 This license is effective until terminated.
12.2 Your rights under this license terminate automatically if You fail to comply with any of its terms and do not cure the non-compliance within the period specified in Section 9.3.
12.3 Upon termination, You must cease all use and distribution of the Licensed Software and destroy all copies in Your possession or control.
12.4 Sections 7 (Attribution), 8 (Intellectual Property), 10 (Disclaimer), 11 (Limitation of Liability), and 13 (General) survive termination.
13. General Provisions
13.1 Governing Law. This license is governed by the laws of the State of Texas, United States of America.
13.2 Dispute Resolution. Any dispute arising under this license shall be subject to the exclusive jurisdiction of the state and federal courts located in Travis County, Texas.
13.3 Severability. If any provision is held unenforceable, the remaining provisions continue in full force.
13.4 Entire Agreement. This license constitutes the entire agreement with respect to the Licensed Software.
13.5 No Waiver. Failure to enforce any provision does not constitute a waiver.
13.6 Assignment. You may not assign or transfer this license without prior written consent.
Copyright (c) 2026 Anka Labs, Inc. Licensed under the Project Sandstar Source-Available License (PSSL v1.1).
常见问题
关于PSSL v1.1的最常见问题的快速答案。
这是开源许可证吗？
不是。这是一个源代码可用许可证。代码是可见和可修改的，但商业使用取决于许可软件消费的数据源。它不符合开源倡议（OSI）对开源的定义。
什么被视为"Sandstar源数据"？
来自运行Project Sandstar引擎的设备的数据，既包括用于控制编程的Sedona Framework（SVM），也包括用于数据建模的Project Haystack。生成读数的物理设备本身必须运行Sandstar——它由源头决定，而不是由格式或传输决定。
我可以在也有BACnet控制器的建筑中使用这些应用吗？
可以，只要BACnet数据不流入许可软件即可。物理共存没有问题——两个系统可以在同一建筑、同一网络中共存。在应用内混合数据才会触发商业许可证要求。
如果我通过网关将BACnet数据重新标记为Haystack怎么办？
那仍然是非Sandstar数据。许可证查看的是源头，而不是格式。通过网关重新标记、包装或转换数据不会转换其源头——如果它不是来自运行Sandstar的设备，它将落在符合条件的使用范围之外。
我需要许可证来研究或修改源代码吗？
不需要。在符合条件的使用下，研究、检查和修改是免费的权利。您可以自由构建、测试、派生和实验——许可证仅在部署时查看什么数据流经应用。
这个许可证会转换为MIT或Apache 2.0吗？
不会。符合条件的使用条件是永久的。没有基于时间的自动转换条款（与BSL或类似源代码可用许可证不同）。PSSL旨在无限期保护Sandstar生态系统。
如果我不符合条件怎么办？
您将获得60天的书面通知，选择以下三条路径之一：（a）重新配置您的部署以满足符合条件的使用、（b）购买商业许可证或（c）停止使用这些应用。我们旨在合作解决，而不是诉讼。
我可以分发应用的修改版本吗？
可以，前提是收件人也遵守符合条件的使用，您包括原始许可证文本和署名通知。允许重新分发——符合条件的使用条件仅与代码一起传输。
我如何验证我的部署是否符合规定？
被许可人负责自我评估。在不确定的情况下，在部署前联系Anka Labs。许可人还可以部署技术机制——源头标记、密码签名或证明——来验证应用消费的数据源。
商业许可证涵盖什么？
商业许可证条款——定价、部署范围、支持、服务级别协议和服务级别——单独协商，不受PSSL本身管制。条款根据部署规模和支持需求进行调整。详情请联系[email protected]。
需要商业许可证？
如果您的部署涉及非Sandstar数据，让我们谈一下。商业条款可根据您的范围、部署规模和支持需求进行定制。
Suite 300
Coral Springs, Florida 33065