distribution-terms
Can you use the Raspberry Pi 4 in your own product?
<p>Suppose I decided to create a product that used the Pi 4B as it's main processing unit. Then I made a business out of that product and had a million-dollar-company. Would the Raspberry Pi foundation sue me? Is it legal to use these computers in my own product that I'm selling? I know it's a bit more complicated than that. Suppose I was using (Linux based) Raspbian Buster, and I wrote my code in node js. No modules, APIs, anything but node. Then I used my own hardware, attached it to that, and there was my product. Would it be legal to sell? I'm no expert at law, so I'm asking this question it here. Thanks in advance!</p>

<p><strong>Yes.</strong> This is a frequently asked question on the foundation's homepage, and answered without ambiguity (<a href="https://www.raspberrypi.org/documentation/faqs/#commercial-integrate" rel="nofollow noreferrer">source</a>):</p>
<blockquote>
<p><em>Can I use a Raspberry Pi in a commercial product?</em></p>
<p>This is a very common question, and the answer is yes!
Once you have bought a Raspberry Pi, it's yours to do with as you wish.</p>
</blockquote>
<p>You would be in good company too, as in fact the Raspberry Pi is regularly used and sold for commercial applications third parties.</p>
<p>Note that this the default consequence of a contract of sale in all jurisdiction I know of (but I am not a lawyer): The seller does not retain property rights in the particular item, and by the mere selling of the item implies there are no other rights that might prevent the buyer from using it as they wish.</p>
<hr />
<p>Apart from the particular computer now in your property, there are <strong>other legal requirements:</strong></p>
<ul>
<li><strong>&quot;Copyleft&quot; softweare:</strong> Large parts of the Raspbian software are licensed under &quot;copyleft&quot; licenses (importantly, versions of the General Public License, GPL). These licenses are meant to provide your customers with the means of reproduciing and building upon the &quot;copylefted&quot; software. You will need to provide your customers with the source code to those software items, the tools and documentation needed for building, and a written notice.</li>
</ul>
<p>Your own programs need not be licensed under a &quot;copyleft&quot; license, provided that you don't build on (distribute &quot;derative works&quot; of) &quot;copyleft&quot; software.</p>
<p>The open source licenses involved are not meant to exclude commercial use, and there are helpful compliance guides available
(
<a href="https://www.linuxfoundation.org/open-source-management/2017/05/practical-gpl-compliance/" rel="nofollow noreferrer">a</a>,
<a href="https://www.softwarefreedom.org/resources/2008/compliance-guide.html" rel="nofollow noreferrer">b</a>
).</p>
<ul>
<li><p><strong>Non-free software:</strong> Make sure to not include non-free software, like <a href="https://www.wolfram.com/legal/agreements/wolfram-mathematica-raspberry-pi/" rel="nofollow noreferrer">Mathematica</a> or Oracle Java, which are not licensed for commercial redistribution.</p>
</li>
<li><p><strong>Trademarks:</strong> Your use of the words &quot;Raspberry PI&quot; or the raspberry logo is subject to <a href="https://www.raspberrypi.org/trademark-rules/" rel="nofollow noreferrer">restrictions</a>, as is usual with trademarks.</p>
</li>
<li><p><strong>Speaking of the logos:</strong> You can <a href="https://www.raspberrypi.org/trademark-rules/powered-raspberry-pi/" rel="nofollow noreferrer">request permission</a> to use their &quot;powered by Raspberry Pi&quot; logo.</p>
</li>
<li><p><strong>Market regulations:</strong> You need to abide by regulations, for example safety and electromagnetic interference. Repackaging the Pi might mean you'll need to <a href="https://www.raspberrypi.org/blog/raspberry-pi-integrator-programme/" rel="nofollow noreferrer">test and recertify your product</a>, I'm not an expert.</p>
</li>
<li><p><strong>Video codecs:</strong> Some Raspberry Pis (up to 3) include specialised video decoding hardware. If you want to use it with the MPEG2 codec, you'll have to <a href="https://www.raspberrypi.org/documentation/configuration/config-txt/codeclicence.md" rel="nofollow noreferrer">buy an activation key</a> for small one-time fee per device - £2.40 for MPEG2, £1.20 for VC-1; other codecs are already activated. I don't think you'll need a license even for commercial, for-sale devices, but I am not your lawyer.</p>
</li>
</ul>
<hr />
<p>Just to be clear, <strong>nothing prevents your buyers from cloning your software</strong>. (This is not a consequence of you providing the Raspbian source code - they can just clone the contents of your SD card.) While you can retain copyright in your own code, <strong>you'll probably have no <em>effective</em> means of detecting infringement.</strong> However, the physical design of the rest of your device will not be affected.</p>
<p>Your business model needs to account for this fact.</p>

<blockquote>
<p>Is it legal to use these computers in my own product that I'm selling?</p>
</blockquote>
<p>That is something you need to ascertain from the ToU of Raspberry. Generally speaking, though, your description is similar to a manufacturer who buys screws, bolts, diodes, transistors, and so forth that will form part of --or be embedded in-- his products. At the outset it seems unlikely that the T&amp;C would prohibit you from commercializing your Raspberry-based product. If anything, companies such as Microsoft are likelier [than Raspberry] to require a special license for commercial purposes.</p>
<p>You will also need to read the terms or license of node js and Raspian Buster. If any specific clauses are unclear, you can make follow-up questions.</p>
