1. Service and roles
Enfyra Cloud is a management plane for Enfyra projects deployed into infrastructure accounts you own. Enfyra provides the console, provider integration, provisioning workflow, deployments, updates, credentials, domains, backup controls, and runtime operations. Enfyra does not sell or include compute in the management subscription.
Railway is the first supported provider. Enfyra may add other providers that support an appropriate OAuth connection. The provider you select supplies the infrastructure and bills you directly under its own terms.
2. Accounts and provider connections
You must provide accurate account and billing information and protect your Cloud, provider, administrator, and application credentials. You authorize Enfyra to access the selected provider account through OAuth only for the management actions you request or enable.
You may revoke or disconnect provider access. Doing so stops Enfyra from managing affected resources but does not stop, delete, or cancel those resources or their provider billing.
3. Project and resource ownership
One Enfyra Cloud project maps to one project in the selected provider. Provider services, volumes, databases, network usage, and related data remain in your provider account. Removing an Enfyra management record, stopping renewal, losing entitlement, or deleting your Enfyra account does not authorize Enfyra to silently delete provider resources.
A destructive provider-resource operation is separate, requires explicit confirmation, and is subject to the provider's behavior. You remain responsible for checking the provider console and charges.
4. Management subscription
The standard Enfyra Cloud management subscription is USD 11.99 per project per month unless a written agreement states otherwise. PayPal processes recurring subscription payments. Enfyra does not add a PayPal surcharge.
The subscription covers the Enfyra management layer. It does not include provider compute, memory, storage, network traffic, backups, taxes, currency conversion, or paid provider features.
5. Provider billing
Your provider bills infrastructure usage directly to your provider account. Provider estimates are not guaranteed invoices, and provider prices, quotas, availability, regions, and account requirements may change independently of Enfyra.
You are responsible for maintaining a provider account that can create and run the selected resources and for paying all provider charges, including charges that continue after Enfyra management ends.
6. Setup and provisioning
Project details and provider configuration are completed before payment. Provisioning begins only after the management subscription is active. Provisioning depends on provider authorization, workspace access, billing status, quotas, regions, APIs, and service availability.
Enfyra may pause an unsafe operation when reconciliation finds missing or changed services, volumes, domains, images, regions, or mappings. Enfyra does not automatically overwrite or recreate customer-owned resources to hide provider drift.
7. Data, database, and file storage
You retain ownership of project data, schemas, records, files, code, flows, and configuration. You are responsible for the legality, accuracy, security, retention, backup, and privacy notices for data processed by your application.
Railway projects use a dedicated external PostgreSQL service and volume; the production database is not embedded in the Enfyra container. File uploads require separately configured external object storage such as Amazon S3, Cloudflare R2, Google Cloud Storage, or a supported S3-compatible service.
8. Serverless and deployments
Provider settings can require a deployment before they take effect. On Railway, enabling or disabling Serverless requires a new deployment. Sleeping services may have cold starts, and open connections or background work may prevent sleep. PostgreSQL remains always on.
9. Acceptable use and security
You must not use Enfyra Cloud to facilitate illegal activity, malware, phishing, credential theft, unauthorized access or scanning, denial-of-service attacks, provider abuse, cryptocurrency mining that violates provider rules, or attempts to bypass authentication, authorization, rate limits, sandboxing, or project isolation.
Enfyra may restrict management access when necessary to address abuse, fraud, non-payment, legal risk, compromised credentials, or a material threat to Enfyra, a provider, another customer, or a third party.
10. Support and availability
Standard support covers Enfyra platform issues, the Cloud management plane, supported provisioning workflows, verified Enfyra-managed operations, and Enfyra subscription records. It does not include provider billing disputes, provider outages, custom application development, schema design, customer code, data migration, or third-party integrations unless separately agreed.
Enfyra and provider services are offered on a commercially reasonable-efforts basis unless a written agreement provides a specific service level. Provider outages, limits, policy changes, suspensions, and API changes may affect service.
11. Stop renewal and termination
You may stop subscription renewal. Renewal stops at the next billing date, and management access continues through the paid period unless access is restricted for abuse, fraud, security, legal, or payment-dispute reasons.
When entitlement ends, Enfyra-managed operations are disabled. Provider resources remain in your account and can continue running and accruing provider charges.
12. No voluntary refunds
Paid subscription periods are final and are not voluntarily refunded, credited, or prorated for unused time, change of mind, provider incidents, customer configuration, cold starts, or early cancellation. Exceptions apply only where required by applicable law or a mandatory payment-network correction. See the Cancellation and No-Refund Policy for details.
13. Disclaimers and limitation of liability
Enfyra Cloud is provided without a guarantee that every provider, region, feature, deployment, or workload will be continuously available or suitable for every purpose. You are responsible for evaluating compliance, recovery, availability, and risk requirements.
To the maximum extent permitted by law, Enfyra is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, including lost profit, revenue, goodwill, data, or business opportunity. Enfyra's aggregate liability for the affected management service is limited to the management fees paid for that project during the three months before the event, unless applicable law requires otherwise.
14. Changes and contact
Enfyra may update these Terms as the product, providers, payment processing, or legal requirements change. Material updates will be communicated through a reasonable channel. For Cloud, billing, or legal questions, contact Enfyra through the support channels published on the Enfyra website.