Terms of Use
Last updated: 2026-05-19. Scope: These terms govern use of surfaces Lesshq operates: the pileless.com landing page, the public demo Pileless™ instance, the npm registry distributions Lesshq publishes (@pileless/mcp and related packages), and the Pro waitlist. The MIT-licensed source code is governed by LICENSE, not these terms. Brand and name use is governed by TRADEMARKS.
Related: PRIVACY · TRADEMARKS · FAQ · LICENSE.
Plain-English summary
These terms are hand-written by Lesshq, not by a lawyer. If you need lawyered terms before using Lesshq surfaces in a regulated context, don't use them — self-host instead from the MIT source.
The short version:
- The code is MIT. Do what MIT says you can do.
- Lesshq-operated surfaces (landing, demo, npm) are provided as-is, no warranty.
- If you self-host, your deployment is your responsibility — your Cloudflare bill, your users, your data, your incident response.
- Your data does not pass through Lesshq when you self-host. We can't help you with it because we can't see it.
- We can change or shut down Lesshq-operated surfaces at any time.
The MIT source
The source code in this repository is licensed under the MIT License. These Terms do not modify the MIT license. If you use the source, the MIT license is the governing document.
Lesshq-operated surfaces
Lesshq operates a small set of public surfaces (see PRIVACY for the list). When you use them:
- As-is, no warranty. Lesshq-operated surfaces are provided "AS IS" without warranty of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. To the maximum extent permitted by law, Lesshq is not liable for any direct, indirect, incidental, consequential, or punitive damages arising from use of these surfaces.
- No SLA. Lesshq-operated surfaces have no uptime guarantee. The demo, landing, and waitlist may be unavailable for maintenance or any other reason.
- Demo instance is shared and ephemeral. Do not put sensitive, private, or production data into the public demo. Demo data is deleted after 30 days; see PRIVACY.
- We may change or remove surfaces. Demo, landing, waitlist, and npm distributions may change shape, location, or availability without notice.
- Acceptable use. Don't abuse Lesshq-operated surfaces. No scraping at scale, no automated load against the demo, no using the demo for production traffic, no using these surfaces to attack third parties.
Self-hosted Pileless
If you self-host Pileless on your own Cloudflare account:
- Your deployment is yours. You are responsible for provisioning, configuring, monitoring, patching, and securing it. Lesshq has no access and cannot help with anything that requires reaching into your CF account.
- Your Cloudflare bill is yours. You agree directly with Cloudflare for the resources you consume.
- Your data is yours and stays on your CF account. Lesshq is not a processor of self-hosted data; see PRIVACY.
- Your end-users are yours. Privacy notices, terms of service, breach notification, retention, and compliance obligations for your end-users are your responsibility as the operator.
- Your incident response is yours. Lesshq can support OSS bug fixes via the issue tracker, but cannot triage incidents inside your deployment.
Pro (when it ships)
Pro is not yet available. When it ships, it will have its own license agreement that supplements the MIT core. The Pro license-key check will be local — no phone-home, no telemetry; see FREE_VS_PRO.
Name and brand
The "Pileless" name, logo, and visual identity are NOT granted under the MIT license. Read TRADEMARKS before naming a product or service after Pileless.
Liability
To the maximum extent permitted by law, Lesshq's aggregate liability for any claim arising from your use of any Lesshq-operated surface is limited to the amount you have paid Lesshq for that surface in the 12 months preceding the claim. That amount is currently zero for all Lesshq-operated surfaces.
Changes
We may update these terms. Material changes will be flagged at the top of this file with a date.
Governing law
These terms are governed by the laws of the State of Missouri, United States, without regard to conflict-of-laws principles. Self-hosted deployments are unaffected — the MIT license governs the code.