Beta Notes

1. What “closed beta” means

Farmland is operated as a closed beta. The platform is functional and actively used, but features, APIs, retention windows, and operating limits may change. New tenants are admitted by Farmland on a rolling basis; signing up does not guarantee admission, and admission can be revoked if the platform is misused.

2. Admin approval before use

When you sign up, your tenant is created in a pending_approval state. You can sign in, but the dashboard is gated until a Farmland operator approves the tenant. Approval may take a business day or longer, especially around major releases. Rejected applications are recorded with a reason and the user account stays inactive.

3. Data may be reset between releases

We may reset the platform's data — tenant state, build history, cached artefacts, attribution rollups — between beta releases when a schema change or correctness bug demands it. We try to avoid this and communicate planned resets in advance, but you must not use Farmland to store anything you cannot reproduce. The platform is not a backup target.

Source code repositories you point Farmland at are not at risk; Farmland reads from your VCS and never writes back without an explicit operator action you initiated.

4. Build, log and artefact retention

Build records, log streams, and stored artefacts have a retention window that depends on your tenant's tier. The window is short by default (days, not months). Old data may be purged without per-tenant warning. If you need a permanent record of a particular build, export it before the retention window closes — there is no undo.

5. Support hours and availability

Farmland does not run a 24/7 on-call rotation during beta. Outages are investigated and fixed during European business hours (CET/CEST). There is no SLA, no uptime guarantee, no compensation for downtime. If your team's production CI depends on Farmland being up, the beta is not the right venue — talk to us about a dedicated arrangement instead.

6. Acceptable use

• Use Farmland for software builds, tests, and pipeline experiments that you have the right to run.
• Don't use Farmland for cryptocurrency mining, password cracking, traffic generation against third parties, or any other workload whose primary purpose is computational abuse.
• Don't upload data subject to regulated handling (PHI, cardholder data, classified material) — beta isn't certified for any of it.
• Respect the rate limits and tenant quotas. We may pause or revoke tenants that consume resources in a way that affects other beta users.

7. Feedback, issues, security

For beta-facing issues, ideas, and bug reports: beta@farmland.rocks or our public GitHub issues.

For security disclosures, please use security@farmland.rocks and not GitHub. We will respond within five business days.

8. Versioning and your acknowledgement

Each Beta Notes 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 notes, the console will re-prompt you on next login until you acknowledge the new version. You can review your current acceptances by logging in and reading this page; an in-product audit view is on the roadmap.