Skip to content

Smart Launch. Describe the workload, get the GPUs that fit.See how →
    • GPU CloudTrain and serve on NVIDIA GPUs in partner datacenters.
    • PricingPer GPU-hour, billed by the minute.
    • CommunityIndependent GPU machines, a private VM per session.
    • Smart LaunchDescribe the workload. Get the GPUs that fit.
    • Budget GuardSet a budget. Never pay past it.
    • EnvironmentsJupyterLab, PyTorch, vLLM, Ollama. Ready at launch.
    • BillingBy the minute, on demand or reserved.
    • SecurityIsolation, access and what each tier protects.
    • GPU calculatorWhich GPU holds your model, line by line.
    Two tiersSecure or Community?Pick the right one for your data.→
    • CLI and SDKTypeScript, Python and the nodelodge command.
    • MCP serverClaude and your agents launch GPUs, under a cap.
    • Agent frameworksLangChain, LlamaIndex, OpenAI and Claude agents.
    • GitHub ActionA GPU step in your workflow, always stopped.
    • NotebooksA GPU from a Jupyter cell.
    • API referenceEvery endpoint, with examples.
    • Overview →
    Hard capsA GPU you can hand to an agent.Spending limits on every API key, enforced by Node Lodge.→
    • LLM inferenceAn OpenAI-compatible endpoint with vLLM.
    • Fine-tuningTrain on your data. Keep the weights.
    • Batch jobsThousands of files, one session.
    • 3D renderingBlender and Cycles, headless.
    • Earn with your GPUsYour price, 85 percent to you, on Community.
    • Install the agentList a machine with one command.
    • Datacenter partnersSell capacity through your cloud API.
    RequirementsUbuntu 24.04 and a recent NVIDIA GPU.HWE kernel 6.12 or newer. Ampere or newer, 12 GB of VRAM or more.→
    • QuickstartFrom access to SSH, step by step.
    • Pick a GPUHow Smart Launch sizes your model.
    • Connect over SSHKeys, addresses, tunnels, files.
    • Sessions and limitsOn demand, reserved, the end of a session.
    • RecipesvLLM, ComfyUI, LoRA, Blender.
    • All docs →
    • AboutWho runs Node Lodge.
    • ContactRequest access, ask a question.
    • ChangelogWhat shipped, and when.
    • Report a vulnerabilityResponsible disclosure, by email.
    • Legal centerTerms, privacy, cookies and data processing.
Sign in
  • English
  • Français
  • Deutsch
  • Español
  • English
  • Français
  • Deutsch
  • Español
Sign inRequest access

Node Lodge legal documents

  • Overview
  • Applies to every service

    • Terms of Service
    • Acceptable Use Policy
    • Privacy Policy
    • Cookie Policy
    • Data Processing Addendum
    • Sub-processors
  • Secure

    • Secure Service Terms
  • Community

    • Community Service Terms
    • Host Agreement
  1. Legal
  2. Acceptable Use Policy
Version française

Acceptable Use Policy

What you may not do on Node Lodge, how we handle reports of abuse and illegal content, copyright notices, and how we decide and appeal sanctions.

Version
1.0
Published
November 7, 2026
Effective
November 7, 2026

1. Scope

1.1. This Acceptable Use Policy (“Policy”) is part of the Terms of Service. Capitalized terms have the meaning given there.

1.2. It applies to every Account, Organization, API key, Session and Host Machine, and to anyone you let use them, including AI agents and automated workflows acting with your API key.

2. Compute

You may not:

  • mine cryptocurrency, or run proof-of-work, proof-of-space or any workload whose main purpose is to consume the Machine for that;
  • run a workload designed to damage hardware or to defeat its thermal or power limits;
  • use a Session to try to reach the Host’s system, the hypervisor, the GPU firmware or the network outside your Session.

3. Illegal and harmful content

3.1. You may not create, store, process or distribute child sexual abuse material of any kind, including synthetic or AI-generated material, or use the Service to train or run a model for that purpose. We report it to the competent authorities and preserve evidence as the law requires.

3.2. You may not create, store, process or distribute material that:

  • is illegal where you are, where the Machine is, or in Québec or Canada;
  • infringes intellectual property, privacy or publicity rights;
  • shows intimate images of a person without their consent, including synthetic images;
  • incites or threatens violence, or promotes terrorism or violent extremism;
  • is used to defraud, impersonate or deceive, including phishing pages, fake payment flows and deceptive deepfakes.

4. Network

You may not:

  • send unsolicited bulk email or messages. Outbound TCP port 25 is blocked;
  • scan, probe or test the vulnerability of systems without their owner’s authorization;
  • attack, flood or disrupt any system or network, including denial-of-service attacks;
  • host or control malware, botnets or command-and-control servers;
  • operate an open proxy, an open relay, a VPN service for third parties or a Tor exit node;
  • falsify packet headers, sender information or any other network identifier.

5. Security and integrity of the Service

You may not:

  • access or try to access another customer’s Machine, data or Account;
  • access Node Lodge, a partner or a Host beyond what your Session or Host Agreement gives you;
  • get around a security, network, budget or billing control, including the Budget Guard, your Limits, API key caps, rate limits, a blocked Account or a suspension;
  • open several Accounts or Organizations to get around a limit or a suspension;
  • test the security of the Service outside our disclosure policy.

6. Access, resale and sanctions

You may not:

  • share an Account, or share an API key with people outside your Organization;
  • resell, sublicense or provide the Service to third parties as such, unless we agree in writing. Offering your own product or model built on the Service is allowed;
  • use the Service in breach of section 20 of the Terms (sanctions and export control).

7. High-risk uses

Do not use the Service to operate systems whose failure could lead to death, bodily injury or serious environmental damage, such as nuclear facilities, aircraft navigation or life-support systems. The Service has no availability commitment suited to them.

8. Reporting abuse and illegal content

8.1. How to report. Anyone can report abuse coming from Node Lodge, with or without an account:

  • with the form at /report-abuse;
  • by email to abuse@nodelodge.com.

8.2. What to include. To let us act, give: the IP address or URL, the date and time with time zone; what happened, with logs or evidence; why the content or activity is illegal or breaches this Policy; and your name and email address, unless you report child sexual abuse material. Tell us if your report is made in good faith on information you believe accurate.

8.3. What happens next. We confirm receipt to reporters who give an email address, review each report without undue delay, and tell the reporter of our decision and of the ways to contest it.

8.4. Authorities. Authorities and law enforcement can reach us at abuse@nodelodge.com, in English or French. We answer lawful orders as the law requires.

9. Copyright notices

9.1. Where to send them. Send notices of claimed copyright infringement, and counter-notices, to abuse@nodelodge.com.

9.2. Notice. A notice must include: your physical or electronic signature as the right holder or a person authorized to act for it; the work claimed to be infringed; the material claimed to be infringing, with enough information to locate it (IP address, URL, date and time); your name, postal address, telephone number and email address; a statement that you believe in good faith that the use is not authorized by the right holder, its agent or the law; and a statement that the notice is accurate and, under penalty of perjury, that you are authorized to act for the right holder.

9.3. What we do. On a complete notice, we act promptly to remove or disable access to the material, which may mean stopping the Session concerned. We forward notices under Canada’s Copyright Act to the customer concerned, as that Act requires.

9.4. Counter-notice. A customer whose material was removed by mistake or misidentification may send a counter-notice with: their signature; the material removed and where it was; a statement, under penalty of perjury, of their good-faith belief that it was removed by mistake or misidentification; their name, address and telephone number; and their consent to the jurisdiction of the courts of their address and to accept service from the person who sent the notice. We forward it to that person. Material deleted with a Machine at the end of a Session cannot be restored.

9.5. Repeat infringers. We close, in appropriate circumstances, the Accounts of repeat infringers: two valid notices not successfully contested within 12 months, or one flagrant infringement.

9.6. Misrepresentation. A person who knowingly makes a material misrepresentation in a notice or counter-notice may be liable for damages.

10. Enforcement

10.1. Investigation. We do not monitor Customer Content. We act on reports, on signals from partners and Hosts, on network metadata (such as flow records of Community Sessions, without content), and on billing and security signals.

10.2. Measures. Depending on the seriousness, the intent, the harm and any repetition, we may, alone or together:

  1. warn you and ask you to fix the issue within a set time;
  2. restrict a feature, an API key or your Limits;
  3. stop a Session, which deletes its Machine;
  4. suspend an Account, an Organization or a Host Machine;
  5. close the Account, with set-off under section 10.2 of the Terms;
  6. report the activity to the competent authorities and preserve the evidence the law requires.

10.3. Urgency. When there is a risk to people, to the Service or to third parties, or when the law requires it, we act at once and explain afterwards.

10.4. Statement of reasons. When we restrict, suspend or close an Account or remove content, we tell the person concerned, unless the law or an ongoing investigation prevents it: what we did and its scope; the facts and the rule we relied on; whether the decision was based on a report; whether automated means were used; and how to contest it.

10.5. Contesting a decision. You may contest a decision within 6 months by replying to our notice or by writing to abuse@nodelodge.com. A person who did not take the first decision reviews it and answers you. If we find the decision was wrong, we reverse it without delay. This does not affect your right to go to court.

10.6. Misuse of reporting. We may stop processing reports from a person who frequently sends manifestly unfounded reports, after a warning.

11. Changes

We may update this Policy under section 22 of the Terms.

Previous versions

No previous version.

Questions about these documents? support@nodelodge.com · privacy@nodelodge.com

On this page

  • 1. Scope
  • 2. Compute
  • 3. Illegal and harmful content
  • 4. Network
  • 5. Security and integrity of the Service
  • 6. Access, resale and sanctions
  • 7. High-risk uses
  • 8. Reporting abuse and illegal content
  • 9. Copyright notices
  • 10. Enforcement
  • 11. Changes

Get Node Lodge product updates by email.

Confirm by email. Unsubscribe anytime.

Product

  • GPU Cloud
  • Pricing
  • Community
  • Secure or Community
  • Smart Launch
  • Budget Guard
  • Billing
  • Security
  • GPU calculator

Developers

  • Overview
  • Quickstart
  • CLI and SDK
  • MCP server
  • API reference
  • Recipes
  • All docs

Use cases

  • LLM inference
  • Fine-tuning
  • Batch jobs
  • 3D rendering

Providers

  • Earn with your GPUs
  • Install the agent
  • Datacenter partners

Company

  • About
  • Contact
  • Request access
  • Changelog
  • Report a vulnerability

Node Lodge by VDTI · © 2026 VDTI

  • Terms
  • Privacy
  • Cookies
  • Acceptable use
  • Sub-processors
  • Legal center
  • English
  • Français
  • Deutsch
  • Español