Running Flint Alongside Your Existing CMS

Flint is designed to work alongside your existing website stack. Whether you run WordPress, Webflow, DatoCMS, Contentful, Gatsby, Next.js, or something else, Flint handles landing pages while your CMS handles the rest.

With reverse proxy (subfolder) hosting, your web server routes specific URL paths to Flint while everything else is served by your existing CMS.

Example:
- yoursite.com/ — your CMS (homepage, blog, product pages)
- yoursite.com/lp/* — Flint (ad landing pages, campaign pages)
- yoursite.com/events/* — Flint (event pages)

To visitors and search engines, everything looks like one cohesive site under one domain.

• •No migration required. Keep your CMS for what it does well. Use Flint for high-velocity pages your marketing team can build without engineering.
• •SEO continuity. Domain authority stays intact. Flint pages inherit your domain's trust signals.
• •Shared cookies and consent. Because Flint pages live under your domain, your analytics, CMP consent, and session cookies work seamlessly across both systems. See Cookie Consent & CMP Integration and Data Residency & GDPR Compliance.
• •Independent deployment. Publishing a Flint page does not trigger a build or deployment on your CMS, and vice versa.

See Hosting Options to choose the right publishing setup for your stack and get step-by-step configuration guides.

Can I use the same header and footer as my main site?
Yes. Flint extracts your site's navigation and footer during brand import. You can also use Mirror Sections to pull live sections from your main site into Flint pages.

Will this affect my site's performance?
No. Flint pages are served from a global CDN edge network. The reverse proxy adds negligible latency (under 10ms).

Can I move pages between Flint and my CMS later?
Yes. Flint pages live at specific URLs, so you can redirect those paths back to your CMS at any time.