# Authentication Source: https://www.thundercompute.com/docs/agents/operations/authentication Use your AI agent to authenticate with Thunder Compute, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. Thunder Compute uses your agent's standard MCP authentication flow. For example, in Claude Code you can run `/mcp` to connect and complete the browser-based sign-in flow for the Thunder Compute server. # Connecting to Instances Source: https://www.thundercompute.com/docs/agents/operations/connecting-to-instances Ask your AI agent to connect to instances and run commands, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Creating Instances Source: https://www.thundercompute.com/docs/agents/operations/creating-instances Ask your AI agent to create Thunder Compute instances, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Deleting Instances Source: https://www.thundercompute.com/docs/agents/operations/deleting-instances Ask your AI agent to delete Thunder Compute instances, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # File Transfers Source: https://www.thundercompute.com/docs/agents/operations/file-transfers Ask your AI agent to move data to and from Thunder Compute instances, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Modifying Instances Source: https://www.thundercompute.com/docs/agents/operations/modifying-instances Ask your AI agent to update instance configuration, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Monitoring Instances Source: https://www.thundercompute.com/docs/agents/operations/monitoring-instances Ask your AI agent for instance status and usage, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Port Forwarding Source: https://www.thundercompute.com/docs/agents/operations/port-forwarding Ask your AI agent to set up or inspect port forwarding, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Snapshots Source: https://www.thundercompute.com/docs/agents/operations/snapshots Ask your AI agent to create, restore, or delete snapshots, or switch to another interface for direct control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # SSH on Thunder Compute Source: https://www.thundercompute.com/docs/agents/operations/ssh Ask your AI agent to work through Thunder Compute over MCP, or switch to another interface for direct SSH control. MCP server Editor extension Command line Web interface Ask your agent in natural language. For direct control, switch to another interface. # Quickstart Source: https://www.thundercompute.com/docs/agents/quickstart Connect AI tools to GPUs to develop faster MCP server Editor extension Command line Web interface In just 60 seconds you can start developing on GPUs by connecting Cursor, Claude Code, etc. directly to our API. This allows your AI agent to help you set up and manage servers on your behalf. ## Create an Account Sign up for a Thunder Compute account [here](https://console.thundercompute.com/signup). ## Add a Payment Method Add a [payment method](https://console.thundercompute.com/settings/billing) to your account. ## Connect Your Agent Use an AI agent that supports remote MCP servers (Claude Code, Cursor, Codex, etc.). Run this in your terminal: ```bash theme={null} claude mcp add --transport http thunder-compute https://www.thundercompute.com/mcp ``` Then start Claude Code and run `/mcp` to authenticate. A browser window will open for you to log in and authorize access. Alternatively, add to `~/.claude.json` (global) or `.claude.json` in your project root: ```json theme={null} { "mcpServers": { "thunder-compute": { "url": "https://www.thundercompute.com/mcp" } } } ``` Run this in your terminal: ```bash theme={null} codex mcp add thunder-compute --url https://www.thundercompute.com/mcp ``` Codex will prompt you to authenticate via OAuth when you first use a Thunder Compute tool. Add to `.cursor/mcp.json` in your project root (or `~/.cursor/mcp.json` for global access): ```json theme={null} { "mcpServers": { "thunder-compute": { "type": "http", "url": "https://www.thundercompute.com/mcp" } } } ``` Add to your MCP configuration: ```json theme={null} { "mcpServers": { "thunder-compute": { "serverUrl": "https://www.thundercompute.com/mcp", "headers": { "Content-Type": "application/json" } } } } ``` Run the interactive setup: ```bash theme={null} opencode mcp add ``` When prompted: * **Server name:** `thunder-compute` * **Server type:** `Remote` * **URL:** `https://www.thundercompute.com/mcp` * **Requires OAuth:** `Yes` * **Pre-registered client ID:** `No` ```bash theme={null} opencode mcp auth thunder-compute ``` A browser window will open for you to log in and authorize access. ```bash theme={null} opencode ``` The Thunder Compute tools are now available in your session. Alternatively, add to `~/.config/opencode/opencode.json`: ```json theme={null} { "$schema": "https://opencode.ai/config.json", "mcp": { "thunder-compute": { "type": "remote", "url": "https://www.thundercompute.com/mcp", "oauth": {} } } } ``` Then run `opencode mcp auth thunder-compute` to authenticate. If you use an MCP client that supports [Smithery](https://smithery.ai), you can install directly: ```bash theme={null} npx @smithery/cli install @thunder-compute/thunder-compute ``` Or browse the [Thunder Compute listing on Smithery](https://smithery.ai/server/@thunder-compute/thunder-compute) and click **Install** for your client. For custom integrations, the MCP server uses [Streamable HTTP transport](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http) at a single endpoint. Authentication is via OAuth 2.0 with standard MCP discovery. **Endpoint:** `https://www.thundercompute.com/mcp` ```bash theme={null} curl -X POST https://www.thundercompute.com/mcp \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "method": "initialize", "params": { "protocolVersion": "2025-03-26", "capabilities": {}, "clientInfo": { "name": "my-agent", "version": "1.0.0" } }, "id": 1 }' ``` ## Try It Out Once configured, ask your AI agent to: * "Spin up an A100 instance with PyTorch" * "List my running instances" * "Run `nvidia-smi` on my instance" * "How much have I spent this month?" The MCP server gives your agent access to everything you would want to do with a GPU. ## Next Steps * Read the [full MCP Server guide](/guides/mcp-server) for the complete list of available tools, prompts, and troubleshooting * Learn about [Prototyping vs Production](/prototyping-vs-production) to choose the right mode for your workload * Explore [Technical Specifications](/technical-specs) for hardware, networking, and storage details # Add SSH key to instance Source: https://www.thundercompute.com/docs/api-reference/instances/add-ssh-key-to-instance https://api.thundercompute.com:8443/openapi.json post /instances/{id}/add_key Add an SSH key to an existing instance. If public_key is provided in the request body, it will be added to authorized_keys. If no public_key is provided, a new key pair will be generated and the private key returned. # Create instance Source: https://www.thundercompute.com/docs/api-reference/instances/create-instance https://api.thundercompute.com:8443/openapi.json post /instances/create Create a new compute instance # Delete instance Source: https://www.thundercompute.com/docs/api-reference/instances/delete-instance https://api.thundercompute.com:8443/openapi.json post /instances/{id}/delete Delete a compute instance by ID # List instances Source: https://www.thundercompute.com/docs/api-reference/instances/list-instances https://api.thundercompute.com:8443/openapi.json get /instances/list Get a list of user's compute instances # Modify instance Source: https://www.thundercompute.com/docs/api-reference/instances/modify-instance https://api.thundercompute.com:8443/openapi.json post /instances/{id}/modify Modify a running compute instance's resources # Create a snapshot Source: https://www.thundercompute.com/docs/api-reference/snapshots/create-a-snapshot https://api.thundercompute.com:8443/openapi.json post /snapshots/create Create a new snapshot from a running instance # Delete a snapshot Source: https://www.thundercompute.com/docs/api-reference/snapshots/delete-a-snapshot https://api.thundercompute.com:8443/openapi.json delete /snapshots/{id} Delete a snapshot by ID # List snapshots Source: https://www.thundercompute.com/docs/api-reference/snapshots/list-snapshots https://api.thundercompute.com:8443/openapi.json get /snapshots/list Get a list of all snapshots for the authenticated user's organization # Add an SSH key Source: https://www.thundercompute.com/docs/api-reference/ssh-keys/add-an-ssh-key https://api.thundercompute.com:8443/openapi.json post /keys/add Add a new SSH public key to the authenticated user's organization # Delete an SSH key Source: https://www.thundercompute.com/docs/api-reference/ssh-keys/delete-an-ssh-key https://api.thundercompute.com:8443/openapi.json delete /keys/{id} Delete an SSH key by ID # List SSH keys Source: https://www.thundercompute.com/docs/api-reference/ssh-keys/list-ssh-keys https://api.thundercompute.com:8443/openapi.json get /keys/list Get a list of all SSH keys for the authenticated user's organization # Get current pricing Source: https://www.thundercompute.com/docs/api-reference/utilities/get-current-pricing https://api.thundercompute.com:8443/openapi.json get /pricing Retrieve current hourly pricing information for compute resources # Get GPU specifications Source: https://www.thundercompute.com/docs/api-reference/utilities/get-gpu-specifications https://api.thundercompute.com:8443/openapi.json get /specs Retrieve GPU spec configurations for all supported GPU types, counts, and modes # Get thunder templates Source: https://www.thundercompute.com/docs/api-reference/utilities/get-thunder-templates https://api.thundercompute.com:8443/openapi.json get /thunder-templates Get available thunder templates for instance creation # Billing Source: https://www.thundercompute.com/docs/billing Understand Thunder Compute's usage-based billing, payment methods, billing alerts, current rates, and tips for saving on GPU cloud costs. ## Payment Options There are **two ways to pay** for Thunder Compute: ### Option 1: Auto-Pay Set up auto-pay by saving a credit card. Go to [console.thundercompute.com/settings/billing](https://console.thundercompute.com/settings/billing) and click "Manage saved payment method" (or "Add card to enable auto-pay" if no card is on file). ### Option 2: Preload Credit Add credit directly to your account as an alternative to auto-pay. This credit never expires and will be used before any saved payment method. **Order of payment** 1. Any preloaded credit you've added 2. Charges to your saved payment method You can switch between options or use both—set up auto-pay anytime, even if you started with preloaded credit. ## Billing Alerts * **Instance reminders:** We'll email you about any running instances so you're never caught off guard. * **Threshold charges:** As your usage grows, we'll bill your card at preset checkpoints (which rise over time) to prevent runaway bills. ## Our rates All compute resources are billed per minute only while your instances run. Rates and promotions are subject to change without notice. For current rates, see our [pricing page](https://www.thundercompute.com/pricing). ## Credit Terms * **Preloaded credit** does not expire and will be used before charging your saved card. * **Promotional credit** can be revoked at our discretion. * **Refunds:** Credit is non-refundable. ## Money-Saving Tips While Thunder Compute is already the cheapest GPU cloud platform, there are a few strategies we recommend to reduce your bill: * Delete instances when you're done with them to stop billing. * Right‑size new workloads with `tnr create --gpu`, `--vcpus`, and related flags so you only pay for what you use. We think this balances a smooth experience with strong verification—but if you have feedback or questions, please hop into our [Discord](https://discord.com/invite/nwuETS9jJK). We're always happy to improve! # Data Processing Addendum Source: https://www.thundercompute.com/docs/guides/data-processing-addendum Review the Data Processing Addendum for Thunder Compute. Audit legal terms, data handling protocols, and privacy compliance for your organization. ## Sample Agreement Data Processing Agreement ## Using this DPA This DPA has 2 parts: (1) the Key Terms on this Cover Page and (2) the Common Paper DPA Standard Terms Version 1 posted at commonpaper.com/standards/data-processing-agreement/1.1 (“DPA Standard Terms”), which is incorporated by reference. If there is any inconsistency between the parts of the DPA, the Cover Page will control over the DPA Standard Terms. Capitalized and highlighted words have the meanings given on the Cover Page. However, if the Cover Page omits or does not define a highlighted word, the default meaning will be “none” or “not applicable” and the correlating clause, sentence, or section does not apply to this Agreement. All other capitalized words have the meanings given in the DPA Standard Terms or the Agreement. A copy of the DPA Standard Terms is attached for convenience only. ## Key Terms The key legal terms of the DPA are as follows: | Term | Details | | ------------------------- | ---------------------------------------------------------------------------------------------- | | Agreement | Reference to sales contract will be set when sending agreement | | Approved Subprocessors | [https://www.thundercompute.com/sub-processors](https://www.thundercompute.com/sub-processors) | | Provider Security Contact | `support@thundercompute.com` | | Security Policy | As defined in the Agreement. | ### Service Provider Relationship To the extent California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq (“CCPA”) applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as agreed in the Agreement and detailed below (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer under the Agreement. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer under the Agreement except as necessary for providing the Service for Customer, as stated in the Agreement, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this paragraph and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA. ## Restricted Transfers ### Governing Member State * EEA Transfers: Ireland * UK Transfers: England and Wales ## Annex I(A) List of Parties ### Data Exporter * Name: the Customer signing this DPA * Activities relevant to transfer: See Annex I(B) * Role: Controller ### Data Importer * Name: the Provider signing this DPA * Contact person: Carl Peterson, CEO * Address: 887 w marietta st nw, Suite N105, Georgia 30318, USA * Activities relevant to transfer: See Annex I(B) * Role: Processor ## Annex I(B) Description of Transfer and Processing Activities ### Service The Service is: GPU cloud computing with on-demand cloud instances, backed by physical servers, in addition to data storage. ### Categories of Data Subjects * Customer's employees ### Categories of Personal Data * Name * Contact information such as email, phone number, or address * Financial information such as bank account numbers * Transactional information such as account information or purchases * User activity and analysis such as device information or IP address * Location information ### Special Category Data Is special category data (as defined in Article 9 of the GDPR) Processed? No ### Frequency of Transfer Continuous ### Nature and Purpose of Processing * Receiving data, including collection, accessing, retrieval, recording, and data entry * Holding data, including storage, organization, and structuring * Using data, including analysis, consultation, testing, automated decision making, and profiling * Updating data, including correcting, adaption, alteration, alignment, and combination * Protecting data, including restricting, encrypting, and security testing * Sharing data, including disclosure, dissemination, allowing access, or otherwise making available * Returning data to the data exporter or data subject * Erasing data, including destruction and deletion ### Duration of Processing Provider will process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in Section 2.2(a)-(d) of the Standard Terms; or (ii) by Applicable Laws. ## Annex I(C) ### Competent Supervisory Authority The supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum. ## Annex II ### Technical and Organizational Security Measures See Security Policy Provider and Customer have not changed the DPA Standard Terms except for the details on the Cover Page above. By signing this Cover Page, each party agrees to enter into this DPA as of the last date of signature below. ## Signatures | Field | Provider (Thunder Compute) | Customer | | -------------------- | -------------------------- | -------- | | Signature | | | | Print Name | | | | Title | | | | Legal Notice Address | `carl@thundercompute.com` | | | Date | | | ## 1. Processor and Subprocessor Relationships ### 1.1 Provider as Processor In situations where Customer is a Controller of the Customer Personal Data, Provider will be deemed a Processor that is Processing Personal Data on behalf of Customer. ### 1.2 Provider as Subprocessor In situations where Customer is a Processor of the Customer Personal Data, Provider will be deemed a Subprocessor of the Customer Personal Data. ## 2. Processing ### 2.1 Processing Details Annex I(B) on the Cover Page describes the subject matter, nature, purpose, and duration of this Processing, as well as the Categories of Personal Data collected and Categories of Data Subjects. ### 2.2 Processing Instructions Customer instructs Provider to Process Customer Personal Data: (a) to provide and maintain the Service; (b) as may be further specified through Customer’s use of the Service; (c) as documented in the Agreement; and (d) as documented in any other written instructions given by Customer and acknowledged by Provider about Processing Customer Personal Data under this DPA. Provider will abide by these instructions unless prohibited from doing so by Applicable Laws. Provider will immediately inform Customer if it is unable to follow the Processing instructions. Customer has given and will only give instructions that comply with Applicable Laws. ### 2.3 Processing by Provider Provider will only Process Customer Personal Data in accordance with this DPA, including the details in the Cover Page. If Provider updates the Service to update existing or include new products, features, or functionality, Provider may change the Categories of Data Subjects, Categories of Personal Data, Special Category Data, Special Category Data Restrictions or Safeguards, Frequency of Transfer, Nature and Purpose of Processing, and Duration of Processing as needed to reflect the updates by notifying Customer of the updates and changes. ### 2.4 Customer Processing Where Customer is a Processor and Provider is a Subprocessor, Customer will comply with all Applicable Laws that apply to Customer’s Processing of Customer Personal Data. Customer’s agreement with its Controller will similarly require Customer to comply with all Applicable Laws that apply to Customer as a Processor. In addition, Customer will comply with the Subprocessor requirements in Customer’s agreement with its Controller. ### 2.5 Consent to Processing Customer has complied with and will continue to comply with all Applicable Data Protection Laws concerning its provision of Customer Personal Data to Provider and/or the Service, including making all disclosures, obtaining all consents, providing adequate choice, and implementing relevant safeguards required under Applicable Data Protection Laws. ### 2.6 Subprocessors 1. Provider will not provide, transfer, or hand over any Customer Personal Data to a Subprocessor unless Customer has approved the Subprocessor. The current list of Approved Subprocessors includes the identities of the Subprocessors, their country of location, and their anticipated Processing tasks. Provider will inform Customer at least 10 business days in advance and in writing of any intended changes to the Approved Subprocessors whether by addition or replacement of a Subprocessor, which allows Customer to have enough time to object to the changes before the Provider begins using the new Subprocessor(s). Provider will give Customer the information necessary to allow Customer to exercise its right to object to the change to Approved Subprocessors. Customer has 30 days after notice of a change to the Approved Subprocessors to object, otherwise Customer will be deemed to accept the changes. If Customer objects to the change within 30 days of notice, Customer and Provider will cooperate in good faith to resolve Customer’s objection or concern. 2. When engaging a Subprocessor, Provider will have a written agreement with the Subprocessor that ensures the Subprocessor only accesses and uses Customer Personal Data (i) to the extent required to perform the obligations subcontracted to it, and (ii) consistent with the terms of Agreement. 3. If the GDPR applies to the Processing of Customer Personal Data, (i) the data protection obligations described in this DPA (as referred to in Article 28(3) of the GDPR, if applicable) are also imposed on the Subprocessor, and (ii) Provider’s agreement with the Subprocessor will incorporate these obligations, including details about how Provider and its Subprocessor will coordinate to respond to inquiries or requests about the Processing of Customer Personal Data. In addition, Provider will share, at Customer’s request, a copy of its agreements (including any amendments) with its Subprocessors. To the extent necessary to protect business secrets or other confidential information, including personal data, Provider may redact the text of its agreement with its Subprocessor prior to sharing a copy. 4. Provider remains fully liable for all obligations subcontracted to its Subprocessors, including the acts and omissions of its Subprocessors in Processing Customer Personal Data. Provider will notify Customer of any failure by its Subprocessors to fulfill a material obligation about Customer Personal Data under the agreement between Provider and the Subprocessor. ## 3. Restricted Transfers ### 3.1 Authorization Customer agrees that Provider may transfer Customer Personal Data outside the EEA, the United Kingdom, or other relevant geographic territory as necessary to provide the Service. If Provider transfers Customer Personal Data to a territory for which the European Commission or other relevant supervisory authority has not issued an adequacy decision, Provider will implement appropriate safeguards for the transfer of Customer Personal Data to that territory consistent with Applicable Data Protection Laws. ### 3.2 Ex-EEA Transfers Customer and Provider agree that if the GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the EEA to Provider outside of the EEA, and the transfer is not governed by an adequacy decision made by the European Commission, then by entering into this DPA, Customer and Provider are deemed to have signed the EEA SCCs and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the EEA SCCs, which are completed as follows: 1. Module Two (Controller to Processor) of the EEA SCCs apply when Customer is a Controller and Provider is Processing Customer Personal Data for Customer as a Processor. 2. Module Three (Processor to Sub-Processor) of the EEA SCCs apply when Customer is a Processor and Provider is Processing Customer Personal Data on behalf of Customer as a Subprocessor. 3. For each module, the following applies (when applicable): * The optional docking clause in Clause 7 does not apply; * In Clause 9, Option 2 (general written authorization) applies, and the minimum time period for prior notice of Subprocessor changes is 10 business days; * In Clause 11, the optional language does not apply; * All square brackets in Clause 13 are removed; * In Clause 17 (Option 1), the EEA SCCs will be governed by the laws of Governing Member State; * In Clause 18(b), disputes will be resolved in the courts of the Governing Member State; and * The Cover Page to this DPA contains the information required in Annex I, Annex II, and Annex III of the EEA SCCs. ### 3.3 Ex-UK Transfers Customer and Provider agree that if the UK GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the United Kingdom to Provider outside of the United Kingdom, and the transfer is not governed by an adequacy decision made by the United Kingdom Secretary of State, then by entering into this DPA, Customer and Provider are deemed to have signed the UK Addendum and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the UK Addendum, which is completed as follows: 1. Section 3.2 of this DPA contains the information required in Table 2 of the UK Addendum. 2. Table 4 of the UK Addendum is modified as follows: Neither party may end the UK Addendum as set out in Section 19 of the UK Addendum; to the extent ICO issues a revised Approved Addendum under Section ‎18 of the UK Addendum, the parties will work in good faith to revise this DPA accordingly. 3. The Cover Page contains the information required by Annex 1A, Annex 1B, Annex II, and Annex III of the UK Addendum. ### 3.4 Other International Transfers For Personal Data transfers where Swiss law (and not the law in any EEA member state or the United Kingdom) applies to the international nature of the transfer, references to the GDPR in Clause 4 of the EEA SCCs are, to the extent legally required, amended to refer to the Swiss Federal Data Protection Act or its successor instead, and the concept of supervisory authority will include the Swiss Federal Data Protection and Information Commissioner. ## 4. Security Incident Response Upon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 72 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident. ## 5. Audit & Reports ### 5.1 Audit Rights Provider will give Customer all information reasonably necessary to demonstrate its compliance with this DPA and Provider will allow for and contribute to audits, including inspections by Customer, to assess Provider’s compliance with this DPA. However, Provider may restrict access to data or information if Customer’s access to the information would negatively impact Provider’s intellectual property rights, confidentiality obligations, or other obligations under Applicable Laws. Customer acknowledges and agrees that it will only exercise its audit rights under this DPA and any audit rights granted by Applicable Data Protection Laws by instructing Provider to comply with the reporting and due diligence requirements below. Provider will maintain records of its compliance with this DPA for 3 years after the DPA ends. ### 5.2 Security Reports Customer acknowledges that Provider is regularly audited against the standards defined in the Security Policy by independent third-party auditors. Upon written request, Provider will give Customer, on a confidential basis, a summary copy of its then-current Report so that Customer can verify Provider’s compliance with the standards defined in the Security Policy. ### 5.3 Security Due Diligence In addition to the Report, Provider will respond to reasonable requests for information made by Customer to confirm Provider’s compliance with this DPA, including responses to information security, due diligence, and audit questionnaires, or by giving additional information about its information security program. All such requests must be in writing and made to the Provider Security Contact and may only be made once a year. ## 6. Coordination & Cooperation ### 6.1 Response to Inquiries If Provider receives any inquiry or request from anyone else about the Processing of Customer Personal Data, Provider will notify Customer about the request and Provider will not respond to the request without Customer’s prior consent. Examples of these kinds of inquiries and requests include a judicial or administrative or regulatory agency order about Customer Personal Data where notifying Customer is not prohibited by Applicable Law, or a request from a data subject. If allowed by Applicable Law, Provider will follow Customer’s reasonable instructions about these requests, including providing status updates and other information reasonably requested by Customer. If a data subject makes a valid request under Applicable Data Protection Laws to delete or opt out of Customer’s giving of Customer Personal Data to Provider, Provider will assist Customer in fulfilling the request according to the Applicable Data Protection Law. Provider will cooperate with and provide reasonable assistance to Customer, at Customer’s expense, in any legal response or other procedural action taken by Customer in response to a third-party request about Provider’s Processing of Customer Personal Data under this DPA. ### 6.2 DPIAs and DTIAs If required by Applicable Data Protection Laws, Provider will reasonably assist Customer in conducting any mandated data protection impact assessments or data transfer impact assessments and consultations with relevant data protection authorities, taking into consideration the nature of the Processing and Customer Personal Data. ## 7. Deletion of Customer Personal Data ### 7.1 Deletion by Customer Provider will enable Customer to delete Customer Personal Data in a manner consistent with the functionality of the Services. Provider will comply with this instruction as soon as reasonably practicable except where further storage of Customer Personal Data is required by Applicable Law. ### 7.2 Deletion at DPA Expiration 1. After the DPA expires, Provider will return or delete Customer Personal Data at Customer’s instruction unless further storage of Customer Personal Data is required or authorized by Applicable Law. If return or destruction is impracticable or prohibited by Applicable Laws, Provider will make reasonable efforts to prevent additional Processing of Customer Personal Data and will continue to protect the Customer Personal Data remaining in its possession, custody, or control. For example, Applicable Laws may require Provider to continue hosting or Processing Customer Personal Data. 2. If Customer and Provider have entered the EEA SCCs or the UK Addendum as part of this DPA, Provider will only give Customer the certification of deletion of Personal Data described in Clause 8.1(d) and Clause 8.5 of the EEA SCCs if Customer asks for one. ## 8. Limitation of Liability ### 8.1 Liability Caps and Damages Waiver To the maximum extent permitted under Applicable Data Protection Laws, each party’s total cumulative liability to the other party arising out of or related to this DPA will be subject to the waivers, exclusions, and limitations of liability stated in the Agreement. ### 8.2 Related-Party Claims Any claims made against Provider or its Affiliates arising out of or related to this DPA may only be brought by the Customer entity that is a party to the Agreement. ### 8.3 Exceptions This DPA does not limit any liability to an individual about the individual’s data protection rights under Applicable Data Protection Laws. In addition, this DPA does not limit any liability between the parties for violations of the EEA SCCs or UK Addendum. ## 9. Conflicts Between Documents This DPA forms part of and supplements the Agreement. If there is any inconsistency between this DPA, the Agreement, or any of their parts, the part listed earlier will control over the part listed later for that inconsistency: (1) the EEA SCCs or the UK Addendum, (2) this DPA, and then (3) the Agreement. ## 10. Term of Agreement This DPA will start when Provider and Customer agree to a Cover Page for the DPA and sign or electronically accept the Agreement and will continue until the Agreement expires or is terminated. However, Provider and Customer will each remain subject to the obligations in this DPA and Applicable Data Protection Laws until Customer stops transferring Customer Personal Data to Provider and Provider stops Processing Customer Personal Data. ## 11. Definitions ### 11.1 Applicable Laws “Applicable Laws” means the laws, rules, regulations, court orders, and other binding requirements of a relevant government authority that apply to or govern a party. ### 11.2 Applicable Data Protection Laws “Applicable Data Protection Laws” means the Applicable Laws that govern how the Service may process or use an individual’s personal information, personal data, personally identifiable information, or other similar term. ### 11.3 Controller “Controller” will have the meaning(s) given in the Applicable Data Protection Laws for the company that determines the purpose and extent of Processing Personal Data. ### 11.4 Cover Page “Cover Page” means a document that is signed or electronically accepted by the parties that incorporates these DPA Standard Terms and identifies Provider, Customer, and the subject matter and details of the data processing. ### 11.5 Customer Personal Data “Customer Personal Data” means Personal Data that Customer uploads or provides to Provider as part of the Service and that is governed by this DPA. ### 11.6 DPA “DPA” means these DPA Standard Terms, the Cover Page between Provider and Customer, and the policies and documents referenced in or attached to the Cover Page. ### 11.7 EEA SCCs “EEA SCCs” means the standard contractual clauses annexed to the European Commission's Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the European Council. ### 11.8 European Economic Area (EEA) “European Economic Area” or “EEA” means the member states of the European Union, Norway, Iceland, and Liechtenstein. ### 11.9 GDPR “GDPR” means European Union Regulation 2016/679 as implemented by local law in the relevant EEA member nation. ### 11.10 Personal Data “Personal Data” will have the meaning(s) given in the Applicable Data Protection Laws for personal information, personal data, or other similar term. ### 11.11 Processing “Processing” or “Process” will have the meaning(s) given in the Applicable Data Protection Laws for any use of, or performance of a computer operation on, Personal Data, including by automatic methods. ### 11.12 Processor “Processor” will have the meaning(s) given in the Applicable Data Protection Laws for the company that Processes Personal Data on behalf of the Controller. ### 11.13 Report “Report” means audit reports prepared by another company according to the standards defined in the Security Policy on behalf of Provider. ### 11.14 Restricted Transfer “Restricted Transfer” means (a) where the GDPR applies, a transfer of personal data from the EEA to a country outside of the EEA which is not subject to an adequacy determination by the European Commission; and (b) where the UK GDPR applies, a transfer of personal data from the United Kingdom to any other country which is not subject to adequacy regulations adopted pursuant to Section 17A of the United Kingdom Data Protection Act 2018. ### 11.15 Security Incident “Security Incident” means a Personal Data Breach as defined in Article 4 of the GDPR. ### 11.16 Service “Service” means the product and/or services described in the Agreement. ### 11.17 Special Category Data "Special Category Data” will have the meaning given in Article 9 of the GDPR. ### 11.18 Subprocessor “Subprocessor” will have the meaning(s) given in the Applicable Data Protection Laws for a company that, with the approval and acceptance of Controller, assists the Processor in Processing Personal Data on behalf of the Controller. ### 11.19 UK GDPR “UK GDPR” means European Union Regulation 2016/679 as implemented by section 3 of the United Kingdom’s European Union (Withdrawal) Act of 2018 in the United Kingdom. ### 11.20 UK Addendum “UK Addendum” means the international data transfer addendum to the EEA SCCs issued by the Information Commissioner for Parties making Restricted Transfers under S119A(1) Data Protection Act 2018. # Self-host Deepseek R1 Source: https://www.thundercompute.com/docs/guides/deepseek-r1-running-locally-on-thunder-compute Self-host Deepseek R1 on Thunder Compute cloud GPUs. Local model deployment and configure hardware for optimized inference performance. # Easily Run DeepSeek R1 on Thunder Compute Looking for the **cheapest way to run DeepSeek R1** or just want to **try DeepSeek R1** without buying hardware? Thunder Compute lets you spin up pay‑per‑minute A100 GPUs so you only pay for the time you use. Follow the steps below to get the model running in minutes. > **Quick reminder:** Make sure your Thunder Compute account is set up. If not, start with our [Quickstart Guide](/vscode/quickstart). If you prefer video instructions, watch this overview: