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. Your team can edit pages through the Flint editor or via the API and MCP integrations.

Read-only code access may be available on Enterprise. 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.

If you're considering ending your Flint engagement, contact our team to discuss your pages, access, and data portability. Your contract determines what happens to hosting and editing access after the engagement ends. Plan any migration with your Flint contact before your end date.

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.