docs: Add copy for Cloud legal docs (meltano#7502)

docs/src/_cloud/fees.md

@@ -1,5 +1,6 @@
 ---
-title: "Cloud Fees"
+title: "Meltano Cloud Fees"
+layout: doc
 hidden: true
 ---
 <div class="notification is-info">
@@ -9,4 +10,43 @@ hidden: true
 
 ## Meltano Cloud Fees
 
-Todo
+_Last updated: April 10, 2023_
+
+Unless specified otherwise in the applicable Order Form, the following terms and fees shall apply to the Cloud Service:
+
+1. <u>Definitions</u>:
+    - Additional Runtime: Runtime exceeding the Included Runtime.
+    - Base Spend: In a Credit Purchase, the base price charged for the credits covered by the Credit Threshold.
+    - Credit Purchase: A nonrefundable upfront purchase of Credits in bulk.
+    - Credit Threshold: The minimum Credit Purchase size to receive the rates on the Service Consumption Table below.
+    - Credit: A unit consumed by Pipeline Runs across the Organization. The number of Credits consumed by a given Pipeline Run is based on its Pipeline’s Frequency and its Additional Runtime. Credits can be purchased in bulk in a Credit Purchase, or be acquired as defined in the Service Level Agreement. Credits are shared by all Projects in an Organization, and may not be redeemed for cash.
+    - Deployment: A deployment on Meltano Cloud of a specific Environment and Project Git repository branch combination.
+    - Environment: An environment defined in the Project. An Environment may have multiple Schedules and Deployments.
+    - Frequency: The number of times a Pipeline Run of a Schedule’s Pipeline is to be executed in a specific Deployment during a given period based on the Schedule’s cron schedule expression, with a maximum of one Run every 15 minutes.
+    - Frequent Run: A Pipeline Run of a Pipeline associated with a Schedule with a Frequency of 24 or more times per day.
+    - Included Runtime: Runtime of a Pipeline Run that is not charged beyond the cost of the Pipeline Run itself: 10 minutes for Infrequent Runs, 5 minutes for Frequent Runs.
+    - Incremental Spend: In a Credit Purchase, the price charged for each Credit in the next set of Credits (or portion of the next set of Credits) after surpassing the Credit Threshold.
+    - Infrequent Run: A Pipeline Run of a Pipeline associated with a Schedule with a Frequency of less than 24 times per day, or a Pipeline Run triggered externally using the Meltano Cloud command line interface (CLI) or application programming interface (API).
+    - Meltano Cloud: The Cloud Service for hosting Projects created using Meltano Core.
+    - Meltano Core: The tool for building and running Pipelines available at https://github.com/meltano/meltano.
+    - Order Form: Order Form: An ordering document or online order entered into between Customer and Meltano, or online order process completed by Customer and confirmed by Meltano, including any applicable terms, in each case specifying the Meltano Cloud service(s) to be provided.
+    - Organization: The Customer’s top-level entity on Meltano Cloud. An Organization may have multiple Projects.
+    - Pipeline Run: An execution of a Pipeline.
+    - Pipeline: A named pipeline defined in the Project, or the tasks associated with a Schedule.
+    - Project: A Git repository connected to the Organization containing a meltano.yml file and other artifacts created using Meltano Core. A Project may have multiple Pipelines, Schedules, Environments, and Deployments.
+    - Runtime: The cumulative execution time of all tasks in a Pipeline Run, from the start of the task to the end of the task, excluding platform startup and shutdown time.
+    - Schedule: A schedule defined in the Project and enabled in a specific Deployment.
+
+2. Credits are priced based on a diminishing slope: in other words, the more Pipelines you run, the cheaper the incremental cost per unique Pipeline Run. Rates will be determined by the Service Consumption Table set forth below, subject to the terms of your specific Order Form. Meltano will provide Customer with monthly usage for the current and previous months via the Meltano Cloud CLI and dashboard.
+
+3. When the Credits in Customer’s Organization are depleted, the Organization will no longer run Pipelines. When Credits are close to being depleted, Meltano Cloud will alert Customer. If Customer has a Credit Purchase that is coming to an end, Customer must contact their account representative to arrange for a new purchase on an updated Order Form, or complete a Credit Purchase through Meltano Cloud.‍
+
+4. <u>Service Consumption Table</u>:
+
+    | Unit               | Consumption            |
+    |--------------------|------------------------|
+    | Infrequent Run     | 1 Credit               |
+    | Frequent Run       | 0.5 Credits            |
+    | Additional Runtime | 0.1 Credits per minute |
+
+    Pricing of Credits is specified on Customer's Order Form. The table will be added to this page once Meltano Cloud is out of Beta.

docs/src/_cloud/index.md

@@ -1,8 +1,7 @@
 ---
 title: Meltano Cloud
-description: Information about Meltano Concepts.
+description: Information about Meltano Cloud Concepts.
 layout: doc
-hidden: true
 toc: false
 ---
 
@@ -15,6 +14,8 @@ toc: false
 
 <ul>
   {% for doc in site.cloud %}
-    <li><a href="{{ doc.url }}">{{ doc.title }}</a></li>
+    {% unless doc.hidden %}
+      <li><a href="{{ doc.url }}">{{ doc.title }}</a></li>
+    {% endunless %}
   {% endfor %}
 </ul>

docs/src/_cloud/security-policy.md

@@ -1,5 +1,6 @@
 ---
-title: "Security Policy"
+title: "Meltano Cloud Security Policy"
+layout: doc
 hidden: true
 ---
 
@@ -10,4 +11,7 @@ hidden: true
 
 ## Meltano Cloud Security Policy
 
-Todo
+Provider (Meltano) will use commercially reasonable efforts to secure the Cloud Service from unauthorized access, alteration, or use and other unlawful tampering.
+
+Provider will maintain annually updated reports or annual certifications of compliance with the following:
+- SOC2 Type I

docs/src/_cloud/sla.md

@@ -1,5 +1,6 @@
 ---
-title: "SLA"
+title: "Meltano Cloud Service Level Agreement"
+layout: doc
 hidden: true
 ---
 <div class="notification is-info">
@@ -9,4 +10,53 @@ hidden: true
 
 ## Meltano Cloud Service Level Agreement (SLA)
 
-Todo
+_Last updated: April 10, 2023_
+
+Unless specified otherwise in the applicable Order Form, the following terms and fees shall apply to the Cloud Service:
+
+1. <u>Definitions</u>:
+    - Average Run Credits: The average number of Credits consumed by the Schedule’s most recent Consecutive Successful Runs.
+    - Consecutive Successful Runs: 5 consecutive Successful Runs over at least 5 consecutive days since the last time the Pipeline’s configuration, or that of any of its tasks, was changed.
+    - Credit: A unit consumed by Pipeline Runs across the Organization. Credits can be purchased in bulk, or be acquired as defined in this agreement. Credits are shared by all Projects in an Organization, and may not be redeemed for cash.
+    - Deployment: A deployment on Meltano Cloud of a specific Environment and Project Git repository branch combination.
+    - Downtime: Time that Schedules were not running as expected. Calculated as “Missed Ticks / Monthly Ticks” during a calendar month. The inverse of Uptime.
+    - Emergency Maintenance: Downtime outside of Scheduled Downtime hours due to the application of urgent patches or fixes, or other urgent maintenance, recommended by Meltano’s vendors to be applied as soon as possible.
+    - Environment: An environment defined in the Project. An Environment may have multiple Schedules and Deployments.
+    - Meltano Cloud: The Cloud Service for hosting Projects created using Meltano Core.
+    - Meltano Core: The tool for building and running Pipelines available at https://github.com/meltano/meltano.
+    - Missed Tick: A Tick of an enabled Working Schedule that did not result in a Successful Run starting within 30 minutes or before the next Tick. If the first Run for a Tick was not a Successful Run, the system may attempt a retry Pipeline Run within 30 minutes after the Tick time, which will not consume additional Credits.
+    - Monthly Ticks: Total number of Ticks for a given Schedule during a calendar month, taking into account changes to the Schedule’s cron schedule expression during that month.
+    - Organization: The Customer’s top-level entity on Meltano Cloud. An Organization may have multiple Projects.
+    - Pipeline Run: An execution of a Pipeline.
+    - Pipeline: The tasks associated with a Schedule.
+    - Project: A Git repository connected to the Organization containing a meltano.yml file and other artifacts created using Meltano Core. A Project may have multiple Pipelines, Schedules, Environments, and Deployments.
+    - Run: A Pipeline Run triggered as a result of a Tick.
+    - Schedule: A schedule defined in the Project and enabled in a specific Deployment.
+    - Scheduled Downtime: Downtime during the hours of 6:00 p.m. to 8:00 p.m. Thursday U.S. Pacific Time.
+    - Successful Run: A Run that completed successfully, or that failed for a reason unrelated to the Meltano Cloud platform (e.g., misconfiguration or a source API issue).
+    - Tick: Each time a Run of a Schedule’s Pipeline is to be executed in a specific Deployment based on its cron schedule expression, with a maximum of one Tick (and Run) every 15 minutes.
+    - Trial Period: The period of time that Customer first has access to and uses Meltano Cloud for evaluation or trial without a paid contract in place as specified in the applicable agreement.
+    - Uptime: Time that Schedules were not as expected. Calculated as “(Monthly Ticks - Missed Ticks) / Monthly Ticks” during a past calendar month.
+    - Working Schedule: A Schedule that has had Consecutive Successful Runs.
+
+2. <u>Service Level Commitment and Credits</u>. If Uptime of a given Working Schedule falls below 99.9%, then for every Missed Tick of that Schedule, Customer’s Account shall be credited 2 times the Average Run Credits to be used by future Pipeline Runs. Credits given for Downtime may not exceed 50% of the Average Run Credits multiplied by the Schedule’s Monthly Ticks for the month in question.
+
+3. <u>Exceptions</u>. The above service level commitment and Credits do not apply to Scheduled Maintenance or circumstances where the Cloud Service is affected by operational, connectivity or other service interruptions beyond Meltano’s sole control, including without limitation:
+    - Maintenance requested by Customer or Emergency Maintenance;
+    - Outages created or experienced by vendors and infrastructure partners;
+    - The Customer’s inability to deliver required content to Meltano or its vendors in a timely manner;
+    - Interruptions due to changes requested by the Customer and agreed in advance as potentially disruptive to the Cloud Service;
+    - Events caused either directly or indirectly by acts, errors or omissions by Customer, its agents, vendors or end-users, including but not limited to negligence, willful misconduct or breach of the Agreement;
+    - Customer’s own inability to connect due to issues with their ISP, local settings or circumstances;
+    - Events arising from malicious, unlawful or terrorist acts against Customer, Meltano or their employees, contractors, vendors or property including viruses, Trojan Horses, and other malware; and
+    -Disasters and events force majeure such as natural disasters, flood, earthquake, war, tornados, extended power outages.
+
+4. <u>Exclusions</u>. The above service level commitment and Credits do not apply to any services or data that are not expressly listed in the CSA, whether implied or inferred, nor do they apply to performance issues caused by Customer's equipment or third-party equipment. The above service level commitment and Credits do not apply during a Trial Period.
+
+5. <u>Claiming Credits</u>. To receive any Credits, Customer must notify Meltano in writing within 30 days after Customer becomes eligible to receive a Credit. Failure to comply with this requirement will forfeit Client's right to receive a Credit.
+
+6. <u>Limitations</u>. The remedies provided herein for interruptions in Cloud Service shall apply only while the Customer is in good standing and not in breach of any term of the Agreement, and the Customer accounts are paid in full with no amounts past due or security deposits not fully paid.
+
+7. <u>Maintenance Announcements</u>. From time to time, Meltano will make announcements via email regarding maintenance activities (“Maintenance Announcements”) which may affect the Cloud Service, including without limitation the possibility of affecting the Uptime of the Cloud Service. Maintenance Announcements are Meltano’s sole method and requirement for communication of such activities to Customer hereunder. It is the Customer’s responsibility to subscribe to, remain aware of and adjust as necessary to the content and effect of the Maintenance Announcements.
+
+8. <u>Maintenance Activities</u>. Meltano will use reasonable commercial efforts to schedule maintenance activities that may result in likely, imminent, or limited interruptions in the Cloud Service, not less than 48 hours in advance of the beginning of that activity. Meltano may determine at its sole discretion that Emergency Maintenance is necessary to protect or preserve the integrity of its services or infrastructure, which may affect Uptime of the Cloud Service, at which time Meltano will make a Maintenance Announcement when the maintenance is performed.

docs/src/_cloud/support.md

@@ -1,5 +1,6 @@
 ---
-title: "Support"
+title: "Meltano Cloud Technical Support"
+layout: doc
 hidden: true
 ---
 
@@ -10,4 +11,5 @@ hidden: true
 
 ## Meltano Cloud Technical Support
 
-Todo
+Customers can receive professional support from the Meltano team via <https://help.meltano.com> and a dedicated private channel in the Meltano Slack community available at <https://meltano.com/slack>.
+The Meltano team strives to respond within 12 hours during weekdays, excluding United States federal holidays. In addition, customers can receive community support via public channels in the Meltano Slack community.