What is Provisioning?

Provisioning is the process of creating and configuring resources, like user accounts, so they are operational. To save time and guarantee that everything goes smoothly, this process is now primarily automated.

Example: When you sign up for a cloud storage provider, provisioning automatically creates your account, allocates storage space, and grants you access to tools.

What is Provisioning in Upmind?

Provisioning is an automated procedure in Upmind that connects and controls third-party products and services you sell through their APIs (an interface that Upmind can communicate with).

This enables organisations to easily and automatically manage external systems, such as web hosting, software licenses, and domain registration, in response to Upmind events like customer orders, renewals, cancellations, or payments.

Example: When a customer purchases a hosting plan from you, Upmind immediately installs software, sets up security, configures a server, and links the service to the customer's account. It also integrates with billing, invoicing, support, and monitoring systems, making it simple to manage services from start to finish.

Provisioning also lets your clients and staff manage third-party services directly from their Upmind dashboard. This can range from simple actions like Single Sign-On (SSO) to full-featured interfaces, giving them on-demand control whenever needed.

Key Terms of Provisioning

Provisioning in Upmind is simple yet offers advanced features. We will explain the key terms.

• Blueprint: A reusable template or framework that defines how a service should be provisioned. It includes step-by-step instructions for setting up resources, such as server configurations, parameters, software installations, or DNS settings. We use blueprints because they standardise the integrations.

  Example: All domain registrars share common features like registration and renewal workflows. This makes integrating multiple providers easier and more consistent, even if their systems vary.

• Provision Provider: A third-party platform or service, like cPanel, that Upmind integrates with for deploying resources. Upmind acts as the “middleman,” translating your blueprint into actions the provider understands.

  Example: If your blueprint requires a domain registration, Upmind communicates with GoDaddy’s API to reserve the domain, configure DNS, and assign it to the customer. This is an implementation of a blueprint for a specific provider.

• Provision Configuration: A unique set of settings that define how a specific service is provisioned. It specifies which blueprint to use, which provision provider to connect to, and any custom parameters needed for the service. It also includes credentials, API keys, default regions, and resource limits. We explain more in this guide.

  Example: A provision configuration for a WordPress hosting service might specify the cPanel provision provider, the WordPress blueprint, and settings for the domain name and database.

• Contract Product: Refers to how Upmind manages and interacts with the products or services you create and offer to customers. It involves setting up and storing the metadata like product details, pricing, billing cycles, support contacts, and any related configurations within the Upmind platform.

  Example: When a customer purchases a hosting package, the contact product ensures that all the necessary details, such as disk space, bandwidth, and other features, are correctly assigned and managed. It also tracks the server’s expiry date, invoices, and support tickets.

• Service Identifier (Service ID): A unique code or label that identifies a specific contract product on the provision configuration. It is used to track and manage the product or service throughout its lifecycle. There can be two contract products on the same provision configuration with the same service identifier.

  Example: A hosting plan might have the ID SVC-2024-WP-5678, which appears in invoices, support requests, and server logs.

• Deployment: The process of assigning a service on the provider's platform. It involves executing the blueprint, applying the provision configuration, and creating and upgrading the contact product or service. This can be Dynamic or Static. We explain more in this guide.

The Provisioning Flow (Example Scenario)

Here is a scenario explaining how a customer purchases a Hosting Plan with Upmind.

• Product Setup: You create a product (e.g., Hosting Plan A) in Upmind and link it to a provisioning provider (e.g., cPanel).
• Blueprint: Upmind uses a prebuilt “Hosting Plan” blueprint with instructions for a 4GB server, cPanel access, and SSL setup.
• Provision Provider: The blueprint triggers AWS (configured with your API keys) to launch a server in us-east-1.
• Provision Configuration: Default settings apply (e.g., monthly backups enabled).
• Customer Purchase: A customer orders that product from your storefront.
• Provisioning Triggered: Upmind automatically triggers provisioning using the configuration you defined.
• Provisioning Request Sent: The request is sent to the connected platform (like your server, registrar, or API provider).
• Service Created: The external platform completes the request (e.g., account created, domain registered).
• Contract Product: A product named BizHost-123 links the service to the customer’s account, tracking renewal dates.
• Service Identifier: The server is tagged SVC-2024-BH-91011.
• Deployment: Upmind deploys the server, installs cPanel, tests the site, and emails the customer their login.
• Automation: A welcome email is sent, and a support ticket is created for onboarding.
• Ongoing Sync (Optional): Some services continue to sync status (e.g., domain status updates, disk usage, license validation).

To understand how provisioning works, follow this guide.

Provisioning Lifecycle (Diagram)

Customer Order

↓

Product Linked to Provider

↓

Provision Request Sent

↓

External Platform Creates Resource

↓

Status Returned to Upmind

↓

Customer Notified & Service Active