Terms of Service and Licensing Agreement
Applicable to modules, kits, services, products, and .work files within the Kitwork ecosystem.
Last updated: 05/12/2025
1. Introduction
This document outlines the Terms of Service and Licensing Agreement for Kitwork — a developer-first, lightweight ecosystem that enables building software faster using reusable modules, automation kits, service tools, and the Work Engine powered by .work files.
By using any part of Kitwork, including .work files and Work Engine features, you agree to these terms. If you act on behalf of an organization, you confirm that you are authorized to bind that organization.
Note: Some open-source repositories use their own licenses (MIT, Apache, GPL, AGPL...). See each repository’s LICENSE file for details.
2. License and Usage Rights
2.1. Open Source Modules
- Follow the license provided (MIT, Apache 2.0, GPL, or similar).
- Free to use, modify, and redistribute within that license.
- Author and license notices must remain intact when redistributing.
2.2. Commercial Products and Work Engine
Kitwork provides a non-exclusive, non-transferable license depending on the selected plan. The license covers modules, kits, .work files, and the Work Engine which interprets and executes .work files in your projects.
Single Project License
Valid for one project only.
You may:
- Create a single End Product using modules and .work files.
- Modify or extend the product for that project using Work Engine workflows.
- Receive lifetime updates for that project and Work Engine enhancements.
You may not:
- Use it in multiple projects.
- Create builders or generators for end users using .work files.
- Distribute components or .work files separately from the End Product.
- Share license access with others.
- Use in open-source projects containing paid components or workflows.
Unlimited License
Unlimited projects.
You may:
- Create unlimited End Products using modules and .work files.
- Build derivatives or workflow variations for your own projects.
- Receive lifetime updates including Work Engine improvements.
You may not:
- Build tools that allow end users to generate products using .work files.
- Distribute components or workflows outside the End Product.
- Share license access with others.
- Create competing libraries replicating Work Engine logic.
- Use in open-source projects containing paid components or workflows.
Team or Organization License
- Developer seats: Unlimited within the purchasing organization.
- Updates: Perpetual lifetime access to modules, .work files, and Work Engine.
- Usage: Allowed for employees, freelancers, and internal teams.
- Sharing: Not allowed outside the purchasing organization.
You may:
- Create unlimited End Products using modules and Work Engine workflows.
- Build derivatives for internal organizational use.
- Share access internally within your organization.
You may not:
- Build tools allowing end users to create products using .work files.
- Distribute modules, components, or workflows outside the End Product.
- Publish competing libraries replicating Work Engine functionality.
- Share license access externally.
- Use in open-source projects containing paid components or workflows.
3. Definitions
- Licensee: The individual or organization purchasing or receiving a license.
- Components: Source code, modules, assets, .work files, and documentation provided by Kitwork.
- End Product: Any product or service built using Kitwork components and workflows.
- Client: A party receiving professional services from the Licensee.
- End User: The final user of the End Product.
- Work Engine: The core system that executes workflows defined in .work files and integrates modules into predictable project behaviors.
- .work file: Declarative file describing workflows, tasks, rules, and processes which are interpreted by the Work Engine to generate project logic.
4. Examples
Allowed
- Building personal or business websites.
- Creating commercial SaaS products.
- Delivering paid client projects using modules and .work workflows.
- Learning, research, and technical blogging.
- Building self-hosted apps for end users with Work Engine integration.
Not Allowed
- Publishing repositories that contain paid components or .work files.
- Creating competing UI or module libraries using Kitwork code or workflows.
- Porting components or .work files to another framework and redistributing.
- Building website or app builders for end users using Work Engine.
- Distributing templates or themes derived from paid components or workflows.
- Releasing End Products as open source if they include paid components or workflows.
- Any distribution method enabling third-party access without a license.
5. Intellectual Property
All original content, modules, .work files, and tools created by Kitwork are owned by the author and protected under copyright, trademark, and applicable IP laws.
6. Liability
Kitwork’s total liability for any damages arising from use of its products, modules, .work files, or Work Engine is limited to the amount paid for the license. Kitwork is not responsible for indirect or consequential damages.
7. Refund Policy
Commercial products include a 14-day refund guarantee with no explanation required. Contact the official support email for assistance.
8. Governing Law
This agreement is governed by the laws of Vietnam unless otherwise specified for a particular product. Disputes will be resolved in competent courts within Vietnam.
9. Changes to Terms
Kitwork may update these terms at any time to reflect platform improvements. Major changes will be announced on this page. Continued use after updates constitutes acceptance of the revised terms.
10. Contact
For questions, support, or partnership inquiries, reach out to Kitwork through the following channels:
- GitHub repository: kitwork
- Founder and lead developer: huynhnhanquoc
- Website: kitwork.io