Skip to main content

Support Zeus

Zeus is an open-source .NET framework for industrial host applications, communication channels, protocol integration, and desktop UI binding. Your support helps keep protocol modules maintained, documentation practical, issues fixed, and field-tested patterns available to other users.

Individual Sponsorship

Individual sponsorship is for developers, users, and teams that want to support ongoing open-source maintenance.

Current support options:

OptionNotes
GitHub Sponsor buttonThe repository Sponsor button links to this page
Afdianafdian.com/a/zeusnet
WeChat / AlipayScan the QR codes below
QQ groupJoin the community and contact the maintainer

Individual sponsorship does not buy a support SLA and does not reserve specific feature work. Clear reproductions, well-scoped requests, and changes that help many users will still get the most attention.

WeChat / Alipay

If you prefer domestic payment methods, expand the QR code you want to use. The QR codes stay collapsed by default so they do not interrupt the page flow.

WeChat Pay
WeChat Pay QR code
Alipay
Alipay QR code

Commercial Support

If Zeus is already used in your project, or you need clearer delivery boundaries, commercial support can be discussed separately.

Good topics for commercial support include:

  • New protocol modules or vendor-specific protocol adapters
  • Serial, TCP, PLC, and instrument field debugging
  • WinForms / WPF host application integration
  • Point maps, acquisition, alarms, and history binding design
  • Long-term maintenance, version pinning, or issue response for internal projects

Commercial support is separate from sponsorship. Commercial work can define scope, deliverables, response channels, and pricing; sponsorship simply supports open-source maintenance.

Use of Funds

Sponsorship is prioritized for:

  • Maintaining Zeus.Communications, Modbus, Mitsubishi MC, Siemens S7, Omron FINS, Omron Host Link, EtherNet/IP, and related modules
  • Adding realistic device and virtual-device integration examples
  • Improving documentation, troubleshooting guides, and NuGet release workflow
  • Expanding tests to reduce protocol and communication regressions
  • Keeping the project maintainable over time instead of only adding one-off features

Contact

When reaching out, say whether you are asking about individual sponsorship, commercial support, a protocol adapter, or project integration.