Enfyra Cloud

Enfyra Cloud Terms and Conditions

Terms for using Enfyra Cloud, including accounts, billing, resource usage, support scope, acceptable use, data, security, suspension, and availability.

Effective May 18, 2026 Version 1.0

Effective date: May 18, 2026

These Enfyra Cloud Terms describe the rules that apply when you create an account, create a Cloud project, pay for a Cloud plan, or otherwise use Enfyra Cloud. If you do not agree to these Terms, you should not use Enfyra Cloud.

1. Service Description

Enfyra Cloud provides managed hosting, provisioning, and runtime infrastructure for isolated Enfyra instances. Each Cloud project is intended to run as its own Enfyra instance with its own runtime boundary, database provisioning path, and project-level access model.

Enfyra is responsible for operating the Cloud infrastructure, provisioning pipeline, platform-level availability, and managed runtime services within the limits of the selected plan. You remain responsible for the applications, data models, users, APIs, workflows, scripts, packages, integrations, and business logic that you create or run inside your Enfyra instance.

2. Accounts and Access

  • You must provide accurate account and billing information.
  • You are responsible for keeping your account credentials, admin credentials, API tokens, secrets, and project access secure.
  • You must promptly notify Enfyra if you believe your account, project, or credentials have been compromised.
  • Enfyra may suspend access when an account appears compromised, fraudulent, abusive, unpaid, or harmful to the platform.

3. Plans, Billing, and Payment

Cloud plans are billed according to the plan and billing cycle shown at the time you create or renew a subscription. Prices may exclude taxes, payment processing fees, currency conversion costs, or other charges unless explicitly stated.

A Cloud project may require a valid payment order before provisioning begins. For paid plans, Enfyra Cloud will only provision or upgrade the project after payment is confirmed by the payment provider or by Enfyra's trusted billing flow.

If a payment fails, is reversed, is disputed, or remains unpaid, Enfyra may pause provisioning, suspend the project, restrict access, or cancel the subscription until the issue is resolved.

4. Resource Usage and No Monthly Request Quota

Unless a plan explicitly says otherwise, Enfyra Cloud does not impose a fixed monthly API request quota. You may use your Enfyra instance within the CPU, memory, network, storage, and runtime limits of the selected plan.

To protect platform stability, Enfyra may apply edge-level rate limits, traffic filtering, abuse detection, temporary throttling, request blocking, or suspension when usage threatens the availability, security, or reliability of Enfyra Cloud, the host pool, another tenant, or the network.

Shared CPU plans use shared infrastructure. Performance can vary based on workload behavior, platform maintenance, host conditions, and other fair-use factors. Shared CPU plans are not a guarantee of dedicated CPU ownership unless the plan or a written agreement explicitly states otherwise.

5. Acceptable Use

You must not use Enfyra Cloud to operate, host, support, or facilitate:

  • spam, phishing, malware, credential theft, botnets, or unauthorized scanning;
  • denial-of-service attacks, stress testing against third parties, or traffic abuse;
  • cryptocurrency mining or similar workloads that consume excessive shared resources;
  • illegal content, illegal transactions, or content that violates applicable rights or laws;
  • attempts to bypass authentication, authorization, sandboxing, rate limits, resource guards, or tenant isolation;
  • unauthorized access to another customer's data, host, database, network, or runtime;
  • bulk scraping, credential stuffing, or automated abuse of third-party services.

Enfyra may take immediate action, including throttling, blocking, suspension, or termination, when usage creates security risk, legal risk, operational risk, or service degradation.

6. Customer Data

You retain ownership of the data, content, schema, records, files, code, workflows, and configuration you create or upload into your Enfyra Cloud project. Enfyra does not claim ownership over your customer data.

Enfyra may process customer data as necessary to provide, secure, monitor, debug, back up, maintain, improve, or support Enfyra Cloud. You are responsible for ensuring that you have the necessary rights, permissions, notices, and legal basis to store and process data inside Enfyra Cloud.

7. Backups, Retention, and Deletion

Enfyra may provide backups, snapshots, exports, or recovery features depending on the plan and operational state of the platform. Unless a specific plan or agreement states otherwise, backups are a best-effort operational safeguard and are not a substitute for your own export or retention process.

After cancellation, suspension, termination, or non-payment, Enfyra may retain project data for a limited period to support recovery, billing, legal, security, or operational needs. After that period, Enfyra may delete project data, backups, logs, credentials, and related resources.

8. Security

Enfyra uses reasonable technical and operational measures to protect Cloud infrastructure and tenant isolation. You are responsible for securing your own application logic, users, roles, permissions, API keys, webhook secrets, packages, scripts, and integrations.

You must not attempt to access, probe, modify, or interfere with infrastructure, containers, databases, networks, tenants, or control-plane resources that are not assigned to your account or project.

9. Support Scope

Basic Cloud support covers Enfyra Cloud infrastructure, provisioning failures, billing issues, payment confirmation issues, project availability caused by Enfyra Cloud infrastructure, and platform-level incidents.

Basic Cloud support does not include custom application development, schema design, data modeling, customer-created workflow debugging, business logic debugging, third-party integration work, performance tuning of customer-created workloads, data migration, or custom architecture review.

Additional support, priority support, implementation help, migration help, or custom development may require a separate paid support agreement or a plan that explicitly includes those services.

10. Availability, Maintenance, and Changes

Enfyra will make reasonable efforts to keep Enfyra Cloud available and reliable. Unless a plan or written agreement includes a specific service level agreement, availability is provided on a commercially reasonable, best-effort basis.

Enfyra may perform maintenance, upgrades, migrations, security patches, provider changes, or operational changes. Enfyra may change, add, remove, suspend, or deprecate features when needed for security, reliability, product direction, or legal compliance.

11. Third-Party Providers

Enfyra Cloud may rely on third-party providers for infrastructure, payment processing, email delivery, networking, storage, observability, or other operational services. Incidents, limitations, outages, or policy changes from those providers may affect Enfyra Cloud.

Payment details may be processed by a payment provider. Enfyra does not need to store full card details when payment is handled by the payment provider.

12. Suspension and Termination

You may cancel your subscription according to the cancellation flow provided by Enfyra or the payment provider. Enfyra may suspend or terminate a project or account for non-payment, abuse, security risk, legal risk, violation of these Terms, or usage that threatens platform stability.

Suspension may restrict API access, admin access, provisioning, upgrades, backups, or other Cloud operations. Termination may result in deletion of Cloud resources and related project data after any applicable retention period.

13. Refunds

Refunds are handled case by case unless a separate refund policy applies. Enfyra may decline refunds for accounts suspended or terminated for abuse, fraud, chargeback activity, policy violations, or usage that created material operational cost or risk.

14. Disclaimers

Enfyra Cloud is provided without warranties of uninterrupted operation, error-free behavior, or fitness for every possible workload. You are responsible for determining whether Enfyra Cloud is suitable for your use case, compliance obligations, uptime expectations, and risk profile.

15. Limitation of Liability

To the maximum extent permitted by law, Enfyra will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, including loss of profits, revenue, goodwill, data, or business opportunity. Enfyra's aggregate liability for Cloud services is limited to the amount you paid for the affected Cloud service during the three months before the event giving rise to the claim, unless applicable law requires otherwise.

16. Updates to These Terms

Enfyra may update these Terms from time to time. When changes are material, Enfyra will make reasonable efforts to provide notice through the website, product, email, billing flow, or another appropriate channel. Continued use of Enfyra Cloud after an update means you accept the updated Terms.

17. Contact

For Cloud support, billing questions, or legal notices, contact Enfyra through the support or contact channels published on the Enfyra website.