CloudDock Terms of Service (v1.1)

Effective Date: August 2025
Jurisdiction: State of California, United States

1. Acceptance of Terms

1.1 Acceptance of Terms. By using CloudDock, you agree to be bound by these Terms of Service (“Terms”). If you do not agree, do not use the service. We may update these Terms; your continued use after any update constitutes acceptance. Material changes will be communicated via in-app notices, email, or similar means.

1.2 Age and Contractual Capacity. The service is intended for natural persons who are at least 16 years old. If a jurisdiction requires you to be 18 to enter into contracts or enjoy certain consumer protections, then within that jurisdiction we offer the service only to individuals who are 18 or older. We do not knowingly provide the service to anyone below the local age of majority.

1.3 User Types. Currently, the service is only available to individual users. Enterprise and team plans will be introduced at a later date.

1.4 Dispute Resolution. In the event of a dispute, both parties will first attempt to resolve it through good-faith negotiation. If negotiation fails, litigation must be brought in a court located in California (see Section 8).

1.5 No Warranty. CloudDock is provided “as is” and “as available.” We make no warranties of merchantability, fitness for a particular purpose, uninterrupted use, or error-free operation; you use the service at your own risk (see Section 10).

2. Service Model & Account Usage

2.1 Launch & Allocation. After you select a GPU group and runtime duration, the system automatically assigns an available machine.

2.2 Concurrency Limit. Each account may run only one instance at a time. Exceptions for education or promotional events: the participant must submit a complete project package and receive written approval; any extra concurrency, credits, duration, or GPU group will be specified in that written confirmation.

2.3 Queue & Claim. When resources are scarce you will be placed in a queue. When your turn arrives you have a 5-minute window to claim the instance; if you miss it, the slot is forfeited and you must re-queue.

2.4 Runtime Duration & Changes. The duration you submit is locked in; mid-session extension or shortening is not supported. If you need a longer runtime, terminate the current session and launch a new one. (Future roadmap: “top-up/extend” may be introduced; any such feature will be announced separately.)

2.5 Pause / Suspend. Not supported.

2.6 Resource & Network Restrictions. To maintain platform stability, CloudDock may impose rate limits, bandwidth quotas, I/O quotas, outbound-port blacklists, or other technical restrictions. Circumvention is prohibited.

2.7 Mining & Power Modifications. Mining workloads are neither optimized nor guaranteed; if they impair the platform we may throttle, lower priority, or deny scheduling. Overclocking, undervolting, power-limit modifications, “shunt mods,” or similar alterations are strictly forbidden. Violations will result in permanent suspension and forfeiture of any balance (except where prohibited by law).

2.8 Availability & SLA. We use commercially reasonable efforts to maintain availability. The formal SLA is provided in Annex A (SLA & Credits) (placeholder).

2.9 Billing & Dispute Tie-in. See Section 5. During payment investigations or chargebacks, CloudDock may take necessary risk-control measures.

2.10 Taxes. Prices are quoted tax-exclusive. If applicable taxes are required by law, CloudDock may collect and remit them or require you to self-remit (see Section 5).

3. Container Lifecycle & Watchdog Monitoring

3.1 Shutdown Determination. Normal shutdown: presently refers only to automatic shutdown when the countdown expires. If a console “Stop” button is introduced later, using it will also be deemed normal. Any other shutdown is abnormal (including crashes, watchdog termination, in-container commands, etc.).

3.2 Seizure & Retention Scope (Abnormal). Upon an abnormal event, CloudDock creates a read-only snapshot of the container and its disk image and retains audit logs (event metadata, process/session state, runtime parameters, etc.).

3.3 Retention Period. General anomalies: 1 year; severe violations (e.g., minor-related content, actual attacks): may be retained long-term/permanently with archived copies; longer retention required by law will be observed.

3.4 Notification. We do not proactively notify during investigation; after a conclusion is reached, the outcome is communicated via ticket or in-app message.

3.5 Watchdog Actions. Currently, instances are terminated immediately and seized; future iterations may introduce tiered responses (alert → throttling → termination).

3.6 Forensic Access. We do not enter a running container; only after seizure may authorized personnel access the snapshot in read-only mode under full audit.

3.7 Monitoring Scope. We conduct behavioral and runtime-parameter monitoring (CPU/GPU temperature & utilization, memory/VRAM, disk/IO, process states, abnormal privilege-escalation indicators, GPU idling, etc.); specific detection rules are not disclosed to prevent circumvention.

3.8 Emergency Threats. When there is an imminent threat to personal safety, we may take preservation measures and cooperate as required by law; otherwise, we act solely upon lawful process.

3.9 Log Access. Users have no right to access or export audit logs or forensic materials.

3.10 Security & Location. Seized and retained data are encrypted at rest and subject to least-privilege access, typically stored in facilities located in California, USA.

4. Prohibited Activities / AUP

4.1 Prohibition on Public-Facing Services. You may not offer services to the public or operate as a public node (Web, proxy, VPN, Tor, reverse tunnel, etc.) without written permission.

4.2 Prohibition on Intranet Breach. All forms of intranet penetration, proxying, port mapping, P2P routing, or tunneling are forbidden.

4.3 Prohibition on Scanning. Port scanning, fingerprinting, vulnerability scanning, penetration testing, or similar activities are not allowed.

4.4 Prohibition on Attack Traffic. DDoS/DoS, reflection/amplification, flood, or malicious load-testing traffic is strictly banned.

4.5 Prohibition on Credential Attacks. Brute-force, credential stuffing, dictionary attacks, session hijacking, or similar tactics are prohibited.

4.6 Prohibition on Malware. Malware, backdoors, keyloggers, C2 infrastructure, or any other malicious code is forbidden.

4.7 Prohibition on Spam. Spam, message bombing, or any unauthorized automated mass messaging or harassment is not permitted.

4.8 Prohibition on IP Infringement. Violations of third-party copyrights, trademarks, patents, or trade secrets are disallowed.

4.9 Prohibition on Unauthorized Scraping. High-frequency scraping that circumvents robots.txt or other access controls is banned.

4.10 Mining Policy. Mining is permitted but not optimized; we may throttle, lower priority, or deny scheduling. Detecting overclocking, power-limit changes, or voltage tweaks results in permanent suspension and forfeiture of balance.

4.11 Circumvention Ban. Bypassing quotas, network/port blocks, identity/token checks, monitoring, or other technical controls is prohibited.

4.12 Identity & Resale. Sub-letting, reselling, or account sharing is forbidden; primary-contact identity rules are in Section 7.4.

4.13 Enforcement Actions. We may impose throttling, deny scheduling, terminate and seize instances, suspend, permanently ban, and/or pursue legal recovery as appropriate.

4.14 Third-Party License Compliance. You must not use or configure any pre-installed third-party components, models, or weights in a manner that violates their original license terms (e.g., RAIL, non-commercial, AGPL). Such violation constitutes material breach and will be handled under this section and Section 11.4.

5. Pricing, Billing, Refunds & Taxes

5.1 Balance & Prepayment. Service operates on a pure prepaid wallet; launches are blocked if the balance is insufficient.

5.2 Billing Start. The moment you click “Start” in the console, usage is metered and charges begin.

5.3 Deduction Method. Before launch, the total price for the requested duration is calculated and the full amount is deducted from the balance in one go; the minimum billing unit is 1 hour. Mid-session extension or reduction is not currently supported; if a future “top-up/extend” feature is introduced, the additional segment will be billed separately (see 5.9).

5.4 Voluntary Stop. Currently no “Stop” button exists; if one is added later, pressing it will not refund any remaining time (done to improve resource turnover).

5.5 Non-user Interruption / Force Majeure Refunds. Session progress at interruption: <50% → 100% refund; <80% → 50% refund; ≥80% → no refund. All refunds are credited to the account balance; if not auto-credited, contact human support.

5.6 Watchdog Termination. Treated as user breach; no refund unless you appeal and the audit confirms no violation, in which case CloudDock may, at its discretion, issue a balance credit equivalent to 5.5.

5.7 Refund Form. Any refunds, credits, or compensation are issued solely as non-transferable, non-withdrawable, non-interest-bearing account balance.

5.8 Balance Validity. Balance never expires.

5.9 Price Changes. Prices may change at any time; running sessions are unaffected; queued or unlaunched sessions adopt the new rate; any future “top-up” segment will be billed at the price in effect at the time of top-up.

5.10 Discount Stacking. Coupons and bespoke discounts may be combined, but not with student pricing; EDU-tier GPU groups do not participate in general coupon promotions.

5.11 Payment Methods. Currently only Zelle is accepted; credit/debit cards, bank wires, PayPal, foreign currencies, or third-party wallets are not. CloudDock reserves the right to refuse funds deemed abnormal or high-risk.

5.12 Payment Investigation / Chargebacks. While a payment-network inquiry is ongoing, service is generally maintained until resolution; if significant risk or legal compulsion exists, CloudDock may temporarily freeze instances/accounts; if the transaction is deemed malicious or abusive, permanent suspension and balance forfeiture may follow (except where prohibited by law).

5.13 Taxes. Prices are tax-exclusive; if your jurisdiction requires collection, CloudDock may remit on your behalf and itemize it on the invoice, or require you to self-remit and self-report.

5.14 Currency & Exchange. USD is the sole settlement currency; if you use a third-party exchanger to fund in another currency, exchange rates and failure risk are between you and that party.

5.15 Negative Balance. Negative balances are not permitted.

6. Education Group & Student Discount

6.1 Eligibility. K–12 and higher-education teachers, lecturers, or TAs may apply for “3060 For Education™”; student pricing is only for higher-education (college-level or above) students currently enrolled. Educational/classroom users can reserve queue-free launches.

6.2 Verification Documents. Educators: institutional email OR teacher ID/employment certificate (either one); Students: student-ID photo OR institutional email (either one).

6.3 Student Discount. Approved students receive a flat 20 % discount on non-EDU GPU groups; this discount cannot be stacked with other promotions.

6.4 EDU Group Access. Students cannot access EDU-tier groups; EDU groups are available only to verified educators and must be enabled manually by support.

6.5 Classroom Concurrency & Reservations. After submitting a complete lesson plan for approval, educators may receive a concurrency whitelist and reserved launch windows; quota, group, and window details are confirmed in writing. Resources not launched within the window are released.

6.6 Validity & Renewal. Qualification is valid for one year and must be re-verified upon expiry.

6.7 Abuse & Sanctions. Misuse, lending, forging credentials, or using discounts for resale/sub-lease results in permanent suspension, balance forfeiture, and blacklisting of the credential/email. Multiple accounts linked to the same student ID/number will all be suspended.

6.8 Display & Pricing. Once approved, the Dashboard automatically displays the exclusive pricing after login.

6.9 Data Retention. After approval we retain name, school, student ID (plaintext) and qualification expiry. Student-ID photos are deleted within 30 days of approval; qualification metadata is kept until the discount expires (to prevent abuse).

6.10 Age Alignment. Student pricing is for higher-education only; in jurisdictions where an 18+ requirement applies, service is provided only to students aged 18 or older.

6.11 Cross-Border Use. Available globally; CloudDock may refuse, restrict, or terminate access based on compliance or risk-control needs.

7. Account Ownership & Limitations

7.1 License Nature. A non-exclusive, non-transferable, revocable license is granted to you; account ownership remains with CloudDock.

7.2 Credential Security. You are solely responsible for safeguarding your credentials; any loss arising from poor custody is borne by you.

7.3 Two-Factor Authentication (2FA). Not currently offered; CloudDock reserves the right to introduce optional or mandatory 2FA in the future.

7.4 Primary Contact Identity & Recovery. The social account or contact method first used to complete a top-up or substantive support interaction is registered as the account’s primary contact identity. After identity verification, the holder may request resets or perform major actions; upon verified provision of a new contact method, the identity may be transferred or co-managed.

7.5 Termination & Balance. We may suspend or terminate accounts at any time for violations, risk-control, or legal reasons: user fault → permanent suspension and balance forfeiture possible; non-user fault → unused balance refunded. CloudDock retains the right to refuse service.

7.6 Account Deletion. Active self-deletion is not currently supported; data retention and deletion follow Section 9.

7.7 Subletting & Resale. Subletting, reselling, relicensing, or mass account operation on behalf of others is prohibited.

7.8 Payment Source & Discounts. Using the same payment source to top up multiple accounts is not inherently a violation; however, discount qualifications bind only to the individually approved person and may not be shared across accounts. Circumventing qualification limits will be handled under Sections 6.7 and 4.13.

8. Legal & Jurisdiction

8.1 Governing Law & Courts. California law applies; disputes are subject to the exclusive jurisdiction of state or federal courts located in California.

8.2 Negotiation First. The parties must attempt good-faith negotiation for 14 days before initiating litigation.

8.3 Class Action & Jury Waiver. To the extent permitted by law, both parties waive class actions and jury trials.

8.4 Severability & Survival. If any clause is invalid, the remainder remain in force; provisions on fees and taxes, privacy and monitoring, liability limitations, indemnities, governing law, and jurisdiction survive termination.

8.5 Export Controls & Sanctions. You represent and warrant that you are not under sanctions, not located in sanctioned jurisdictions, and will not resell or transfer the service to restricted parties.

8.6 Force Majeure. Delays or unavailability caused by natural disasters, power outages, regional network interruptions, cloud-provider incidents, government actions, or other force-majeure events are not CloudDock’s liability; session refunds follow Section 5.5, and SLA calculations follow Annex A.

9. Privacy & Monitoring

9.1 Data Categories. Account profile; runtime telemetry (CPU/GPU/memory/IO/process states, etc.); audit data (abnormal events only); education verification (name, school, student-ID plaintext, photo deleted after 30 days; qualification metadata retained until discount expiry).

9.2 Telemetry Retention. Used for scheduling/security and short-term caching; generally not stored long-term.

9.3 Normal Session Logs. Normal shutdowns do not retain shell/process logs or file contents (see 3.1).

9.4 Cookies/JWT. Uses JWT (localStorage); may also use cookies to enhance security and user experience.

9.5 Third-Party Providers. May use AWS, Cloudflare, CDNs, logging, and anti-fraud services; data is generally processed in facilities located in California, USA.

9.6 Data Access & Export. Self-service export is not currently offered; requests will be handled within the scope of applicable laws (CCPA/GDPR).

9.7 Post-Termination Retention. Normal data per Section 3; abnormal data retained for one year or longer if required by law; accounting and compliance records kept for statutory periods.

9.8 Minors. Service is intended for ages 16+; in jurisdictions requiring 18+, only 18+ users are served. Upon discovery of underage use, the account will be deleted and data handled in accordance with applicable law.

10. Liability, Disclaimers & Indemnity

10.1 Disclaimer. Provided “AS IS” and “AS AVAILABLE,” with no warranties of merchantability, fitness for a particular purpose, uninterrupted use, or error-free operation.

10.2 Liability Cap. CloudDock’s aggregate liability shall not exceed the total amount you actually paid to CloudDock in the three months immediately preceding the incident giving rise to liability.

10.3 Indirect Damages Waiver. CloudDock is not liable for any indirect, incidental, special, punitive, or consequential damages.

10.4 Sole Remedy. Except where mandatory law provides otherwise, your sole remedy is refund or credit of account balance (Sections 5.5/5.7 and Annex A).

10.5 User Indemnity. You agree to defend and indemnify CloudDock and its employees/partners against any third-party claims arising from your content or actions, including reasonable attorneys’ fees.

10.6 Beta/Pre-release. Experimental features or preview GPU types carry stricter disclaimers and may be modified or discontinued at any time without notice.

11. User Content & Limited License

11.1 No Ownership Transfer. CloudDock does not claim ownership of your content.

11.2 Minimal Necessary License. You grant CloudDock a worldwide, non-exclusive, royalty-free, revocable, limited license solely to: (a) provide and operate the Service; (b) maintain security and stability (including abnormal-event retention and auditing); (c) fulfill legal and compliance obligations. CloudDock may create necessary read-only copies or snapshots for these purposes.

11.3 Compliance Removal. Upon receipt of legally valid notice or a good-faith belief that content is unlawful, infringing, or violates these Terms, CloudDock may remove, restrict access, seize, or terminate the relevant content or instance.

11.4 Third-Party Licenses. Pre-installed or otherwise available third-party open-source software, models, and weights within any image or instance are governed by their respective licenses; you must read and comply with them. CloudDock merely provides technical hosting and pass-through, makes no warranties regarding third-party IP, suitability, or compliance, and assumes no liability for your violations of such licenses. If commercial licensing is required, you must obtain it directly from the rights holder.

12. Branding, Publicity & Trademark Use

Without CloudDock’s prior written consent, you may not use CloudDock’s trade names, trademarks, logos, or confusingly similar marks, nor imply endorsement, partnership, or agency. Factual statements such as “using CloudDock” are permitted provided they are not misleading. CloudDock will not use your logo for public promotion without your consent, except where required by law or regulation.

13. Service Changes & Deprecation

CloudDock may at any time modify, replace, or discontinue any feature, image, or GPU type. Material changes will be preceded by reasonable notice; urgent changes may take effect immediately. Pricing and in-progress sessions are governed by Section 5.9; compatibility of historical images, drivers, or dependencies is not guaranteed.

14. Maintenance Windows

Planned maintenance (24-hour notice when feasible) and emergency maintenance (no notice required) may occur. Downtime during maintenance is generally excluded from SLA calculations; details are governed by Annex A and Section 8.6.

15. High-Risk Use Prohibition

Planned maintenance (24-hour notice when feasible) and emergency maintenance (no notice required) may occur. Downtime during maintenance is generally excluded from SLA calculations; details are governed by Annex A and Section 8.6.

16. Government & Legal Requests

Legal Process. CloudDock will cooperate with legally valid requests (subpoenas, court orders, administrative directives) in accordance with applicable law. Except in imminent-threat-to-life situations, user information will not be disclosed. Where legally permissible, we will endeavor to notify the affected user; notification may be delayed or withheld under confidentiality orders or risk circumstances. Reasonable search, screening, or production costs may be charged to the requesting party or the relevant user.

17. Coordinated Vulnerability Disclosure

Production-Environment Security Testing Ban. Any scanning, penetration testing, or load testing in production is prohibited (see Section 4). If you discover a suspected security issue during normal use, email security@[your-domain]. Provided the report is made in good faith, does not exceed authorized access, and causes no impact, CloudDock will not pursue action against the reporter pending written confirmation; detailed guidelines will be published separately.

18. API Terms

API Terms. If an API is provided: (a) each API Key is personal, non-transferable, and revocable; (b) CloudDock may set or adjust rate limits and quotas at any time; (c) public benchmarking or circumvention of throttling is prohibited; (d) violations will result in immediate revocation and may be addressed under Section 4.13. Full details are governed by the API documentation.

19. Assignment & Successors

Assignment. You may not assign or transfer any rights or obligations under these Terms without CloudDock’s prior written consent. CloudDock may assign these Terms, without your consent, to an affiliate or successor in connection with a merger, acquisition, sale of assets, or reorganization, and will provide reasonable notice when such assignment occurs.

20. Entire Agreement; No Waiver; Notices; Headings

Entire Agreement. These Terms constitute the complete agreement between the parties regarding the Service and supersede all prior understandings. In case of conflict among orders, annexes, policies, and these Terms, the expressly agreed order of precedence shall govern. Failure to enforce any right does not constitute a waiver. Formal notices to CloudDock must be sent via officially published channels or to legal@[your-domain]; notices to you may be delivered in-app, to your registered email, or through the primary contact identity channel (see 7.4). Section headings are for convenience only and do not affect interpretation.

21. Open-Source Notices

The service includes third-party components and is subject to the corresponding licenses. For details, see Annex B.

22. Governing Language

In the event of multiple language versions of these terms, the English version shall prevail; all other language translations are provided for reference only.

⸻

Annex A — SLA & Credits

A1. Scope of Application

This appendix applies to the CloudDock production environment only during the period when you have clicked “Start” and the instance is in the “Running” state (see Section 5.2). Time spent queuing, on standby, or before launch is excluded.

A2. Monthly Availability Target

We use commercially reasonable efforts to deliver high availability and measure it on a calendar-month basis.

Monthly Availability = 1 − (Downtime Minutes ÷ Total Minutes in the Month) × 100 %.

Measurement rules are defined in Sections A3 and A4.

A3. Definition of “Downtime”

A running instance is considered “down” when it is continuously unable to be scheduled, unable to establish a session, or unable to open a job channel for ≥5 consecutive minutes due to a failure in the CloudDock infrastructure.

A4. Exclusions (not counted as Downtime)

(i) Scheduled or emergency maintenance described in Section 14.

(ii) Force majeure under Section 8.6.

(iii) Failures on the user side, including networks, configuration, images, or any third-party dependency (e.g., external registries, model downloads, third-party APIs).

(iv) Queuing caused by resource scarcity or the user’s failure to confirm within the claim window (see Section 2.3).

(v) Restrictions or suspensions arising from violation of the AUP, risk-control measures, or law-enforcement cooperation (see Sections 3, 4, and 16).

(vi) Any stop, restart, or configuration change initiated by you.

A5. Discount Trigger & Window (your defined metric)

Trigger: Monthly Availability for a given calendar month is < 80 %.

Discount: The following calendar month becomes a “discount window.” During this window, CloudDock will immediately credit 5 % of every actual charge for newly launched instances back to your account balance (applied per transaction).

Duration: The window ends when the calendar month expires; charges incurred outside the window are not eligible.

Form: Credits are issued as account balance only, non-withdrawable, non-transferable, and non-interest-bearing, in accordance with Section 5.7.

Stacking: The discount may not be combined with any other discount or rebate applied to the same spend. For the same period, it does not stack with session-level refunds under Section 5.5 (see Section A7).

A6. Consecutive Monthly Triggers

If Monthly Availability remains < 80 % for multiple consecutive months, each triggering month creates its own independent 5 % discount window in the subsequent month. These windows run separately and do not overlap or stack.

A7. No Double Compensation

For any overlapping period or the same spend, if you have already received a session-level refund or credit under Section 5.5, the discount under this Annex will not apply. Where both could apply, only the higher-value remedy is granted, once, without stacking.

A8. Claims & Reconciliation

Discounts are applied automatically. If the system fails to credit your account, submit a support ticket within 30 days after the window closes, detailing the affected period. CloudDock will verify against telemetry and audit logs and, upon confirmation, issue the balance within 15 days.

A9. Adjustments

CloudDock may modify the values and scope of this Annex as business needs require. Material changes will be announced under Section 1.1 and take effect in the next billing cycle.

⸻

Annex B – Open-Source & Third-Party Notices

(Applies to CloudDock Secure Client Container v0.254; components are pre-installed without upstream code modifications.)

General: All third-party software inside the container remains subject to its respective license. Your use of these components—including models, weights, and inference outputs—must comply with both the upstream license and the CloudDock ToS (especially Sections 4.14 and 11.4). We provide no legal advice; in case of conflict, the more restrictive terms apply.

A. Base Image & Proprietary Components

Base image: nvidia/cuda:12.1.1-cudnn8-runtime-ubuntu22.04

CUDA Toolkit / cuDNN: subject to the NVIDIA EULA and related proprietary redistribution terms.

B. Distribution & System Runtime

Ubuntu 22.04 LTS (Jammy): collective distribution containing numerous open-source packages, each under its own license (Canonical/Ubuntu trademarks apply).

Docker Engine (Linux community edition): Apache-2.0.

Python 3 runtime: PSF-2.0 (Python Software Foundation License).

FUSE (libfuse2/fuse, etc.): LGPL/GPL combination (library vs. tools).

C. Desktop / Remote Graphics Stac

Xfce / X.Org (incl. Xvfb): X.Org components are generally MIT; the Xfce ecosystem uses GPL/LGPL/BSD licenses as indicated per package.

noVNC: MPL-2.0; websockify: LGPL-3.0; x11vnc: GPL-2.0-or-later (with OpenSSL exception).

D. Browsers & Office Suit

Firefox (MozillaTeam PPA, non-snap): MPL-2.0.

LibreOffice: dual-licensed under MPL-2.0 / LGPLv3+.

E. Machine Learning / Deep Learning Frameworks & Ecosystem

PyTorch / torchvision / torchaudio: BSD-3-Clause.

xFormers: BSD-3-Clause.

ONNX: Apache-2.0; ONNX Runtime: MIT.

Hugging Face ecosystem:
– diffusers / transformers / accelerate / datasets / evaluate / peft: Apache-2.0.
– safetensors: Apache-2.0; einops: MIT.

bitsandbytes (0.39.0): MIT (some parts may carry additional terms).

TensorBoard: Apache-2.0.

PyTorch Lightning / torchmetrics: Apache-2.0.

F. Scientific Computing / Data Processing

pandas / scikit-learn / seaborn / SymPy: BSD-3-Clause.

tqdm: MPL-2.0.

G. Computer Vision / Audio-Video

OpenCV (opencv-python-headless): Apache-2.0 (older versions may be BSD-3-Clause; check your build).

Pillow: Pillow License (similar permissive license to MIT/HPND).

imageio / imageio-ffmpeg: BSD-2-Clause.

moviepy: MIT.

librosa: ISC; soundfile: BSD-3-Clause (depends on libsndfile, LGPL).

H. Web / Application Stack

Gradio / Streamlit: Apache-2.0.

FastAPI: MIT; Uvicorn: BSD-3-Clause.

Openai (Python SDK): MIT.

JupyterLab / Project Jupyter: BSD-3-Clause.

I. Pre-installed AI Applications & Extensions

AUTOMATIC1111 stable-diffusion-webui: AGPL-3.0.
– AGPL network clause reminder: If you modify it and make it interactively available over a network, you must “prominently offer” all users interacting with it remotely the complete corresponding source code of your modified version (AGPL §13). CloudDock provides an unmodified installation and assumes no obligation for your redistribution or service.

sd-webui-controlnet (ControlNet plugin): GPL-3.0.
– (Removal notice): The {hand, openpose, midas, sam} subdirectories of the ControlNet annotator have been removed from the container.

J. Other Common Dependencies

opencv-python-headless packaging scripts are typically MIT; bundled FFmpeg components may be LGPL-2.1.

nvidia-ml-py3 / gpustat: distributed under their respective open-source licenses.

invisible-watermark, sentencepiece, symphony, etc.: subject to upstream licenses; follow upstream guidance for any patent or trademark concern

Final Note:

By using CloudDock, you agree that we do not know and are not responsible for what you do in your container unless we are legally required to investigate.
We provide compute power, not judgment.