> For the complete documentation index, see [llms.txt](https://docs.hashsphere.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashsphere.com/managed-service/provisioning-overview.md). # Provisioning Overview Provisioning a HashSphere is a shared process between your team and the HashSphere team. This page lists the minimum inputs needed to deploy an environment. Before deployment begins, we work with you to understand a small set of foundational requirements. These inputs are critical because they determine: * Infrastructure placement and compliance alignment * Data residency and regulatory posture * Access control and identity integration * Core network identifiers used across integrations These inputs allow the HashSphere team to design and deploy your environment in alignment with your organization’s infrastructure, security, and compliance requirements. The sections below outline the primary topics discussed during provisioning. ### Cloud provider and region selection HashSpheres can be deployed on AWS or GCP. HashSphere endpoints are exposed using: * Virtual Private Cloud Endpoints (AWS) * Private Service Connect (GCP) For this reason, the cloud provider selected for the HashSphere must align with the cloud provider hosting the services that will interact with it. This ensures secure, private connectivity without requiring public internet exposure. HashSpheres can be deployed to any supported region. Region selection is typically influenced by your existing infrastructure footprint, security policies, latency considerations, and data residency requirements. The HashSphere team will work with you to determine the optimal deployment pattern based on your technical and regulatory requirements. ### Data residency Prior to provisioning, we clarify any data residency constraints that apply to your organization. These may include requirements for data to live within a single region, jurisdictional restrictions, or your internal governance policies. Understanding these requirements ensures HashSphere components are deployed appropriately. It also ensures [backup storage](/operations/network-backup-and-restore.md) aligns with your constraints. ### Identity and access integration The HashSphere Console integrates with your enterprise identity provider to enable secure, role-based access. Prior to HashSphere provisioning, we confirm your identity provider (e.g., Okta, Ping), SSO integration requirements, and access model. This allows your teams to monitor the network using your existing enterprise authentication framework without introducing separate credential systems. ### Currency identifiers Each HashSphere network requires core identifiers that are referenced by wallets, custody providers, explorers, SDKs, and partner integrations. We will confirm the following: * HashSphere currency name * HashSphere ticker symbol Defining these identifiers upfront ensures consistent ecosystem representation and prevents downstream integration issues once your applications and partners are connected. ### Admin key management Each HashSphere includes an administrative key used for foundational network operations such as: * Creating initial accounts * Funding accounts for development * Supporting early integration and onboarding Prior to provisioning, we identify the designated recipient for this key and a secure method of key delivery. Designating a responsible recipient ensures secure handling and minimizes operational risk. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.hashsphere.com/managed-service/provisioning-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.