Clarification on Single Site Lifetime Purchase – Account vs Domain Binding

Finsweet Components
1

Hi Finsweet Team,

I’m planning to purchase a Single Site Lifetime license for one of your slider components for a client project, and I would like to clarify how the license is technically bound.

Here is my situation:

  • I am building the Webflow project in my own workspace.

  • After completion, the project will be transferred to the client’s Webflow account.

  • The client will host the project on their own custom domain.

  • I want to purchase the component as a one-time payment.

My questions:

  1. Is the Single Site Lifetime license bound to:

    • the Finsweet account that purchases it,

    • the Webflow workspace,

    • or strictly to the live domain?

  2. If I purchase the license under my Finsweet account and assign it to the client’s final custom domain, will the component continue working after I transfer the Webflow project to the client’s account?

  3. Will the client need access to my Finsweet login credentials for the component to keep functioning?

I just want to make sure the setup is fully compliant and that the client can safely own and manage the project long-term without any dependency on my account.

Thank you in advance for the clarification.

Best regards

2

Hey @benjamin.hensel :flexed_biceps:

Yes, this works exactly as you described! You’re good to go with this workflow.

The key thing to understand is that the Single Site Lifetime license is bound to the domain, not to your Finsweet account or the Webflow workspace. This is what makes your freelancer/client setup work perfectly.

Here’s how it works in your scenario:

Is the license bound to the Finsweet account, Webflow workspace, or the domain?

The license is bound strictly to the live domain. Once you assign your client’s custom domain to the license, the component will work on that domain permanently — regardless of which Finsweet account purchased it or which Webflow workspace the project lives in.

Will the component keep working after you transfer the Webflow project to the client’s account?

Yes, absolutely. Once the license is connected to the client’s custom domain, transferring the Webflow project to the client’s account has no impact on the component. It will continue working forever on that domain.

Will the client need access to your Finsweet login credentials?

No, they won’t. The component functions based on the domain license, not account access. Your client doesn’t need a Finsweet account or your credentials for the component to keep working.

A few helpful notes:

  • You can assign the client’s domain at any time after purchase — no rush to do it immediately
  • Domain changes are allowed with lenience for the same project/company if needed down the line
  • If you ever want to transfer ownership of the license to your client in the future (for their own management), you can reach out to us and we’ll guide you through the process

This is a really common setup for freelancers and agencies, and it’s designed to work smoothly! Let us know if you have any other questions.

1 Like
3

Does the domain binding work with subdomains and reverse proxies? We publish our Webflow project to multiple custom subdomains for dev testing, QA, and production. The production deployment is actually itself a subdomain of our main site (i.e. webflow-prod.example.com) and then we use a reverse proxy for the main public site.