Does NoCodeXport actually produce a fully standalone Framer export?

I recently purchased NoCodeXport’s €89 one-time export because I needed to move a Framer project to independent hosting while preserving the original design and functionality.

In my test, the resulting export did not behave as a fully self-contained version of the site.

The generated export log reported “Assets: 0”, and images, icons, and fonts were not packaged locally as I expected. The generated code also continued to reference Framer-hosted resources.

More importantly, some JavaScript-dependent functionality did not survive the export correctly. Interactive elements, buttons, and animations stopped working as expected after deployment.

I initially considered whether this might be caused by my hosting environment, but after inspecting the generated files, the external dependencies appeared to be part of the export itself.

I’d be especially interested in hearing from developers who have inspected the generated files rather than only compared the visual appearance of the exported site.

If the NoCodeXport team can clarify which Framer features are expected to survive a standalone export and which still depend on Framer infrastructure, that would also be useful information for prospective users.