Sunrise edits (#622)

MichaelMacaulay · benface · brandonleekramer · web-flow · commit 54f51c221339 · 2024-03-26T09:10:09.000-04:00
* Updates

* Lower-casing the hosted service

* adding video link

* Update website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx

Co-authored-by: Benoît Rouleau &lt;benoit.rouleau@icloud.com&gt;

* Update website/pages/en/sunrise.mdx

Co-authored-by: Benoît Rouleau &lt;benoit.rouleau@icloud.com&gt;

* Adding the Stripe section and Marcus's new video

* Removed some parentheses from the plan explanation

* updates to cost benefits page

* Feedback from Adam

---------

Co-authored-by: Benoît Rouleau &lt;benoit.rouleau@icloud.com&gt;
Co-authored-by: Brandon Kramer &lt;brandonleekramer@gmail.com&gt;
diff --git a/website/pages/en/billing.mdx b/website/pages/en/billing.mdx
@@ -6,9 +6,20 @@ title: Billing
 
 There are two plans to use when querying subgraphs on The Graph Network.
 
-- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling up.
+- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling their dapp.
 
-- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card (coming soon). The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card. The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+
+<VideoEmbed youtube="Nn771WagX2I" />
+
+## Query Payments with credit card
+
+- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+  1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+  2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
+  3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
+  4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details.
+- Invoices will be processed at the end of each month and require an active credit card on file for all queries beyond the free plan quota.
 
 ## Query Payments with GRT
 
@@ -20,14 +31,12 @@ Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph
 
 ### GRT on Arbitrum or Ethereum
 
-The Graph’s billing system accepts GRT from either Arbitrum or Ethereum, but users will need ETH on Arbitrum to pay for gas. While The Graph protocol started on Ethereum Mainnet, most activity, including all of the billing contracts, are on Arbitrum. Although setting up billing with GRT on Arbitrum will process more quickly, users do not need to bridge GRT to Arbitrum before setting up billing for The Graph Network.
+The Graph’s billing system accepts GRT from either Arbitrum or Ethereum, but users will need ETH on Arbitrum to pay for gas. While The Graph protocol started on Ethereum Mainnet, most activity, including all of the billing contracts, are on Arbitrum One. Although setting up billing with GRT on Arbitrum will process more quickly, users do not need to bridge GRT to Arbitrum before setting up billing for The Graph Network.
 
 > This section is written assuming you already have GRT in your wallet, and you're on Ethereum mainnet. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
 
 ### Adding GRT using a wallet
 
-<VideoEmbed youtube="4Bw2sh0FxCg" />
-
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
@@ -54,8 +63,6 @@ The Graph’s billing system accepts GRT from either Arbitrum or Ethereum, but u
 
 ### Adding GRT using a multisig wallet
 
-<VideoEmbed youtube="eCgxp1Rag_0" />
-
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas.
 3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
diff --git a/website/pages/en/cookbook/subgraph-debug-forking.mdx b/website/pages/en/cookbook/subgraph-debug-forking.mdx
@@ -44,12 +44,12 @@ export function handleUpdatedGravatar(event: UpdatedGravatar): void {
 }
 ```
 
-Oops, how unfortunate, when I deploy my perfect looking subgraph to the [Hosted Service](https://thegraph.com/hosted-service/) it fails with the _"Gravatar not found!"_ error.
+Oops, how unfortunate, when I deploy my perfect looking subgraph to the [hosted service](https://thegraph.com/hosted-service/) it fails with the _"Gravatar not found!"_ error.
 
 The usual way to attempt a fix is:
 
 1. Make a change in the mappings source, which you believe will solve the issue (while I know it won't).
-2. Re-deploy the subgraph to the [Hosted Service](https://thegraph.com/hosted-service/) (or another remote Graph node).
+2. Re-deploy the subgraph to the [hosted service](https://thegraph.com/hosted-service/) (or another remote Graph node).
 3. Wait for it to sync-up.
 4. If it breaks again go back to 1, otherwise: Hooray!
 
diff --git a/website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx b/website/pages/en/deploying/deploying-a-subgraph-to-hosted.mdx
@@ -2,19 +2,19 @@
 title: Deploying a Subgraph to the Hosted Service
 ---
 
-> If a network is not supported on the Hosted Service, you can run your own [graph-node](https://github.com/graphprotocol/graph-node) to index it.
+> If a network is not supported on the hosted service, you can run your own [graph-node](https://github.com/graphprotocol/graph-node) to index it.
 
-This page explains how to deploy a subgraph to the Hosted Service. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-cli). If you have not created a subgraph already, see [creating a subgraph](/developing/creating-a-subgraph).
+This page explains how to deploy a subgraph to the hosted service. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-cli). If you have not created a subgraph already, see [creating a subgraph](/developing/creating-a-subgraph).
 
-## Create a Hosted Service account
+## Create a hosted service account
 
-Before using the Hosted Service, create an account in our Hosted Service. You will need a [Github](https://github.com/) account for that; if you don't have one, you need to create that first. Then, navigate to the [Hosted Service](https://thegraph.com/hosted-service/), click on the _'Sign up with Github'_ button, and complete Github's authorization flow.
+Before using the hosted service, create an account in our hosted service. You will need a [Github](https://github.com/) account for that; if you don't have one, you need to create that first. Then, navigate to the [hosted service](https://thegraph.com/hosted-service/), click on the _'Sign up with Github'_ button, and complete Github's authorization flow.
 
 ## Store the Access Token
 
 After creating an account, navigate to your [dashboard](https://thegraph.com/hosted-service/dashboard). Copy the access token displayed on the dashboard and run `graph auth --product hosted-service <ACCESS_TOKEN>`. This will store the access token on your computer. You only need to do this once, or if you ever regenerate the access token.
 
-## Create a Subgraph on the Hosted Service
+## Create a Subgraph on the hosted service
 
 Before deploying the subgraph, you need to create it in The Graph Explorer. Go to the [dashboard](https://thegraph.com/hosted-service/dashboard) and click on the _'Add Subgraph'_ button and fill in the information below as appropriate:
 
@@ -34,7 +34,7 @@ Before deploying the subgraph, you need to create it in The Graph Explorer. Go t
 
 After saving the new subgraph, you are shown a screen with help on how to install the Graph CLI, how to generate the scaffolding for a new subgraph, and how to deploy your subgraph. The first two steps were covered in the [Defining a Subgraph section](/developing/defining-a-subgraph).
 
-## Deploy a Subgraph on the Hosted Service
+## Deploy a Subgraph on the hosted service
 
 Deploying your subgraph will upload the subgraph files that you've built with `yarn build` to IPFS and tell the Graph Explorer to start indexing your subgraph using these files.
 
@@ -243,7 +243,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
 
-Graph Node exposes a graphql endpoint which you can query to check the status of your subgraph. On the Hosted Service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+Graph Node exposes a graphql endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 
 ```graphql
 {
@@ -274,13 +274,13 @@ This will give you the `chainHeadBlock` which you can compare with the `latestBl
 
 ## Hosted service subgraph archive policy
 
-The Hosted Service is a free Graph Node Indexer. Developers can deploy subgraphs indexing a range of networks, which will be indexed, and made available to query via graphQL.
+The hosted service is a free Graph Node Indexer. Developers can deploy subgraphs indexing a range of networks, which will be indexed, and made available to query via graphQL.
 
-To improve the performance of the service for active subgraphs, the Hosted Service will archive subgraphs that are inactive.
+To improve the performance of the service for active subgraphs, the hosted service will archive subgraphs that are inactive.
 
-**A subgraph is defined as "inactive" if it was deployed to the Hosted Service more than 45 days ago, and if it has received 0 queries in the last 45 days.**
+**A subgraph is defined as "inactive" if it was deployed to the hosted service more than 45 days ago, and if it has received 0 queries in the last 45 days.**
 
-Developers will be notified by email if one of their subgraphs has been marked as inactive 7 days before it is removed. If they wish to "activate" their subgraph, they can do so by making a query in their subgraph's Hosted Service graphQL playground. Developers can always redeploy an archived subgraph if it is required again.
+Developers will be notified by email if one of their subgraphs has been marked as inactive 7 days before it is removed. If they wish to "activate" their subgraph, they can do so by making a query in their subgraph's hosted service graphQL playground. Developers can always redeploy an archived subgraph if it is required again.
 
 ## Subgraph Studio subgraph archive policy
 
diff --git a/website/pages/en/deploying/subgraph-studio.mdx b/website/pages/en/deploying/subgraph-studio.mdx
@@ -36,7 +36,7 @@ Querying subgraphs generates query fees, used to reward [Indexers](/network/inde
 
 ## Subgraph Compatibility with The Graph Network
 
-The Graph Network is not yet able to support all of the data-sources & features available on the Hosted Service. In order to be supported by Indexers on the network, subgraphs must:
+The Graph Network is not yet able to support all of the data-sources & features available on the hosted service. In order to be supported by Indexers on the network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
 - Must not use any of the following features:
diff --git a/website/pages/en/network/benefits.mdx b/website/pages/en/network/benefits.mdx
@@ -11,7 +11,7 @@ Here is an analysis:
 
 ## Why You Should Use The Graph Network
 
-- 60-98% lower monthly cost
+- Significantly lower monthly costs
 - $0 infrastructure setup costs
 - Superior uptime
 - Access to hundreds of independent Indexers around the world
@@ -21,67 +21,65 @@ Here is an analysis:
 
 ### Lower & more Flexible Cost Structure
 
-No contracts. No monthly fees. Only pay for the queries you use—with an average cost-per-query of $0.00003. Queries are priced in USD and paid in GRT.
+No contracts. No monthly fees. Only pay for the queries you use—with an average cost-per-query of $40 per million queries (~$0.00004 per query). Queries are priced in USD and paid in GRT or credit card.
 
-Query costs may vary; the quoted cost is the average at time of publication (February 2024).
+Query costs may vary; the quoted cost is the average at time of publication (March 2024).
 
-## Low Volume User (less than 30,000 queries per month)
+## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | Graph Network |
+| Cost Comparison | Self Hosted | The Graph Network |
 | :-: | :-: | :-: |
 | Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | ~$15 per month |
+| Query costs | $0+ | $0 per month |
 | Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 30,000 (autoscaling) |
-| Cost per query | $0 | $0.0005<sup>‡</sup> |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
 | Infrastructure | Centralized | Decentralized |
 | Geographic redundancy | $750+ per additional node | Included |
 | Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | ~$15 |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
-## Medium Volume User (3,000,000+ queries per month)
+## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | Graph Network |
+| Cost Comparison | Self Hosted | The Graph Network |
 | :-: | :-: | :-: |
 | Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $750 per month |
+| Query costs | $500 per month | $120 per month |
 | Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 3,000,000+ |
-| Cost per query | $0 | $0.00025<sup>‡</sup> |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
 | Infrastructure | Centralized | Decentralized |
 | Engineering expense | $200 per hour | Included |
 | Geographic redundancy | $1,200 in total costs per additional node | Included |
 | Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $750 |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
-## High Volume User (30,000,000+ queries per month)
+## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | Graph Network |
+| Cost Comparison | Self Hosted | The Graph Network |
 | :-: | :-: | :-: |
 | Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $4,500 per month |
+| Query costs | $4000 | $1,200 per month |
 | Number of nodes needed | 10 | Not applicable |
 | Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 30,000,000+ |
-| Cost per query | $0 | $0.00015<sup>‡</sup> |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
 | Infrastructure | Centralized | Decentralized |
 | Geographic redundancy | $1,200 in total costs per additional node | Included |
 | Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $4,500 |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
 <sup>†</sup>Engineering time based on $200 per hour assumption
 
-<sup>‡</sup>using the max query budget function in the budget billing tab, while maintaining high quality of service
+<sup>‡</sup>Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries.
 
-Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks.
+Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet.
 
 Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process).
 
-Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing.
 
-Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet.
 
 ## No Setup Costs & Greater Operational Efficiency
 
diff --git a/website/pages/en/sunrise.mdx b/website/pages/en/sunrise.mdx
