Operator Agreement - development preview

UNREVIEWED DEVELOPMENT DRAFT.

DevGrail is not live yet. This document is a placeholder for testing the operator agreement flow. Accepting it records a development test action only.

Installation heartbeat

Accepting this agreement starts the installation's heartbeat: a report to the DevGrail site the installation was installed from, sent each time the DevGrail server starts and then about once a day, together with this acceptance. It cannot be turned off.

A heartbeat contains random installation, instance, run and report IDs, a sequence number, the DevGrail release, the operating system and the CPU architecture, plus entitlement_sha256 (a checksum of the plan document it received) and entitlement_applied (which part of that document applies now). It contains nothing about users, workspaces or usage. The Privacy Notice describes each field, why it is sent and how long it is kept.

As the operator, you tell the people who use this installation that it sends the heartbeat, and the usage report when its plan is billed by usage. DevGrail also shows them on its Agreements & privacy page.

Plans and limits

The installation runs on its assigned plan, including any custom terms. The plan's limits, features, end date and any plan that follows are shown in Settings -> Plan. No particular plan name, limit or price is fixed by this agreement. DevGrail may change which plan is the default for new subscriptions and for installations whose subscription ends or lapses.

When a time-limited subscription ends, a scheduled follow-up takes effect; if none is scheduled, the installation moves to the current default plan. When a subscription otherwise ends or lapses, it moves to that default. Custom terms end with the subscription unless expressly carried into another term. Existing users, workspaces and running work are not disabled, deleted or stopped because of reduced limits. The installation refuses new actions that would exceed a hard limit, including adding or enabling users, creating workspaces or starting additional stopped workspaces.

You must not circumvent the installation's plan or limits, including by altering its stored entitlement document or blocking the heartbeat to retain an earlier plan. A received plan document remains valid for 30 days. Without a newer document after that time, the installation uses the last default plan it received. A temporary outage does not stop existing work.

Plans billed by usage

A plan can be billed by usage, for example per enabled user account. On such a plan the installation sends a usage report after each heartbeat, as part of this agreement: for each completed day, the highest count of each meter the plan bills on, counted every hour. Settings -> Plan says which counts are sent and when. A plan that is not billed by usage sends no usage report.

The charge for a billing period is based on the highest daily count in it. A day without a report counts as the last day reported before it in the same period. You must not prevent, alter or falsify usage reports, for example by blocking them or editing the counts the installation keeps.

Supported releases and plan checks

DevGrail may mark a release outdated or retired, for example after a security fix. An outdated release asks administrators to upgrade. A retired release runs under the default plan's limits until upgraded; the subscription itself is not changed and existing work is not stopped. Administrators can see the release status and upgrade destination in the dashboard.

The heartbeat's entitlement checksum and applied-part fields let DevGrail check whether an installation applies the plan document it was sent. Repeated mismatches may be flagged for review, and DevGrail may contact the operator about them. A flag alone does not change a subscription or stop work. The Privacy Notice describes the purpose, proposed legal basis and retained records.

Review before launch

Reviewed terms will replace this notice before launch. This minor version is intended to require operators to accept again under the normal renewal rules. A lawyer must review these plan, usage billing, release and anti-circumvention clauses together with Privacy Notice 1.3.0, especially the purpose and legal basis of mismatch checks and of usage reports. Nothing in this draft establishes that production processing is lawful.