Disclaimer

1. Service provided “as is”

FARMLAND IS PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS, WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED. THIS INCLUDES BUT IS NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE.

You are responsible for evaluating whether Farmland is suitable for your specific use case. We recommend you do not rely on Farmland as the sole CI/CD path for production-critical work during beta.

2. Build correctness is your responsibility

Farmland orchestrates execution of build commands, scripts, and pipelines that you supply. The platform does not audit, lint, or modify your build inputs:

• If your build script deletes files outside the build sandbox, that's your script's behaviour — Farmland will run it as-instructed.
• If your build emits artefacts that contain secrets, those artefacts are stored as you produced them — sanitise at the source.
• If your tests are flaky, build outcomes will be flaky. Farmland does not interpret test results, only their reported exit codes.
• Variant-aware build orchestration reuses cached outputs when inputs match. Cache invalidation is your responsibility — declare your build's inputs accurately or you'll get stale results.

3. Third-party integrations

Farmland integrates with third-party version control providers (GitHub, GitLab, Bitbucket, Gitea), object storage backends, authentication providers, and notification services. Those services are operated by their respective vendors and are not part of the Farmland Service.

Their availability, terms, pricing, retention windows, and security postures are governed by the vendor — not Farmland. Farmland makes no warranty about third-party behaviour and is not responsible for outages, data loss, or terms changes on those services.

4. No professional advice

Documentation, blog posts, support emails, and conversations with Farmland staff are not professional engineering, security, or legal advice. They are informational. For decisions with regulatory or contractual impact, consult an appropriately qualified professional in your jurisdiction.

5. Beta limits

During the closed beta:

• There is no SLA. The platform may be unavailable for hours or longer with no compensation.
• There is no on-call rotation outside business hours (CET/CEST). Critical bugs are still fixed, but not at 3 AM.
• Stored data — build records, log streams, cached artefacts, attribution rollups — may be reset between releases.
• Quotas, rate limits, retention windows, and pricing may change with notice but without negotiation.

See the Beta Notes for the operational detail.

6. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, FARMLAND, ITS DIRECTORS, EMPLOYEES, AND CONTRIBUTORS SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING WITHOUT LIMITATION LOSS OF PROFITS, REVENUE, DATA, GOODWILL, OR REPUTATIONAL HARM, ARISING FROM YOUR USE OF (OR INABILITY TO USE) THE SERVICE.

See the Terms of Service for the full liability framework.

7. Versioning and your acknowledgement

Each Disclaimer revision is published with a version number (this page is version 1.0.0). Your acceptance is recorded against that exact version. When we revise the disclaimer, the console will re-prompt you on next login until you acknowledge the new version.