How can we help you?
Find answers to common questions about Thrinacia. Can’t find what you’re looking for? Contact our support team.
Can Fabric data be copied, exported, or migrated to another system?
Yes. Customers can copy, export, transfer, and migrate their Fabric data to another system, service, or environment.
Fabric data can be accessed through the Web UI, documented REST APIs, webhooks, and project-specific migration workflows as needed.
If a customer is moving to a different application, infrastructure provider, or internal system, Thrinacia can also assist with migration planning and data transfer requirements.
Who owns Fabric, customer data, frontend modifications, and integrations?
Thrinacia retains ownership of the Fabric codebase, backend implementation, supplied reference frontend, updates, releases, and backend development performed by Thrinacia.
Customers own their data, branding, customer materials, and independently developed frontend modifications, replacement frontends, and integration code.
Modifying the supplied frontend does not transfer ownership of Thrinacia’s original reference code.
What happens when a Fabric Enterprise licence expires?
When an Enterprise licence expires, the customer’s right to continue deploying and operating licensed Fabric backend runtime containers depends on the terms of the applicable agreement and any renewal or transition arrangements in place with Thrinacia.
Fabric Enterprise does not provide perpetual, one-time, lifetime, or permanent backend deployment rights.
Customers continue to own their data, branding, customer materials, and independently developed frontend or integration code.
Is Fabric Enterprise licensing annual?
Yes. Fabric Enterprise licensing is provided on an annual basis.
The active licence term governs the right to deploy approved backend runtime containers, receive supported releases and security updates, and operate the licensed Enterprise environments described in the Order Form.
How are permitted Fabric Enterprise instances determined?
Permitted instances are determined by the active annual licence and the applicable Order Form.
Those terms define the number and type of approved environments and instances, which may include production, staging, development, high-availability, and disaster-recovery deployments.
Fabric Enterprise deployment rights are licence-scoped rather than unlimited, perpetual, or permanent.
Does Thrinacia offer managed private-cloud deployment for Fabric Enterprise?
Yes. Thrinacia can provide a managed private-cloud Enterprise deployment for organizations that want private infrastructure without operating the environment themselves.
Depending on the engagement, Thrinacia can also assist with deployments into a customer’s own private cloud environment.
Can Fabric Enterprise be self-hosted?
Yes. Self-hosted Fabric Enterprise deployments are available under an annual licence.
Self-hosted Enterprise customers receive compiled, signed backend runtime containers for approved deployments and may run those containers on their own infrastructure or private cloud, subject to the applicable licence and Order Form.
Is Fabric backend or API source code included?
No. Fabric’s backend and API implementation are not included in source form.
Protected backend code includes the FastAPI implementation, internal services, workers, transaction logic, authorization logic, deployment internals, and private build systems.
Customers integrate with Fabric through the supplied frontend, documented REST APIs, webhooks, and supported integrations. If backend changes are required, custom backend development can be performed by Thrinacia under a separate scoped engagement.
Still have questions?
Can’t find the answer you’re looking for? Our support team is here to help.
Contact Support