From 38c39fffef6279abad77abfd7ce7ff72dcef34c1 Mon Sep 17 00:00:00 2001
From: eashaw <eashaw@sailsjs.com>
Date: Tue, 2 Nov 2021 16:56:04 -0500
Subject: [PATCH] add pricing question (#2759)

---
 website/views/pages/pricing.ejs | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/website/views/pages/pricing.ejs b/website/views/pages/pricing.ejs
index 8f8df1d7cb..94aeb10e34 100644
--- a/website/views/pages/pricing.ejs
+++ b/website/views/pages/pricing.ejs
@@ -1183,6 +1183,15 @@
                 Since Fleet is self-managed, some metadata is stored wherever it is deployed (e.g. Amazon, Azure, Google, your own data center, hybrid cloud, anywhere).  That's done using a MySQL database, but the bulk of the data is not stored there — instead, it flows directly into a tool like Splunk or ElasticSearch. You can send that information to any of Fleet's supported log destinations.
               </p>
             </div>
+            <div style="border-bottom: 1px solid #E2E4EA; padding-right: 20px;" class="position-relative">
+              <p id="faq__question11" style="cursor: pointer;" class="faq-question pt-3 mb-3" data-toggle="collapse" data-target="#faq__answer11" aria-controls="faq__answer11">
+                Can I fork Fleet's source code and build upon it myself to create my own features?
+                <span style="color: #6A67FE; right: 0; top: 24px;" class="position-absolute fa fa-angle-down"></span>
+              </p>
+              <p id="faq__answer11" class="collapse" aria-labelledby="faq__question11">
+                Anyone is free to fork the project. We are always interested to hear feedback, and we are happy to take pull requests and ideas upstream any time we can.
+              </p>
+            </div>
           </div>
         </div>