Terms of Service

1. This agreement

These Terms of Service (the “terms”) are an agreement between you and Durable Workflow, a sole proprietorship based in Huntsville, Alabama, USA (“Durable Workflow”, “we”, “us”), about your use of Durable Workflow Cloud (“Cloud”): its website, dashboard and API, and the managed runtimes we operate for you.

By creating an account or using Cloud, you agree to these terms and to our Privacy Policy. If you use Cloud for an organization, you agree on its behalf and confirm that you are authorized to do so. In that case, “you” means the organization.

2. The service

Cloud runs managed, isolated Durable Workflow runtimes on infrastructure we operate. Each customer runtime has its own Durable Workflow Server, database and cache. You run your own workers and application code; we operate the runtime, its persistence, backups and upgrades. Support and operations are provided by the Durable Workflow team.

Durable Workflow is open source and remains self-hostable. Cloud is the managed option. These terms apply only to Cloud. The open-source software is covered by its own licenses, and these terms do not limit your rights under them.

3. Accounts

• You must be at least 16 years old and able to enter into a binding agreement.
• Give us accurate information when you register, and keep it up to date.
• Keep your password, API keys and runtime credentials secure. You are responsible for activity that happens under your account and credentials.
• Tell us promptly at [email protected] if you believe your account or credentials have been compromised.

4. Plans, prices and billing

Our plans and prices are published on our pricing page. That page is the price list for these terms: it sets out each plan’s rates, minimums, caps and included storage.

• Payment method. You must add a payment method before you provision a runtime. Creating an account, organization or namespace definition does not by itself provision paid capacity.
• Invoicing. We invoice monthly through Stripe, our payment processor. Prices are in US dollars. Taxes are additional where applicable.
• Provisioned capacity is billable. Runtime charges start when a runtime is activated and stop when you deprovision it. A provisioned runtime is billable even when it is idle.
• No per-action charges. Workflow starts, retries, activities, timers, signals and queries are not billed separately.
• Cloud Dev. Cloud Dev is metered by the minute from activation until deprovisioning, at the hourly rate on the pricing page. A minimum charge applies to each runtime purchase in each active UTC month, and charges are capped per runtime per UTC month. Storage is a fixed included allocation.
• Charges already accrued remain payable after you deprovision a runtime or close your account.

5. Availability and service levels

Cloud Dev has no uptime service level agreement (SLA). It runs on a single host, and maintenance or recovery may interrupt service.

Single-region and multi-region high-availability plans are planned and are not yet available. Each plan with an SLA publishes its monthly availability target, how availability is measured, and its service credit tiers on the pricing page.

If a runtime on an SLA plan misses its availability target in a UTC calendar month, we automatically apply a service credit to your account. The credit is the percentage of that month’s charges for the affected runtime that the plan’s published tier sets.

• Service credits on your account are the only remedy for outages and missed SLAs. We do not give cash refunds for outages.
• Total credits for a month never exceed the amount charged for that runtime that month.
• Credits reduce future charges on your account.
• Planned maintenance is not excluded from the availability calculation.
• A single-region plan does not cover an outage of the whole region.
• The SLA covers the managed runtime. The availability of your own workers and applications is outside it.

We publish current service status on our status page.

6. Your data

Your content belongs to you. “Customer content” means the workflow inputs, outputs and history, and other data that you or your workers send to Cloud. You give us permission to host, copy, transmit and otherwise process customer content only as needed to provide Cloud to you. We do not use it for any other purpose.

You are responsible for your customer content, and for having the rights and permissions needed to process it with Cloud.

• Backups. We take encrypted backups of each runtime every six hours and keep up to 28 recovery sets.
• Workflow history is kept according to the retention setting configured for each namespace.
• Deprovisioning removes the runtime’s active data and credentials. It is not a pause. Export anything you need before you deprovision.
• After deprovisioning, we keep recovery copies for seven days, at no charge, for disaster recovery that we manage. Then we delete them. This is not a self-service restore feature.

Our Privacy Policy explains how we handle personal data about you as an account holder.

7. Acceptable use

You must not use Cloud to:

• store, process or distribute content that is illegal, or that infringes anyone else’s rights;
• abuse, harass, defraud or harm others, or send spam;
• attack, probe or disrupt Cloud, other customers, or any other system or network, including attempts to break runtime isolation or to get around authentication, limits or billing;
• mine cryptocurrency; or
• resell Cloud, or access to it, without our written permission. Running your own applications and services on Cloud is fine.

8. Suspension

We may suspend or limit your access to Cloud, or to a specific runtime, if:

• a payment fails or an invoice is overdue;
• you break the acceptable use rules; or
• your use creates a security risk to Cloud, other customers or anyone else.

Where practical, we will contact you first and give you a chance to fix the problem.

9. Ending your use of Cloud

You can stop using Cloud at any time. Deprovision your runtimes to stop runtime charges, then ask us to close your account by emailing [email protected] from the address on your account.

We may end these terms and close your account if you seriously breach them and do not fix the breach after we tell you about it, or immediately if the breach cannot be fixed.

When a runtime is deprovisioned, its data is handled as described in Your data.

10. Changes to these terms

We may update these terms. When we do, we will publish the new version on this page with a new version label and effective date. We will notify account holders by email before a material change takes effect. The pricing page is part of these terms, so a price increase for a plan you use follows the same notice.

If you continue to use Cloud after a change takes effect, the new terms apply. If you do not agree to them, you can stop using Cloud as described in Ending your use of Cloud.

11. Warranty disclaimer

Except for the service level commitments stated in these terms, Cloud is provided “as is” and “as available”. To the fullest extent the law allows, we disclaim all other warranties, express or implied, including warranties of merchantability, fitness for a particular purpose and non-infringement. We do not promise that Cloud will be uninterrupted or error-free.

12. Limitation of liability

To the fullest extent the law allows:

• we are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits or revenue, arising from or related to Cloud or these terms; and
• our total liability for all claims arising from or related to Cloud or these terms is limited to the fees you paid us for Cloud in the 12 months before the claim arose.

Nothing in these terms limits liability that cannot be limited under applicable law.

13. Indemnity

You will defend and indemnify us against third-party claims, and the resulting losses and reasonable costs, that arise from your customer content or from your use of Cloud in breach of these terms or the law.

14. Governing law

These terms are governed by the laws of the State of Alabama, USA, without regard to conflict-of-law rules. Disputes will be resolved in the state or federal courts located in Madison County, Alabama. This does not remove any rights you have as a consumer under the law of the place where you live.

15. General

• These terms, the pricing page and the Privacy Policy are the whole agreement between you and us about Cloud, unless we sign a separate written agreement with you.
• If any part of these terms cannot be enforced, the rest remains in effect.
• If we do not enforce a provision, that is not a waiver of our right to do so later.
• You may not transfer these terms to someone else without our written consent.
• We send notices to the email address on your account. Send notices to us at [email protected].

16. Contact