TDS on Foreign Cloud Hosting Charges

Cloud infrastructure as a service, not a licensed product

Payments to major cloud infrastructure providers — for compute instances, storage, networking, and managed database services — are generally payments for access to a service running on the provider's infrastructure, not for a licence to any specific copyrighted software the customer installs or possesses. This is the same underlying principle discussed in our SaaS subscription guide: the absence of a transferred right to exploit copyright is what keeps most of these payments outside the royalty definition, and absent an Indian PE for the specific transaction, outside Section 393(2) TDS as business income of the foreign provider.

How major providers typically structure Indian billing

Large cloud providers often have an Indian billing entity or reseller arrangement for some categories of customer, particularly for GST compliance and local invoicing convenience — but the specific contracting structure matters for the TDS analysis. Where the actual contracting party is a foreign entity with no Indian PE involved in that transaction, the payment stays within the general no-PE analysis. Where the Indian entity is genuinely the contracting party (not merely a billing conduit), the payment may instead follow ordinary domestic TDS rules applicable to a resident vendor, sidestepping Section 393(2) entirely in the other direction.

Checking the actual invoicing/contracting entity for each specific cloud vendor relationship — rather than assuming a uniform answer for 'cloud hosting' generally — is the necessary first step before applying any TDS conclusion.

Bundled managed services complicate the picture

Pure infrastructure access (compute, storage) is the clearest NIL case. Where the arrangement bundles significant managed services — dedicated technical support, custom architecture consulting, or a managed database service with active operational involvement from the provider's technical team — a services component with FTS character can arise alongside the infrastructure element, potentially requiring apportionment between a NIL infrastructure-access component and a taxable services component.

Documentation even for a routine NIL cloud-hosting position

Businesses with significant recurring cloud infrastructure spend should maintain documentation of the classification rationale for their major providers — confirming the contracting entity, the absence of a proprietary licence element, and the absence of Indian PE involvement — rather than relying on an informal, undocumented assumption that 'cloud hosting is generally NIL.' This protects the position if questioned in a later assessment.