vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Pricing for IBM Blockchain Platform for IBM Cloud 

ATTENTION!! IBM Blockchain Platform SaaS Edition is being replaced by IBM Support for Hyperledger Fabric!! IBM Blockchain Platform SaaS Edition will no longer be supported after July 31, 2023. Customers have been directed to migrate their networks by July 31, 2023. After this date, IBM Blockchain Platform SaaS networks that are not migrated to IBM Support for Hyperledger Fabric will be at risk for potential security vulnerabilities. A migration tool is provided from your console, and the disruption to your network is minimal. See [Migrating to IBM Support for Hyperledger Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-support) for details.

This guide helps you understand the pricing model for IBM® Blockchain Platform for IBM Cloud, and how much you will pay when you develop and grow your blockchain network of peers, ordering nodes, and Certificate Authorities components, which are based on Hyperledger Fabric v2.2.10.



 Pricing model 

IBM Blockchain Platform introduces a new hourly pricing model that is based on virtual processor core (VPC) allocation. This simplified model is based on the amount of CPU (or VPC) that your IBM Blockchain Platform nodes are allocated on an hourly basis, at a flat rate of $0.29 USD/VPC-hour.

A VPC is a unit of measurement that is used to determine the licensing cost of IBM products. It is based on the number of virtual cores (vCPUs) that are available to the product. A vCPU is a virtual core that is assigned to a virtual machine or a physical processor core. For IBM Blockchain Platform cost estimation purposes, 1 VPC = 1 CPU = 1 vCPU = 1 Core. The term "VPC" is also used to refer to a type of infrastructure on IBM Cloud and is unrelated to this topic.

For a total cost estimate, remember that your blockchain network consists of an Kubernetes cluster on IBM Cloud that contains IBM Blockchain Platform components and uses storage of your choice. Your Kubernetes cluster on IBM Cloud and the storage that you choose incur separate charges.
Viewing your support costs 

If you have Advanced or Premium support, you can keep track of your monthly support costs from the Support costs page in the IBM Cloud® console.



  How you're charged for support 

Each [IBM Cloud support plan](https://cloud.ibm.com/docs/get-support?topic=get-support-support-plans) has a minimum monthly price for providing support for your cloud workload at the stated service level. Beyond this starting price, any additional costs for support are based on your resource usage. The higher your resource usage, the higher your total support cost. For details about your purchased support plan, contact [IBM Cloud Sales](https://www.ibm.com/cloud?contactmodule).





  Viewing support costs 

To view your support costs, you need an access policy with the Administrator role on the Billing account management service. For more information about access roles, see [IAM access](https://cloud.ibm.com/docs/account?topic=account-userroles).

In the IBM Cloud console, go to Manage > Billing and usage, and select Support costs. You can view your support plan and relevant cost details:



*  If your support costs are billed monthly, you can view your costs for the current month. These costs include the starting price for the plan and any additional costs from your resource usage. After each billing cycle, these charges are added to your monthly invoice.
*  If you have a support subscription, you can view the remaining credit in your active subscriptions and any overages for the current month. Overage is charged if you run out of credit in your active subscriptions. You can also view upcoming support subscriptions, which are subscriptions that you bought but are not yet valid.
For an overview of available Helm charts from the Kubernetes community, see the kubernetes and kubernetes-incubator repositories in the [Helm charts](https://cloud.ibm.com/kubernetes/helm) catalog.

Any costs that incur by using a third-party open source integration are not included in your monthly IBM Cloud bill.

Installing third-party open source integrations or Helm charts from the Kubernetes community might change the default cluster configuration and can bring your cluster into an unsupported state. If you run into an issue with using any of these tools, consult the Kubernetes community or the service provider directly.





 Extending Kubernetes API and software with CRDs and Operators 

You might use custom resource definitions (CRDs) to extend the Kubernetes API to create and orchestrate custom objects in your cluster. Operators combine custom resources and controllers to automate the lifecycle of app, such as installing and rolling out updates to a customized app from a catalog in your cluster.

To get started, see the Kubernetes documentation for [Custom resources](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) and [Operators](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/).
For more information, see the [pricing plan](https://cloud.ibm.com/catalog/services/hyper-protect-crypto-services). A [billing example](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-faq-pricingfaq-how-charge-hpcs) is also available for your reference.

Updated: Process of ordering smart cards and smart card readers
: To order smart cards and smart card readers, you can now email IBM at zcat@ibm.com@ibm.com and provide necessary information. For detailed steps, see [Setting up smart cards and the Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-prepare-management-utilitiesorder-smart-card-and-reader).





 25 March 2022 

Added: Hyper Protect Crypto Services expands into the Toronto region
: You can now create Hyper Protect Crypto Services instances in the Toronto (ca-tor) region where the infrastructure is based on IBM Cloud Virtual Private Cloud (VPC). For more information, see [Regions and locations](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-regions).





 22 March 2022 

General availability: Using Unified Key Orchestrator to manage and orchestrate keys in a multicloud environment
: Unified Key Orchestrator is a public cloud control plane for multicloud and hybrid cloud key orchestration. As part of the IBM Cloud® Hyper Protect Crypto Services, it provides key lifecycle management according to NIST recommendations and secure transfer of keys to internal keystores in the service instance or external keystores.

With Unified Key Orchestrator, you can connect your service instance to keystores in IBM Cloud and third-party cloud providers, back up and manage keys by using a unified system, and orchestrate keys across multiple clouds.

The following topics can help you get started with Unified Key Orchestrator:



* [Introducing Unified Key Orchestrator](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-introduce-uko)
[Plus or higher plans only](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/plus.png)



* [Phone integration](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-deploy-phone)
* [Private endpoints](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-securingsecurity-private-endpoints)
* [Search](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-add)
* [v2 Logs API](https://cloud.ibm.com/apidocs/assistant/assistant-v2listlogs)
* [Log webhook](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-webhook-log)
* [Autolearning](https://cloud.ibm.com/docs/assistant?topic=assistant-autolearn)
* [Intent conflict resolution](https://cloud.ibm.com/docs/assistant?topic=assistant-intentsintents-resolve-conflicts)



The following features are available only to users of Enterprise plans. ![Enterprise plan only](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/enterprise.png)



* [Activity tracker](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-admin-auditing)



The plan type of the service instance you are currently using is displayed in the page header. You can upgrade from one plan type to another.
Sitemap for Cloud Functions 

Find what you are looking for in the compilation of IBM Cloud® Functions topics.



 Getting started with IBM Cloud Functions 

[Getting started with IBM Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-startedgetting-started)



* [Working with actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-startedgs_actions)
* [Creating an action in the console](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-startedgs_hello_world)
* [Creating an action in the CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-startedgs_hello_world_cli)
* [What's next in Cloud Functions?](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-startedgs_next_steps)







 What is FaaS (Function-as-a-Service)? 

[What is FaaS (Function-as-a-Service)?](https://www.ibm.com/cloud/learn/faas)





 About 

[Common use cases](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-use_casesuse_cases)



* [Microservices](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-use_casesuse_cases_microservices)
* [Web apps](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-use_casesuse_cases_webapps)
* [IoT](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-use_casesuse_cases_iot)
* [Android Push Notifications (FCM)](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-fcm)
* [iOS Push Notifications (APNs)](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-apns)
* [Chrome Push Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-chrome)
* [Firefox Push Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-firefox)
* [Safari Push Notifications](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-safari)





1. Next, the bank sends a notification with payload containing attribute "notification-type":"maintenance"and "ibmenpushto": "{"tags":["AP""]]}", notification-type attributes is added so that it matches against the topic condition and ibmenpushto as the message is for targeting push customers with android and iOS devices in Asia Pacific region AP.





* Why don't I see Email or SMS notifications that I have sent after configuring Event Notifications for Email and SMS?

Email and SMS are supported only for IBM Managed Sources (IBM Cloud services). You can send a notification from API source to all other destinations, except Email and SMS.
* Where do I specify the Slack channel name in the Slack Destination configuration?

Event Notifications supports the Slack destination using Slack's “Incoming Webhook” feature. An incoming webhook is linked directly to a Slack channel. Hence, there is no need to separately specify the Slack channel.
* Is it possible to customize the message that is generated from IBM Cloud services ((IBM Cloud sources)?

You cannot customize messages that are generated from IBM Cloud services ((IBM Cloud sources).
Publish your service to the IBM Cloud catalog 

This tutorial walks you through how to publish your service to IBM Cloud®. By completing this tutorial, you submit your publishing request, respond to any review feedback, and then publish the service to the IBM Cloud catalog.

This tutorial is one of five in a series that demonstrates how to onboard and publish a service. As you complete the tutorial, adapt each step to fit your product's needs.



 Before you begin 



1. [Register your service in IBM Cloud Partner Center](https://cloud.ibm.com/docs/sell?topic=sell-svc-register).
2. [Define the product details of your service](https://cloud.ibm.com/docs/sell?topic=sell-svc-define).
3. [Onboard a broker](https://cloud.ibm.com/docs/sell?topic=sell-broker-onboard).
4. [Add a pricing plan for your service](https://cloud.ibm.com/docs/sell?topic=sell-svc-pricing).







 Step 1: Submit your publishing request 

The details of any third-party service must be reviewed by IBM Cloud before it can be published to the catalog. Complete the following steps to submit a request to publish your service:



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My Products.
2. Select your product.
3. From the Onboarding checklist, click Request Approval.
4. Click Request Approval.



At this point, your publishing request is reviewed by IBM Cloud to ensure the required details, such as the product name, catalog entry, product page, pricing model, and support experience are complete and accurate. When your request is approved, you receive an email notifying you that you can publish your product to the catalog.
In part 1 of this tutorial series, you used [Webhook.site](https://webhook.site) to test your notifications workflow for the first time. Now that you've set up a Cloud Functions action, you can also use it to receive any incoming notifications.



1. From the Cloud Functions action menu, click Endpoints.
2. Select Enable as Web Action.
3. Select Raw HTTP handling.
4. Click Save.
5. Copy the URL. This URL will be your new webhook URL that you can add as an Event Notifications destination in the next step.









 Step 2: Update your Event Notifications settings 

Next, update your Event Notifications settings so that the service can begin to forward any incoming events from Secrets Manager to your new Cloud Functions action.



 Add your new webhook URL as a destination 

Start by adding your Cloud Functions webhook URL as a new Event Notifications destination.



1. In the console, click the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/icons/icon_hamburger.svg)> Resource list.
2. From the list of resources, select your Event Notifications instance.
3. In the Event Notifications UI, go to Destinations.
4. [Create a destination](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-create-en-destination) so that your alerts can be forwarded to the Cloud Functions webhook that you created the previous step.



1. From the navigation, click Destinations > Add.
2. Provide a name for your destination. For example, GitHub.
3. Select Webhook as the destination type.
4. Paste the URL that you copied from the Cloud Functions UI.
5. From the list of HTTP verbs, select POST.
* A Google account to log in to Firebase console to get your project_id, private_key, and client_email.
* An IBM Cloud account. If you do not have one, [create an IBM Cloud account](https://cloud.ibm.com/).



The instructions used in this document uses FCM's HTTP v1 API. The HTTP v1 API has advantages such as secure access tokens, efficient customizations, and future proof as well as more extendable client platform versions. For more information on migrating from FCM legacy HTTP API to the HTTP v1 API, see [Migrating FCM legacy HTTP API to HTTP v1 API](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-push-fcmen-fcm-http-migration).





 Step 1: Create an Event Notifications service instance 



* Log in to your [IBM Cloud account](https://cloud.ibm.com/).
* In the [IBM Cloud catalog](https://cloud.ibm.com/catalogservices), search and select Event Notifications > Event Notifications.
* Select a Region from the list of supported regions and select a pricing plan.
* Provide a Service name.
* Select a resource group.
* Accept the licensing agreements and terms by clicking the checkbox.
* Click Create.







 Step 2: Get FCM credentials 

Firebase Cloud Messaging (FCM) is the gateway that delivers push notifications to Android devices. To set up the Android Push destination on the console, you must get your FCM credentials project_id, private_key, and client_email.



* Go to the [Firebase Console](https://console.firebase.google.com/?pli=1). A Google user account is required.
* Click Create a project. If you are already having a project, then click Add Project.
* In the Create a project window, enter a project name, and accept the terms and enable or disable Google analytics (optional) by selecting the toggle switch and click Continue.
Add an IBM Cloud source 





 Step 1: Verify the IBM Cloud service 

Verify that the IBM Cloud service is available as a source for Event Notifications.



* Go to the Sources section of the Event Notifications dashboard.
* Click Add and select IBM Cloud source.
* Confirm that the managed service of interest is shown.







 Step 2: Create a service authorization 

Create a service-to-service authorization between your IBM Cloud service and Event Notifications.



* From the IBM Cloud console, select Manage >> Access(IAM) >> Authorizations.
* The Authorizations view contains drop-down list for Source service and Target service. Select your IBM Cloud service as the source, and Event Notifications as the target.
* Set the service access level to Event Source Manager.







 Step 3: Find your instance of the IBM Cloud service 



* Find your existing service instances in your [account resource list](https://cloud.ibm.com/resources).
* Select the instance of interest and open its dashboard.



If you don't have an existing instance, create one from the [IBM Cloud catalog](https://cloud.ibm.com/catalog).





 Step 4: Configure your IBM Cloud service instance to connect to Event Notifications 

Follow the documentation for the selected service to configure the connection to Event Notifications.





 Add a generic API source 

API Sources cannot be used to send notifications to out of the box destinations like email and SMS.



* Go to the Sources section of the Event Notifications dashboard.
* Click Add and select API Source.
* Type a name and an optional description and click Add.
* Because you are connecting from your own application or service, follow the instructions in the [Event Notifications API documentation](https://cloud.ibm.com/apidocs/event-notifications/event-notifications?code=node), or in the SDK documentation for your programming language to configure the connection.
SDK for Node.js 

IBM® Cloud Foundry is deprecated and no longer supported as of 1 June 2023. For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

The Node.js runtime on IBM Cloud® is powered by the sdk-for-nodejs buildpack. The sdk-for-nodejs buildpack provides a complete runtime environment for Node.js apps.

The sdk-for-nodejs buildpack is used when the app contains a package.json file in the root directory.

The app must listen on the port that is assigned to it through the PORT environment variable.

var port = (process.env.PORT || 3000);



  Starter app 

IBM Cloud provides a Node.js starter apps. The Node.js starter app is a simple Node.js app that provides a template that you can use for your app. You can experiment with the starter app, and make and push changes to the IBM Cloud environment.





  App Management (deprecated) 

Deprecation Note: As of version 4.0, the SDK for Node.js buildpack no longer supports App Management.

IBM Cloud provides a number of utilities for managing and debugging your Node.js app. See [App Management](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) for complete details.
The subscription is divided into two terms that each contain $12,000 of credit, with one term valid from 1 July 2019 through 30 June 2020, and the next term valid from 1 July 2020 through 30 June 2021. You can use the $12,000 credit of the first term at any time during its one-year period, whether it's $6,500 the first month and $500 a month afterward or $1,000 each month. If you spend $13,000 during that time period and don't have any other active subscriptions, the extra $1,000 is billed as overage.

If you have multiple subscriptions in your account that are valid at the same time, credit is spent from the individual subscription terms according to which one expires the soonest. Adding to the previous example, you might buy a new one-year subscription, 00432100, for $750 a month that starts 1 September 2019. As users in your account use resources, credit is deducted from the first term of your existing subscription, 01234567, because it expires first. When all its credit is spent, credit is then deducted from subscription 00432100 while it's valid.



Table 1. Subscription credit spending order

 Subscription Credit Valid From Valid Until 

 IBM Cloud Platform - 01234567, term 1 $12,000 1 July 2019 30 June 2020 
 IBM Cloud Platform - 00432100 $9,000 1 September 2019 31 August 2020 
 IBM Cloud Platform - 01234567, term 2 $12,000 1 July 2020 30 June 2021 



Support subscriptions that you buy after 24 September 2019 can be spent as described in this section, with credit being available for the entire subscription term. For support subscriptions that were bought before this date, credit is available on a month-to-month basis. When you buy or renew a support subscription, any existing active support subscriptions are converted to the term-based model for the remainder of their term.

For example, you might have a support subscription for $200 per month with three months remaining. When you buy a new support subscription, the existing subscription is converted to a new one with $600 of credit that can be used anytime within those three months.





 Viewing subscription usage
Applicable Additional SDs for any service ordered using your IBM Cloud account are available at [https://www.ibm.com/terms/?id=i126-6605](https://www.ibm.com/terms/?id=i126-6605) . The additional SDs contain links to the applicable Data Sheet for each service.





 Exchange Rate Policy 

Effective 1 February 2023, IBM Cloud will adjust the exchange rates used to provide pricing in non-US dollar currencies on a monthly basis. Charges for cloud services are based on US dollars. Non-US dollar pricing is calculated by converting the US dollar rate by using market exchange rates published by leading financial institutions. Market exchange rates will be adjusted monthly, except as prohibited or controlled by applicable law.

IBM uses leading financial institution benchmark rates set at the end of the month to go into effect for consumption starting the first day of the next month. The corresponding invoice will be sent 30 days later. For example, IBM will set the exchange rate at the end of January effective for consumption in February. Customers will see the impact of the new rates in their March invoice.





 IBM Business Associate Addendum 

If you or your company is a covered entity as defined by the US Health Insurance Portability and Accountability Act (HIPAA) and intend to order Cloud Services that might process protected health information (PHI), you must accept the IBM® Business Associate Addendum (BAA) available at [https://www-03.ibm.com/software/sla/sladb.nsf/sla/baa?OpenDocument](https://www-03.ibm.com/software/sla/sladb.nsf/sla/baa?OpenDocument). The BAA can be digitally accepted as described in [Enabling the HIPAA Supported setting](https://cloud.ibm.com/docs/account?topic=account-enabling-hipaa).





 Legal contact information 

For subpoenas or for reporting abuse on IBM Cloud, contact the following:

IBM Cloud c/o SoftLayer Inc.
14001 North Dallas Parkway, Suite M100
Dallas, TX 75240
214.442.0600 Main