<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SaaS on OpenChain KWG</title><link>https://OpenChain-Project.github.io/OpenChain-KWG/en/tags/saas/</link><description>Recent content in SaaS on OpenChain KWG</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 10 Aug 2026 11:20:08 +0900</lastBuildDate><atom:link href="https://OpenChain-Project.github.io/OpenChain-KWG/en/tags/saas/index.xml" rel="self" type="application/rss+xml"/><item><title>Is Open Source Compliance Necessary Even When Providing a Service as SaaS?</title><link>https://OpenChain-Project.github.io/OpenChain-KWG/en/blog/2021/12/20/saas-compliance/</link><pubDate>Mon, 20 Dec 2021 00:00:00 +0000</pubDate><guid>https://OpenChain-Project.github.io/OpenChain-KWG/en/blog/2021/12/20/saas-compliance/</guid><description>&lt;p&gt;Most open source licenses place no restrictions on simply running the software, but they do require compliance with obligations such as source code disclosure and attribution when the open source is redistributed. Here, &amp;ldquo;distribution&amp;rdquo; generally means the physical delivery of software, such as selling an embedded device that carries the software or distributing a mobile app through an app market.&lt;/p&gt;
&lt;p&gt;SaaS providers do not distribute software to deliver their service, so they can be relatively free of license obligations even when they use open source. However, some open source licenses, such as AGPL, impose license obligations even when a service is provided over a network, so care is needed there.&lt;/p&gt;</description></item></channel></rss>