DOC-510 | ArangoGraph Packaging Changes (#1453)

* packaging changes

* remove note and fix link

* remove two more mentions of enterprise

* changed heading

Author: nerpaula

3.10/quick-start-in-the-cloud.md

@@ -138,14 +138,16 @@ Alternatively, follow the steps of the linked guides:
 - [Access your deployment](arangograph/deployments.html#how-to-access-your-deployment)
 - [Delete your deployment](arangograph/deployments.html#how-to-delete-a-deployment)
 
-## Free-to-Try vs. Professional Service
+## Free-to-Try vs. Paid
 
-The ArangoGraph Insights Platform comes with a free-to-try tier that lets you test our ArangoDB
-Cloud for free for 14 days. It includes one project and one deployment.
-After the trial period, your deployments are automatically deleted.
+The ArangoGraph Insights Platform comes with a free-to-try tier that lets you test
+the ArangoDB Cloud for free for 14 days. It includes one project and one small
+deployment of 4GB, local backups, and one notebook for learning and data science.
+After the trial period, your deployment is automatically deleted.
 
-You can convert to the professional service model at any time by adding 
+You can unlock all features in ArangoGraph at any time by adding 
 your billing details and at least one payment method. See:
+- [ArangoGraph Packages](arangograph/organizations.html#arangograph-packages)
 - [How to add billing details to organizations](arangograph/billing.html#how-to-add-billing-details)
 - [How to add a payment method to an organization](arangograph/billing.html#how-to-add-a-payment-method)
 

3.11/quick-start-in-the-cloud.md

@@ -138,14 +138,16 @@ Alternatively, follow the steps of the linked guides:
 - [Access your deployment](arangograph/deployments.html#how-to-access-your-deployment)
 - [Delete your deployment](arangograph/deployments.html#how-to-delete-a-deployment)
 
-## Free-to-Try vs. Professional Service
+## Free-to-Try vs. Paid
 
-The ArangoGraph Insights Platform comes with a free-to-try tier that lets you test our ArangoDB
-Cloud for free for 14 days. It includes one project and one deployment.
-After the trial period, your deployments are automatically deleted.
+The ArangoGraph Insights Platform comes with a free-to-try tier that lets you test
+the ArangoDB Cloud for free for 14 days. It includes one project and one small
+deployment of 4GB, local backups, and one notebook for learning and data science.
+After the trial period, your deployment is automatically deleted.
 
-You can convert to the professional service model at any time by adding 
+You can unlock all features in ArangoGraph at any time by adding 
 your billing details and at least one payment method. See:
+- [ArangoGraph Packages](arangograph/organizations.html#arangograph-packages)
 - [How to add billing details to organizations](arangograph/billing.html#how-to-add-billing-details)
 - [How to add a payment method to an organization](arangograph/billing.html#how-to-add-a-payment-method)
 

3.12/quick-start-in-the-cloud.md

@@ -138,14 +138,16 @@ Alternatively, follow the steps of the linked guides:
 - [Access your deployment](arangograph/deployments.html#how-to-access-your-deployment)
 - [Delete your deployment](arangograph/deployments.html#how-to-delete-a-deployment)
 
-## Free-to-Try vs. Professional Service
+## Free-to-Try vs. Paid
 
-The ArangoGraph Insights Platform comes with a free-to-try tier that lets you test our ArangoDB
-Cloud for free for 14 days. It includes one project and one deployment.
-After the trial period, your deployments are automatically deleted.
+The ArangoGraph Insights Platform comes with a free-to-try tier that lets you test
+the ArangoDB Cloud for free for 14 days. It includes one project and one small
+deployment of 4GB, local backups, and one notebook for learning and data science.
+After the trial period, your deployment is automatically deleted.
 
-You can convert to the professional service model at any time by adding 
+You can unlock all features in ArangoGraph at any time by adding 
 your billing details and at least one payment method. See:
+- [ArangoGraph Packages](arangograph/organizations.html#arangograph-packages)
 - [How to add billing details to organizations](arangograph/billing.html#how-to-add-billing-details)
 - [How to add a payment method to an organization](arangograph/billing.html#how-to-add-a-payment-method)
 

arangograph/backups.md

@@ -15,7 +15,7 @@ To backup data in ArangoGraph for an ArangoDB installation, navigate to the
 There are two ways to create backups. Create periodic backups using a
 **Backup policy**, or create a backup manually.
 Both ways allow you to create [backups in multiple regions](#multi-region-backups)
-as well, if your organization belongs to the Enterprise tier.
+as well.
 
 ### Periodic backups
 
@@ -34,8 +34,7 @@ These backups are not automatically uploaded. To enable this, use the
 **Upload backup to storage** option and choose a retention period that
 specifies how long backups are retained after creation. 
 
-If your organization belongs to the Enterprise tier and the
-**Upload backup to storage** option is enabled for a backup policy,
+If the **Upload backup to storage** option is enabled for a backup policy,
 you can then create backups in different regions than the default one.
 The regions where the default backup is copied are shown in the
 **Additional regions** column in the **Policies** section.
@@ -48,8 +47,7 @@ It's also possible to create a backup on demand. To do this, click **Back up now
 
 ![Back up Now Dialog](images/arangograph-back-up-now-dialog.png)
 
-If your organization belongs to the Enterprise tier and you want to manually
-copy a backup to a different region than the default
+If you want to manually copy a backup to a different region than the default
 one, first ensure that the **Upload backup to storage** option is enabled.
 Then, highlight the backup row and use the
 **Copy backup to a different region** button from the **Actions** column. 
@@ -103,13 +101,6 @@ alternatives such as having hourly backups with a retention period of a year.
 
 ## Multi-region backups
 
-{% hint 'info' %}
-The multi-region backup feature is only available for the ArangoGraph
-Enterprise tier. To upgrade to the Enterprise tier,
-[get in touch](https://www.arangodb.com/contact/){:target="_blank"}
-with the ArangoDB team.
-{% endhint %}
-
 Using the multi-region backup feature, you can store backups in multiple regions
 simultaneously either manually or automatically as part of a **Backup policy**.
 If a backup created in one region goes down, it is still available in other
@@ -145,8 +136,7 @@ During restore, the deployment is temporarily not available.
 {% hint 'info' %}
 The cloned deployment will have the exact same features as the previous
 deployment including node size, model, and cloud provider. The region
-can stay the same or you can select a different one if your organization belongs
-to the Enterprise tier.
+can stay the same or you can select a different one.
 For restoring a deployment as quick as possible, it is recommended to create a
 deployment in the same region as where the backup resides to avoid cross-region
 data transfer.

arangograph/deployments.md

@@ -30,12 +30,6 @@ its projects and deployments.
 4. Click the __New deployment__ button.
 5. Set up your deployment. The configuration options are described below.
 
-   {% hint 'info' %}
-   The configuration options depend on the tier your organization belongs to.
-   For more details about available resources and usage limits, refer to the 
-   [ArangoGraph tiers](organizations.html#arangograph-tiers) section.
-   {% endhint %}
-
 ![ArangoGraph New Deployment](images/arangograph-new-deployment1.png)
 
 {% hint 'info' %}
@@ -94,13 +88,8 @@ provider and region in the Location section.
 
 #### OneShard
 
-1. Select the memory size of your node.
-2. Select the CPU size of your node.
-3. Select the initial disk size of your node. The available ranges for the disk size
-   depend on the selected memory size.
-4. Select the upper limit for the disk size. It defaults to twice the initial
-   disk size. You can set it to the same value as the initial disk size to
-   disable automatic disk sizing.
+- Select the memory size of your node. The disk size is automatically set for you
+  based on the selected memory size.
 
 {% hint 'info' %}
 A deployment's node disk size is automatically increased by 25% when the maximal
@@ -114,16 +103,17 @@ the upper disk size limit already.
 
 #### Sharded
 
-- In addition to memory and disk size as in the OneShard configuration, select
+- In addition to the memory size as in the OneShard configuration, select
   the number of nodes for your deployment. The more nodes you have, the higher
-  the replication factor can be.
+  the replication factor can be. Same as in OneShard, the disk size is automatically
+  set for you.
 
 ![ArangoGraph Deployment Sharded](images/arangograph-new-deployment-sharded.png)
 
 #### Single Server
 
-- Like with OneShard and Sharded deployments, you choose memory and disk size.
-  However note that the sizes you choose are for the entire deployment.
+- Like with OneShard and Sharded deployments, you can choose the memory size.
+  Note, however, that the size you choose is for the entire deployment.
   For OneShard and Sharded deployments the chosen sizes are per node.
 
 ![ArangoGraph Deployment Single Server](images/arangograph-new-deployment-singleserver.png)
@@ -250,7 +240,7 @@ are using the `18529` port to avoid breaking changes.
 ## How to edit a deployment
 
 You can modify a deployment’s configuration, including the ArangoDB version
-that is being used, change the memory, CPU, and disk size, or even switch from
+that is being used, change the memory size, or even switch from
 a OneShard deployment to a Sharded one if your data set no longer fits in a
 single node. 
 
@@ -259,12 +249,6 @@ To edit an existing deployment, you must have the necessary set of permissions
 attached to your role. Read more about [roles and permissions](access-control.html#roles).
 {% endhint %}
 
-{% hint 'info' %}
-The configuration options depend on the tier your organization belongs to.
-For more details about available resources and usage limits, refer to the 
-[ArangoGraph tiers](organizations.html#arangograph-tiers) section.
-{% endhint %}
-
 1. Go to the **Projects** section and select an existing deployment from the list. 
 2. Open the deployment you want to change. 
 3. On the **Overview** tab, click the **Edit** button. 
@@ -274,28 +258,18 @@ For more details about available resources and usage limits, refer to the
    - Select a different CA certificate.
    - Add or remove an IP allowlist.
 5. In the **Configuration** section, you can do the following:
-   - Upgrade the memory size per node. 
-   - Modify the CPU per node from General to Low or vice-versa, if made available
-     by the cloud provider.
-   - Select a different disk size per node. The available ranges for the disk size
-     depend on the selected memory size. To enable automatic disk size scaling, move
-     the slider to a value higher than the current disk size.
+   - Upgrade the memory size per node. The disk size is automatically set for you.
    - Change **OneShard** deployments into **Sharded** deployments. To do so,
      click **Sharded**. In addition to the other configuration options, you can
      select the number of nodes for your deployment. This can also be modified later on.
 
    {% hint 'warning' %}
    Notice that you cannot switch from **Sharded** back to **OneShard**.
    {% endhint %}
-   
-   - AWS deployments have an additional option that allows you to select the
-     **Disk Performance** either with general settings, or optimized for large
-     and very large data sets. This option is dependent on the selected memory
-     size. For example, larger deployments have optimized settings by default.
 
    {% hint 'warning' %}
-   When upgrading the memory size, disk size, and/or disk performance in AWS deployments,
-   the value gets locked and cannot be changed until the cloud provider rate limit is reset.  
+   When upgrading the memory size in AWS deployments, the value gets locked and
+   cannot be changed until the cloud provider rate limit is reset. 
    {% endhint %}
 
 6. All changes are reflected in the **Summary** section. Review the new

arangograph/images/arangograph-billing.png

@@ -58,8 +58,8 @@ favorite GraphML libraries with GPUs.
 
 {% hint 'info' %}
 Depending on the tier your organization belongs to, different limitations apply:
-- Professional and Enterprise tiers: you can create up to three notebooks per deployment.
-- Free-to-try tier: you can only create one notebook per deployment.  
+- On-Demand and Committed: you can create up to three notebooks per deployment.
+- Free-to-try: you can only create one notebook per deployment.
 {% endhint %}
 
 ![Notebooks](images/arangograph-notebooks.png)