Choose your capacity
Start at 1 TB and select the tier that fits your current data footprint and growth plan.
Indian-region endpoints, built-in data redundancy, automatic encryption at rest, and S3-compatible API connectivity for applications, backup tools, and file-management systems. Included transfer allowances and monthly terms are confirmed in your written quote.
Built-in redundancy is designed to enhance durability and reduce the risk of data loss caused by individual storage hardware failures. Protection is managed automatically by the underlying infrastructure, requiring no additional customer configuration.
Available in Mumbai and Indore. The upstream provider documents a Tier IV Mumbai facility, a TIA-942 and ISO-certified Indore facility, and 3x replication. Availability and service-level commitments are confirmed in the applicable written order.
Infrastructure-level redundancy operates automatically to improve resilience and reduce the risk of data loss caused by individual storage hardware failures. It requires no additional customer configuration and is not a substitute for an independent backup.
Connect through an S3-compatible endpoint with common S3-compatible tools, SDKs and workflows, including HTTPS, CORS, pre-signed URLs and HTTP Range requests. Test application-specific operations and policies before production cutover because not every AWS S3 feature or policy expression is supported.
Monthly outbound transfer up to the active storage capacity is included without an excess-transfer fee. If outbound transfer reaches that limit, service may be temporarily suspended until the storage plan is upgraded or the next billing cycle begins. Common API requests are included where confirmed.
Data is automatically encrypted at rest by default as part of the storage service, with no additional customer configuration required. Data transfers can be secured through HTTPS/TLS connections.
Mumbai and Indore endpoints provide Indian-region object storage with 3x replication for redundancy and resilience. Indian-region hosting can support data-residency and data-governance requirements. Customers remain responsible for their own applicable legal, regulatory, technical and organizational compliance obligations.
Start with the service decisions that affect your deployment. Your written quote then confirms the capacity, transfer allowance and configuration for your workload.
Start at 1 TB and select the tier that fits your current data footprint and growth plan.
Tell us about backup, media, application or file-management use so we can review compatibility before provisioning.
Your quote confirms the final configuration, transfer allowance, commercial terms and any workload-specific requirements.
Capacity tiers run from a 1 TB minimum to 50 TB+. Monthly outbound transfer up to the active storage capacity is included without an excess-transfer fee; reaching the limit may temporarily suspend service until an upgrade or the next billing cycle. The current written quote confirms the final monthly HubforHost charge and configuration.
HubforHost uses an assisted provisioning process rather than requiring customers to complete the initial storage setup entirely through a self-service workflow. Customers select the storage tier, preferred region and workload requirements. We review the request, confirm the configuration and provide payment instructions. After payment confirmation, the S3-compatible storage environment is provisioned and the required access configuration is prepared. Provisioning timelines depend on the requested configuration and workload.
Select your storage tier (1 TB to 50 TB+), preferred region (Mumbai or Indore) and workload requirements.
We review the request, confirm the configuration and provide payment instructions. S3 uses assisted provisioning.
Pay via UPI, Razorpay or net banking. A credit card is not mandatory. Provisioning begins after payment confirmation.
The S3-compatible storage environment is provisioned with agreed IAM, CORS and configuration-dependent Object Lock settings.
The S3 endpoint URL, Access Key, Secret Key and connection details are securely shared with you once provisioning is complete.
Use common S3-compatible tools and workflows after validating the operations your workload requires. On-demand media storage is supported; live streaming is not. Customers remain responsible for content rights, licences and permissions.
Connect AWS CLI, Boto3, Java, Node.js, and Go clients to the supplied endpoint; validate the operations your application requires.
High-throughput cloud-to-cloud synchronization, streaming transfers, and automated cron migration scripts.
Connect from Windows, macOS, or Linux for intuitive drag-and-drop file browsing and bucket permission editing.
Veeam integration and Object Lock requirements are checked during provisioning and should be validated with a restore test before production use.
Once access details are issued, use these examples as a starting point and validate the operations your application needs before production use.
# Configure HubforHost S3 endpoint
aws configure set aws_access_key_id YOUR_ACCESS_KEY
aws configure set aws_secret_access_key YOUR_SECRET_KEY
aws configure set default.region ap-south-1
# Upload file; encryption at rest is automatic
# Endpoint URL provided during provisioning
aws s3 cp backup.tar.gz s3://my-enterprise-bucket/ \
--endpoint-url https://YOUR_S3_ENDPOINT
# List bucket contents
aws s3 ls s3://my-enterprise-bucket/ \
--endpoint-url https://YOUR_S3_ENDPOINTMumbai and Indore endpoints provide Indian Data Residency with 3x replication for redundancy and resilience. Compliance with the Digital Personal Data Protection Act, CERT-In directions, or sector-specific obligations depends on the customer's purpose, data flows, contracts, access controls, retention settings, incident procedures, and other operational controls. Customers remain responsible for their own applicable legal, regulatory, technical and organizational compliance obligations. Obtain legal and compliance advice for regulated workloads.
Clear, transparent answers on provisioning, technical compatibility, and billing.
HubforHost uses Concierge Assisted Provisioning: 01 โ Submit your requirement (storage tier, preferred region and workload). 02 โ Requirement review. 03 โ Complete payment (UPI, Razorpay, net banking; a credit card is not mandatory). 04 โ Storage provisioning. 05 โ Receive your access details (S3 endpoint URL, Access Key, Secret Key and connection details, securely shared after payment confirmation). S3 uses assisted provisioning rather than a self-service workflow. Provisioning timelines depend on the requested configuration and workload. Provisioning begins after payment confirmation.
Every subscription operates on a 30-day prepaid cycle. You may renew during the 5 days before expiry without losing the remaining paid term. HubforHost provides a 3-day post-expiry grace period; access may then be suspended, and service data may be retained for up to 60 days after expiry, subject to upstream availability. This is not a recovery guarantee, so keep an independent backup. No retention or reactivation fee applies unless it was disclosed in your accepted written order or is supported by later written terms.
An upgrade is subject to the applicable 48-hour transaction gap. Before processing it, HubforHost will provide a written quote showing the effective date, new capacity, unused-value adjustment or credit, and amount payable. A billing credit is not a cash refund. Downgrades cannot take effect in the same billing cycle and may be reviewed for the next eligible renewal only if your stored data fits the lower capacity. Unused prepaid time is non-refundable.
Monthly outbound transfer up to the active storage capacity is included without an excess-transfer fee. If outbound transfer reaches that limit, service may be temporarily suspended until the storage plan is upgraded or the next billing cycle begins. Tell us about high-transfer workloads before ordering.
The platform exposes an S3-compatible endpoint for common clients and SDKs. Compatibility is not identical to every AWS S3 feature: for example, the provider documents limitations in its supported bucket-policy language. Test required operations and policies before production cutover.
The selected storage endpoints are in Mumbai or Indore, India. The provider documents Tier IV certification for Mumbai and TIA-942 and ISO certifications for Indore. Indian hosting supports a data-residency strategy, but it does not by itself guarantee compliance for a customerโs workload.
Where Object Lock is available and correctly configured, retention controls can reduce the risk of deletion or overwrite. Availability must be confirmed during provisioning, and customers should still use independent backups, least-privilege access, credential isolation, monitoring, and regular restore tests.
Migration assistance is available. We scope the source, supported operations, data volume, validation method, and cutover plan first. The process is designed to minimize disruption, but transfer time and application availability depend on the source provider, network, and workload.
Official first-party documentation at /knowledge-base/. Start with these guides:
Cancellation prevents future renewal but does not create a pro-rata refund for unused capacity or prepaid time. Review the Refund & Cancellation Policy and export required data before cancellation or deprovisioning.
Select your required storage tier. We review the request, confirm the configuration and provide payment instructions (UPI, Razorpay, net banking โ a credit card is not mandatory). Provisioning begins after payment confirmation.