Customer-owned infrastructure
Enfyra Cloud is a management plane, not an infrastructure reseller. Each project runs in an infrastructure provider account you own. You keep the provider project, resources, data, usage record, and provider bill.
Provider-neutral projects
An Enfyra Cloud project selects one supported provider and maps to one provider project. Supported providers must offer an OAuth connection suitable for Enfyra management. Railway is available first; additional providers can use the same ownership boundary.
OAuth management access
You connect a provider through Enfyra Cloud and authorize access with OAuth. Enfyra stores provider credentials encrypted and uses them for requested provisioning and management operations. Disconnecting access stops Enfyra management but leaves provider resources and billing unchanged.
Railway topology
For Railway, Enfyra creates one Railway project, an always-on dedicated PostgreSQL service with a persistent database volume, and one Enfyra runtime service with embedded Redis and a persistent /app/data volume. The services communicate over Railway's private network.
The production database is not embedded in the runtime container. File uploads use a separately configured external object-storage provider such as S3, R2, or GCS.
Management and billing boundary
The USD 11.99 monthly Enfyra fee covers the management layer. Railway or another selected provider bills compute, memory, volumes, traffic, backups, and provider features directly. Enfyra does not mark up or guarantee the provider bill.
Serverless behavior
Railway Serverless can be enabled for the Enfyra runtime, while PostgreSQL stays on. Enabling or disabling Serverless requires a new deployment before it takes effect. Cold starts and connection behavior remain provider runtime characteristics.
Lifecycle and drift
Enfyra records exact provider resource identifiers and reconciles them before managed mutations. Direct provider-console changes can appear as drift and block unsafe operations. Enfyra does not silently recreate or overwrite customer-owned resources.
Stopping Enfyra renewal, disconnecting OAuth, or removing the Cloud management record does not delete provider resources. Any destructive provider-resource action is separate and requires explicit confirmation.