Provider Agreement
Last updated: November 13, 2026 · Effective November 5, 2026
The earnings wording in the summary and in Section 4 applies from December 13, 2026.
In short: This is the agreement between you (a "Provider" who lists GPU hardware on GridShare to earn income) and GridShare, operated by Quartusbrain Ideas Private Limited. You are an independent contractor: you own your hardware, set your availability, and are paid for the time your machine is in use by Buyers. Section 3 explains pay when your machine drops a rental, and Section 7(j) explains the record the node software keeps of entry into Buyer containers. This Agreement forms part of, and is read with, our Terms of Service, Privacy Policy and Acceptable Use Policy. By registering as a Provider you accept it in full.
1. Independent-Contractor Status
Providers are independent individuals or entities, not employees, agents, or partners of GridShare. You make your own GPU hardware available to GridShare, through the GridShare node software, to help meet compute demand on the Platform. GridShare buys the compute capacity your node delivers and resells it to Buyers under its own name as principal; your commercial counterparty for that capacity is GridShare, not the Buyer. GridShare does not own the hardware and is not responsible for the acts, omissions, hardware reliability, or data-security practices of any Provider. GridShare may decline a registration, or suspend or restrict an account, where it has reasonable cause, including suspected fraud, breach of these terms, a legal or regulatory requirement, failure of identity, PAN, or payout verification, or a credible risk to the Platform or its users. It gives notice where practicable, and acts immediately and without prior notice only for serious violations.
2. Listing and Hardware
You represent and warrant that you own, or have the full legal right to share and commercialise, all hardware you list on GridShare. You are solely responsible for:
- The physical security, maintenance, and condition of your hardware
- Electricity, cooling, and all other operating costs of your node
- A stable internet connection; GridShare is not responsible for revenue you lose because of your connectivity
- Making sure your listing does not violate any third-party rights, licences, or agreements (including OEM terms)
3. Availability and Reliability
You may pause or disconnect your node at any time. If your node goes offline while a Buyer is using it, your machine health rating may be lowered, and you are not paid for time your node did not serve, as set out below.
When a rental stops because of your node:
- Node drops. If your node stops responding during a rental, GridShare refunds the Buyer for the time after the last signal it received from your node. That time was not delivered. Where GridShare’s records show that the drop was on your side (for example your machine shut down, slept or restarted, or lost power or its internet connection) while GridShare’s systems were working normally and other Providers’ nodes stayed connected, you are not paid your share of that refunded time.
- GridShare’s side, or unclear. Where the drop was caused on GridShare’s side (for example a restart, stall or outage of GridShare’s servers or connection service, a fault in GridShare’s software, a node software update that GridShare sent or released, a download that GridShare pushed to your node, a move or stop that GridShare started, or many nodes dropping at the same time), or where GridShare cannot tell whose side caused it, you are paid your normal share of that time.
- Other refunds caused on your side. Where GridShare refunds a Buyer after finding that the cause was on your side (for example someone at your machine stopped the Buyer’s workload, or your hardware did not match its listing), GridShare may withhold your share of the amount refunded.
- Limits. GridShare never withholds more than your share of what the Buyer was refunded, and only from your earnings for that rental that are not yet part of a payout. Money already paid to you is not recovered. If another Provider referred you, their referral bonus on the withheld amount is reversed too, but only from bonus not yet paid to them. Nothing else is deducted for the same refund. This is not a penalty: it reflects compute that was not delivered as agreed.
- Questions and disputes. GridShare decides reasonably and in good faith from the records it keeps. You can ask support@gridshare.in whether any of your earnings were withheld under this Section, and why. If you think a refund was not caused on your side, write to us, ideally within 30 days so the records can still be checked; a person will review it and, if GridShare agrees, add the amount to your next payout.
4. Earnings and Payouts
For every second a Buyer's workload holds your machine's GPUs, you earn 70% of your machine's listed hourly rental rate, as shown on your Provider dashboard. GridShare may change Platform fees with 30 days' prior notice.
- Payouts are made by bank transfer to the bank account registered and verified on your account. A verified bank account is required to be paid
- Payout fees, minimum thresholds, and frequency are as shown in your dashboard settings, where you also choose your payout schedule. Payouts then run automatically on that schedule; no per-payout confirmation is required from you
- GridShare does not guarantee any level of earnings. Earnings depend on Buyer demand, your node's machine health, hardware tier, and market conditions. We make no representation that your node will earn anything.
- A machine that stays online without a break for 4 days is marked Always-On and its rental rate is 10% higher; you earn 70% of that higher rate while it keeps the mark.
- GridShare may withhold a payout, pending investigation, where fraud, a Terms violation, or an unresolved Buyer dispute is suspected
Payment for delivered and held capacity: You are paid for compute time actually delivered, measured up to the last signal or checkpoint the Platform recorded from your machine. If you intentionally disconnect or end an active Buyer session, you forfeit earnings from that moment. Session failures caused by a Buyer's own code are not your fault and are not refundable to the Buyer.
GST-registered Providers. If you are registered for GST and have given us your GSTIN, the earnings shown to you include any GST due on them. For each payout you must issue GridShare a valid GST tax invoice for that amount, and the PAN, GSTIN and payout bank account on your Provider account must all be in the same name. GridShare pays your earnings, including the GST part, only against that invoice. Payouts to GST-registered Providers are made monthly. If you are not registered for GST, no GST is added to your earnings.
5. Tax Deducted at Source (TDS)
GridShare deducts tax at source (TDS) on its payments to Providers as required under the Income-tax Act, 1961. GridShare will deduct TDS at the applicable rate for your payment and tax status, deposit it with the Income Tax Department on your behalf, and make a TDS certificate (Form 16A) available. To avoid a higher rate of deduction under Section 206AA, you must furnish a valid PAN. The exact applicable section and rate are determined in accordance with the law as it applies to payments of this kind and are shown or notified through your dashboard. TDS deducted by GridShare does not discharge your full income-tax liability; you remain responsible for filing your own return.
6. Data on Provider Hardware
GridShare does not inspect or control what Buyers run on Provider hardware. It does not log it either, apart from the access record described in Section 7(j). Providers must not attempt to access, copy, intercept, or interfere with any Buyer's data or workloads. Violation will result in immediate permanent account termination and may be reported to law enforcement.
7. Provider Obligations
As a Provider, you agree that you will:
- (a) Connectivity and downtime: Use reasonable efforts to maintain node connectivity, and notify GridShare in advance of any planned downtime expected to exceed one (1) hour
- (b) No access to Buyer data: Not access, inspect, log, copy, or persist any Buyer data, files, environment variables, SSH keys, or execution logs, whether during or after a session
- (c) No retained backups: Not retain any backups, snapshots, or copies of Buyer data after an instance is terminated
- (d) Breach disclosure: Disclose any suspected or actual data breach affecting Buyer data on your node to GridShare within 24 hours of becoming aware of it
- (e) Valid PAN: Furnish a valid PAN to receive payouts; TDS is deducted as described in Section 5
- (f) Withholding and forfeiture: Acknowledge that GridShare may withhold or forfeit your payout for the affected period where fraud or a violation of these terms is verified
- (g) Abuse monitoring: Acknowledge that GridShare performs metadata-only abuse monitoring (e.g., resource usage patterns and network metadata) — never the contents of Buyer workloads; Section 7(j) describes a separate record of entry into Buyer containers
- (h) Law enforcement: Cooperate with GridShare and law enforcement authorities in connection with any lawful investigation involving your node
- (i) Accuracy of tax and payout information: You are responsible for the accuracy and completeness of the PAN, GST registration status, and bank account or UPI payout details you provide to GridShare, and for promptly updating them if they change. You agree to indemnify and hold GridShare harmless from any tax, TDS, GST, interest, penalty, or related cost or expense that GridShare incurs as a result of any inaccurate, incomplete, or outdated tax or payout information you furnish.
- (j) Access logging: Acknowledge that, where your node runs Buyer workloads in Docker containers, the GridShare node software keeps a record of certain entry into those containers, on these terms:
- What is recorded. The node software reads the Docker daemon’s own event stream for the containers it creates for Buyers (instances, serverless workers and jobs). It records each time anyone, through any tool that talks to the Docker daemon (for example the
docker command, Docker Desktop or Portainer), runs a command or opens a shell inside such a container, attaches to it, copies files into or out of it, exports it, or saves it as an image. For each such action it sends GridShare a report containing: the type of action; for a command, its first 200 characters (never its output) and Docker’s reference for it; the container and the Buyer workload it belongs to; the time; and the node software version. GridShare links the report to your node and account and, for a rented instance, to the Buyer account that rented it. A copy of each report is also written to a log file on your machine. A command is recorded as typed, so it can include a file name or, if one was typed, a password or key.
- What is recorded during a session. When anyone other than the node software runs a command or opens a shell inside such a container, the node software also follows that session until it ends and reports: each command run in it (its first 200 characters, never its output); the files and folders those commands have open, checked several times a second, and whether each was opened for reading or writing; the network addresses they connect to; and how much data, in total, those commands read and wrote. A command is recorded as typed, so it can include a file name or text passed to it by another command. No report contains the contents of a file or the output of a command. Processes the Buyer runs in the same container, including the Buyer’s own shells and anything they start, are not followed. If a process started in the session leaves it, only that program’s name is recorded and it is not followed further; processes still running when the command or shell ends are not followed either. Where the node software cannot follow a session in full (for example under Docker Desktop on Windows, or when it does not run as root), the report says so. A session that the node software followed in full, in which no Buyer file was opened and nothing was sent out, is treated as a check of your machine and closed without action.
- Not reported. The node software’s own automated operations (such as the commands it runs to start, check, save or stop a workload) are recognised and not reported. On node software released since September 10, 2026, health checks that Docker runs by itself on a container’s regular schedule are not reported either, and a health check that runs outside that schedule is reported and marked as a health check. No report contains the contents of a file or the output of a command.
- What the record cannot see. The record is not complete. Reading a container’s logs, listing its processes, inspecting it or viewing its resource use through Docker produces no report; nor does reading a Buyer’s files directly from your disk, reaching into a container or its memory with tools that bypass the Docker daemon, or anything done while the node software or Docker is stopped or your node is offline. Workloads that do not run in Docker are not covered; nor is a node still running older node software that does not keep this record, until it updates; and a report can be lost before it reaches GridShare. A method not being recorded does not make it permitted: Sections 6 and 7(b) apply to every form of access, recorded or not.
- Your own rentals. Entry into a container you rented yourself, or one running on a node private to your own organisation, is still recorded but is not treated as a breach.
- No interference. You must not disable, alter or interfere with the access log or its reports, or use any method intended to enter a Buyer’s container without it being recorded. Pausing or disconnecting your node as permitted by Section 3 is not interference.
- Access log status. The node software also tells GridShare whether the access log is switched on and running on your node. While it is switched off or has stopped working, GridShare may stop offering that node for new Buyer rentals until the log is running again. Rentals already running are not stopped. This is a condition of listing, not a finding against you, and it lifts by itself once the log is running again.
- Nothing is automatic. A report is a record of what the Docker daemon saw, not a finding against you. No node is delisted, no earnings are held and no account action is taken because of a report until a member of GridShare’s team has reviewed it. If a report has an innocent explanation (for example, a health check built into the container image), GridShare closes it and nothing further happens. Otherwise, as an interim step while it investigates, GridShare may remove your nodes from the marketplace and hold your unpaid earnings (Section 4). Before a final decision, GridShare will tell you what was recorded and give you a chance to explain, except where Section 1 allows immediate action for a serious violation. Where GridShare concludes that you breached Section 6 or Section 7(b) or (c), it may stop any Buyer workloads still running on your nodes, revoke your node software’s access, terminate your account under Section 6, and withhold earnings as allowed by Section 7(f) and Section 12 of the Terms of Service.
- Use and retention. GridShare uses reports only to protect Buyer data, to enforce this Agreement, to resolve disputes and to meet legal obligations, including notifying an affected Buyer or an authority where the law requires it, reporting a suspected offence under Section 6, and co-operating under Section 7(h). GridShare keeps reports for three years from the date of the report, including after your account is closed. It keeps a report longer while a related dispute, investigation or legal claim is open and, where a report supports a decision to withhold or recover money, for as long as the related financial records are kept (Section 3.1 of the Privacy Policy). The copy on your machine is kept until the log file passes about 1 MB, when it is cleared and started again.
8. General
This Agreement is governed by the laws of India, with jurisdiction in Chennai, Tamil Nadu. It incorporates by reference the GridShare Terms of Service, Privacy Policy and Acceptable Use Policy; in the event of a conflict on a Provider-specific matter, this Provider Agreement prevails. GridShare may amend this Agreement with notice; continued use of the Platform after the effective date constitutes acceptance.
9. Survival
Termination, expiry, or suspension of this Agreement — for any reason, and including termination of a Provider's account for a violation under Section 6 — does not extinguish any obligation that by its nature is intended to continue. Without limitation, Section 5 (TDS and accrued tax obligations), Section 6 (Data on Provider Hardware), Section 7(b)-(d) (no access to Buyer data, no retained backups, and breach disclosure), and Section 8 (General, including Governing Law and Jurisdiction), together with any accrued payment, confidentiality, indemnity, and liability obligations, survive termination and remain enforceable. The confidentiality, data-protection, and breach-disclosure obligations in Sections 6 and 7(b)-(d) survive indefinitely, notwithstanding that the event of termination may itself arise from a breach of those Sections.
Operator: Quartusbrain Ideas Private Limited (brand: GridShare), Chennai · CIN U62011TN2026PTC194854 · Questions: support@gridshare.in · Company details: Contact