Export, Code Access & Ownership

Flint does not currently offer a built-in export feature. Your site content lives within Flint's platform.

Workarounds for saving content:

• •Copy text and images directly from the Flint editor
• •Use your browser's "Save As" on any published page to capture a local snapshot (HTML + assets)
• •Use version history within Flint to view and restore previous versions of your pages

If you need assistance with content migration, contact support@tryflint.com and we'll help you explore options.

Flint does not currently support a direct GitHub connection on self-serve plans. All page editing is done through the Flint editor or via the API and MCP integrations.

On custom/enterprise plans, read-only code access may be available. Contact our sales team to discuss.

• •Your content — You own all the content you create (text, images, copy). This is your Customer Data as defined in our Terms of Service.
• •The platform — Flint owns the underlying codebase, framework, and hosting infrastructure. Sites are hosted on Vercel's edge network through Flint.
• •The repo — Flint owns the underlying repository and Vercel project.

• •Your pages stay live — published pages remain accessible on your domain
• •Your account stays accessible — you can still log in and view your site
• •Editing requires credits — since Flint uses a credit-based system, you won't be able to make changes once your remaining credits run out and renewal is canceled
• •You can come back anytime — re-subscribe to get credits and resume editing

Your pages and content are not deleted when you cancel.

If you need code-level control (e.g., building programmatic page generation from external data), Flint's API and MCP integration may meet your needs without direct code access.

For organizations that need deeper integration, enterprise plans include custom support for advanced workflows. Contact sales to discuss options tailored to your use case.