Terms and Conditions

1. Acceptance of Terms #

By creating an account or provisioning an instance within Orchesty Cloud ("the Service"), you agree to be bound by these Terms and Conditions. The Service is provided by Orchesty Solutions s.r.o., with its registered office at Chládkova 898/2, Žabovřesky, 616 00 Brno, Czech Republic (Company ID: 02063450, VAT ID: CZ02063450).

2. Service Structure and Provisioning #

• Hierarchy: The Service is structured into Organizations, which can manage one or more Cloud Instances.
• Provisioning: Creating an instance triggers the automated allocation of dedicated infrastructure resources.
• Service Tiers: Detailed specifications, including Rate Limiting (calls per second/minute) for each tier, are defined in the current Pricing Table. Exceeding these limits may result in temporary throttling of requests to maintain platform stability.

3. Free Trial (30 Days) #

• Trial Period: The Free Trial lasts for 30 days on Pro Level 1 capacity with all premium features (e.g., Trace AI, Operations Suite) enabled. The Trial is offered as a separate, zero-cost plan distinct from any paid plan.
• No Payment Method Required: No payment method or subscription is required to start the Trial. No charges will occur during the 30-day Trial period. To prevent platform abuse, sign-ups are protected by automated mechanisms (e.g., bot challenge, e-mail hygiene checks, per-IP rate limiting).
• Trial Expiration: When the Trial period ends, the instance will be automatically stopped (no data is deleted by the expiration itself). No automatic conversion to a paid subscription takes place. To continue using the Service, you must select and configure a paid plan from the dashboard; a paid subscription is created via Stripe only at that moment.

4. Billing and Payments #

• Subscription: Fees are billed in advance. All prices are exclusive of VAT unless stated otherwise.
• Usage-based fees: Extra Topology Slots or Storage beyond the plan's inclusion are billed according to the current Pricing Table.
• Add-ons: Optional features are billed as fixed monthly surcharges as part of your active subscription.

5. Log Retention and Storage Capacity #

• Maximum Retention: Each plan defines a maximum log retention period (e.g., 30 days).
• Storage Dependency: The actual availability of logs is subject to your purchased Storage Hub capacity. If the log volume exceeds the allocated space, the system will delete the oldest logs to make room for new entries, regardless of the maximum retention period.
• Monitoring: Users are responsible for monitoring storage levels via the Dashboard and upgrading capacity if their log volume requires it.

6. Instance Downgrade and Technical Constraints #

• Storage Persistence: Due to infrastructure architecture, storage capacity cannot be downgraded on an existing instance.
• Migration: To move to a lower storage tier or a Starter plan, a new instance must be created and configurations migrated manually. The old instance must be deleted by the user to stop further billing.

7. Support Services #

• Starter Plan: Support is provided via community documentation and the public Orchesty Discord channel.
• PRO Plans (L1, L2, L3): Users are entitled to email support accessible exclusively via the support form within their account dashboard. Support is provided on a "best-effort" basis.

8. Data Privacy and User Responsibility #

• Zero-Logging Policy: The Orchesty infrastructure does not automatically log or store the content of transferred data (payloads).
• User Configuration: Any sensitive data or personal information (PII) included in the logs is the sole result of the user's explicit configuration within their integration topologies.
• Compliance: Users are exclusively responsible for ensuring their logging configurations comply with relevant data protection laws (e.g., GDPR).

If you use the Service to process personal data of third parties (data subjects), our Data Processing Agreement (DPA) applies to you and forms an integral part of these Terms.

9. Intellectual Property and Software License #

• Engine License: The software engine is licensed under the Elastic License 2.0 (ELv2). These Terms grant you the right to use the software as a managed service.
• Ownership: Orchesty owns the Service and underlying engine. You own all rights to the specific integration logic (Topologies) created by you within the Service.
• Restrictions: You shall not: (a) provide the Service as a competing managed service to third parties; (b) attempt to reverse engineer the engine; (c) circumvent any license keys or technical limitations.

10. Indemnification #

You agree to defend and indemnify Orchesty against any claims, damages, or losses arising from your use of the Service that violates these Terms or infringes upon the rights of any third party (e.g., data breaches in third-party systems caused by your configuration).

11. Limitation of Liability #

Orchesty Cloud is provided "as is". We are not liable for:

• Any issues caused by changes or outages in third-party APIs (e.g., Shopify, ERP systems).
• Data loss due to insufficient storage allocation or misconfiguration of integrations by the user.
• Indirect or consequential damages resulting from service interruptions.

12. Technical Resource Constraints #

• Message Integrity (In-flight): Each plan has a defined limit for "Message Integrity" (maximum number of concurrent messages processed by the instance). If this limit is exceeded, the Service will prioritize platform stability and will automatically discard incoming messages until the number of in-flight messages drops below the threshold.
• Storage Hub Exhaustion: When the allocated Storage Hub capacity is reached, the Service will stop accepting new data or logs. Users are responsible for monitoring capacity and scaling their plan to prevent data loss.
• Failure Record Deduplication: To preserve the readability of the failed-message inbox and protect platform storage, the Service automatically deduplicates identical failures within a single process run. When the same step of a single process produces repeated failures with the same error, only an initial sample is persisted to the failed-message inbox; further identical duplicates are acknowledged off the queue without being stored. A single notification is sent the moment the deduplication is activated, so the User is informed of the runaway condition. The User is responsible for addressing the root cause (typically a downstream service outage) and re-running the affected process; the persisted sample is sufficient for diagnosis. The deduplication threshold is platform-wide today and may be adjusted per plan in future releases.
• Single Object Limit: To ensure consistent performance, the maximum size of a single data object (payload) processed by the Bridge component is strictly limited to 5 MB. Objects exceeding this limit will result in an execution error.
• Topology Configuration Responsibility: Reaching the Single Object Limit is conditional on the User keeping the topology configured according to the documented best practices — in particular, the prefetch of any node handling large payloads must be set to 1, and large objects must be routed only through nodes that need them (typically by passing them as external storage references rather than embedding them in the payload of every step). Misconfigured topologies handling large payloads may overload the topology's control component and cause it to fail. The User is solely responsible for the correctness of their topology configuration. Orchesty shall not be liable for outages, restarts, or data loss caused by topologies that do not follow the documented guidelines.
• No Liability for Data Loss: Orchesty shall not be liable for any data loss resulting from the automated discarding of messages due to (i) the User exceeding their plan's defined limits (In-flight messages or Storage Hub capacity), (ii) the automated deduplication of identical failures within a single process run as described in "Failure Record Deduplication" above, or (iii) User-side topology misconfiguration as described above.

13. Modifications to Terms and Service #

Orchesty reserves the right to modify Service specifications and these Terms. Users will be notified of material changes (such as significant Rate Limit reductions) via email or dashboard notification at least 30 days in advance.

14. Jurisdiction #

These Terms are governed by and construed in accordance with the laws of the Czech Republic. Any disputes shall be subject to the exclusive jurisdiction of the courts of the Czech Republic.