Product Terms

1. Scope

These Product Terms describe what you receive under a Subscription, the limits on your license, and what happens when a Subscription ends. They apply to every Subscription unless a signed agreement between you and us expressly overrides them.

2. Products covered

The Software consists of the following components, all of which are licensed together as a single Subscription:

• fDeploy Server — the central web application and Windows service that stores projects, releases, deployment targets, audit logs, and user accounts. Includes the web Dashboard for end-user access.
• fDeploy Agent — the Windows service installed on each deployment target that performs deployments on behalf of fDeploy Server. You may install the Agent on as many deployment targets as your Subscription allows (see Section 3).

fDeploy is designed to be installed and operated on infrastructure that you control. We do not host fDeploy for you and we do not offer a software-as-a-service edition.

3. License metric and tiers

3.1 License metric

fDeploy is licensed per fDeploy Server instance. Fees do not depend on the number of projects, deployment targets, or users. There are no add-ons and no usage-based charges of any kind.

3.2 Tiers

fDeploy is offered in the tiers below. The applicable tier is set out in your Order Confirmation; for the Community tier, no Order Confirmation is issued.

• Community — free of charge, with no time limit and no feature restrictions. Unlimited projects, unlimited deployment targets, and unlimited users on one fDeploy Server instance. Community is the same build as Professional; the difference is the support commitment (Section 5) and eligibility (Section 3.9). No registration, order, or license request is required to obtain or use the Community tier.
• Professional — paid. Unlimited projects, unlimited deployment targets, and unlimited users on one fDeploy Server instance.
• Academic — paid, available to accredited academic institutions and registered non-profit organisations. Entitlements are identical to Professional; the support commitment differs (see Section 5). We verify eligibility by institutional email domain where possible, and may otherwise ask you for reasonable evidence of eligibility before issuing or renewing an Academic license.
• Enterprise — paid, by separate written agreement. Covers multiple fDeploy Server instances, a contractual service level agreement, and source code escrow. Where an Enterprise agreement conflicts with these Product Terms, that agreement prevails.

3.3 Server instance

Each license entitles you to operate one (1) production fDeploy Server instance. You may operate additional non-production instances (such as for staging, disaster recovery, or development) without additional fees, provided that they are not used to perform deployments to live production targets.

3.4 Deployment targets

A "deployment target" is a Windows machine on which the fDeploy Agent is installed and registered with your fDeploy Server instance. You may install and register the fDeploy Agent on any number of deployment targets at no additional charge, on every tier including Community. We do not meter, cap, or invoice for deployment targets.

3.5 Projects

A "project" is a logical unit configured in fDeploy that groups together releases, processes, and deployment targets for a single piece of software being deployed. No tier, including Community, limits the number of projects.

3.6 Users

All tiers permit unlimited named users. You are responsible for ensuring that each user accesses the Software under their own account and complies with the Agreement.

3.7 Perpetual licenses and maintenance

Professional and Academic are available either as an annual subscription or as a perpetual license. A perpetual license is a one-time fee that grants you the right to use the version of the Software current at the date of purchase, and every version we release during any period for which you hold maintenance, in perpetuity. A perpetual license does not expire and is not revoked if you stop purchasing maintenance.

Annual maintenance is optional and is charged at the published rate (currently twenty per cent (20%) of the perpetual license fee per year). While maintenance is active you receive updates, bug fixes, security patches, new features, and the technical support applicable to your tier under Section 5. If maintenance lapses, you retain the right to keep using every version released up to the date it lapsed, indefinitely. You may reinstate maintenance later; we may require payment of the lapsed period.

The Software does not contact us to validate a license and contains no mechanism by which we can remotely disable a perpetual license.

3.8 Community tier eligibility

The Community tier is free to use in production, for commercial purposes, by any organisation whose Annual Revenue is less than USD 1,000,000 (or EUR 900,000, or the equivalent in your functional currency at the average rate for the period).

"Annual Revenue" means your total gross revenue from all sources for your most recently completed fiscal year, aggregated across you and all of your Affiliates. "Affiliate" means any entity that controls, is controlled by, or is under common control with you, where control means direct or indirect ownership of more than fifty per cent (50%) of the voting interests. For a public-sector body, charity, or other organisation that does not report revenue in the ordinary sense, Annual Revenue means your total annual operating budget.

The following uses are free under the Community tier regardless of Annual Revenue:

• use by a natural person for their own personal, non-commercial purposes;
• use by a student, educator, or accredited educational institution for teaching, learning, or academic research;
• non-production use, including evaluation, proof of concept, development, testing, and training environments, provided no deployment is made to a live production target; and
• use in the development of software distributed publicly under an OSI-approved open-source license, where that use is not part of a commercial product or service.

3.9 Compliance and self-declaration

Eligibility for the Community tier is self-declared. The Software does not measure your revenue, does not transmit any information to us, and does not restrict functionality on the basis of this Section. There is no audit right and we will not ask you for financial records.

If your Annual Revenue reaches or exceeds the threshold in Section 3.8, you must obtain a Professional, Academic, or Enterprise license within ninety (90) days of the end of the fiscal year in which that happened, or stop using the Software for purposes other than those listed as always free. Continuing commercial production use beyond that period without a paid license is a breach of the Agreement.

We may change the threshold in Section 3.8 in future versions of these Product Terms. Any increase applies immediately; any decrease takes effect no earlier than twelve (12) months after we publish it, so that an organisation which relied on the previous threshold has a full fiscal year to respond.

4. Updates, bug fixes, and new features

During each License Term, your Subscription includes all updates, bug fixes, security patches, and new features that we release for the licensed components, at no additional cost. Updates are made available through our published release channels. We do not guarantee any particular release cadence and we do not guarantee that any specific feature will be developed or maintained.

We may discontinue or change features of the Software in any release. Where reasonably practicable, we will give advance notice through the Documentation or release notes for material removals or breaking changes.

5. Technical support

Support is provided by email at [email protected].

• Community tier: community support only — no commitment from us. Issues may be raised via the public documentation channels.
• Professional tier: business-hours email support, Monday to Friday from 09:00 to 17:00 Central European Time / Central European Summer Time, excluding Swedish public holidays. We aim to acknowledge new requests within one (1) business day. Response times are targets, not guaranteed service levels.
• Academic tier: asynchronous email support. We aim to respond within five (5) business days. Response times are targets, not guaranteed service levels.

Support covers questions about the use of the Software, diagnosis and resolution of defects, and assistance with upgrades. It does not cover (a) consulting, training, or bespoke development, (b) issues caused by your infrastructure, network, or third-party software, (c) issues caused by modifications to the Software not made by us, or (d) issues in versions of the Software that we have marked as no longer supported.

We support the latest released version of the Software and the immediately preceding major version. Earlier versions are no longer supported. We will give at least ninety (90) days' advance notice in the release notes before retiring support for a major version.

6. Acceptable use

You will not use the Software to:

• deploy software that you know, or ought reasonably to know, contains malware, ransomware, or any other code intended to disrupt, damage, or gain unauthorised access to a system;
• violate the intellectual property rights, privacy, or other rights of any person;
• violate applicable law, including export-control, sanctions, and data-protection law;
• attempt to interfere with the integrity or security of the Software, or to circumvent its license-enforcement mechanisms.

7. What happens when a License Term ends

This Section applies to annual subscriptions. It does not apply to perpetual licenses: a perpetual license has no License Term and does not end, and lapsed maintenance on a perpetual license has the consequences set out in Section 3.7 rather than those below. The Community tier likewise has no License Term.

A subscription is licensed for a fixed License Term. When a License Term ends without renewal, the Software does not stop working entirely. Instead:

• Deployment functionality is disabled. You will no longer be able to use fDeploy to deploy releases of your software to deployment targets. The fDeploy Agent on each target will remain installed but will not accept new deployment instructions from your fDeploy Server instance.
• Read access remains available. You can continue to log in to fDeploy Server, browse projects, view past releases and audit logs, manage users, and export your data. Most non-deployment features of the Software remain available.
• No new updates. You will not receive new updates, bug fixes, security patches, or new features after the License Term ends. You may continue to use the version of the Software you have installed for as long as you wish, subject to the surviving provisions of the Agreement.
• Renewal restores deployment. If you place a new Order to renew your Subscription, deployment functionality is restored and the new License Term applies retroactively from the day after the previous License Term ended.

If we terminate the Agreement for your material breach, all of your rights to use the Software end on the effective date of termination, and you must promptly stop using and uninstall the Software.

8. Third-party services configured by you

fDeploy lets you configure connections to third-party services that you choose, including an SMTP server for outbound email, source-control systems, package repositories, secret stores, and identity providers. You are solely responsible for those third-party services, for your accounts and credentials with them, and for ensuring that your use of them complies with their terms. We are not a party to your relationship with those providers and we are not your data processor in respect of data exchanged with them.

9. Open-source components

fDeploy is built using open-source components. The Software is provided to you under the Agreement; the open-source components are provided to you under their respective licenses, which are listed in the Documentation and in the Software itself. To the extent that any open-source license grants you broader rights than the Agreement does, those rights apply to that component.

10. Beta and preview features

From time to time we may make features available as "beta", "preview", "experimental", or similar. Those features are provided as-is, without warranty of any kind, may change or be removed without notice, and are not covered by the Section 5 support commitments or the Section 10.2 software warranty in the General Terms. We are not liable for any damages arising from your use of beta or preview features beyond what is required by mandatory law.

11. Changes to these Product Terms

We may modify these Product Terms in accordance with Section 14.4 of the General Terms. Changes that materially reduce the scope of your Subscription will not take effect during a License Term that is already in progress.