Self host Framer in an owned Next.js repository built from the Agentic Website Template. Recreate your live design, move the CMS and forms, preserve useful URLs, and deploy through your own hosting account with a codebase your team can keep editing.
Framer combines publishing with rendering, image optimization, font delivery, caching, CMS, forms, and domain settings. Hosting the site through your own account means giving each of those jobs a clear place in the new codebase.
Use the templateFramer's current self-hosting guide says published sites depend on its rendering, image, font, caching, and delivery infrastructure. An owned Next.js build gives your team source code and a separate deployment path.
Collection fields, item references, form destinations, uploaded fonts, images, and custom code all need an equivalent in the new website. Each part must still work after the domain moves.
Changed URLs need direct redirects. Canonical URLs, localized routes, analytics, form delivery, and HTTPS also need to be checked on the final deployment before DNS points visitors there.
The Agentic Website Template gives the rebuilt site a standard Next.js foundation, working marketing features, and clear instructions for AI coding agents. Your team controls the repository, deployment account, domain, and future changes.
See the three ways to use the templateHosting control
Next.js supports deployment as a Node.js server, Docker container, static export with limited features, or through compatible platforms. Choose the setup that supports the pages and services your marketing site needs.
CMS replacement
Export Collection data through a Framer plugin, then map fields, slugs, references, rich text, images, and localized routes into the new publishing setup. The starter includes a working blog pattern your team can adapt.
Lead delivery
Rebuild the fields, validation, success states, and spam protection. Connect the form to your email, CRM, database, or webhook, then submit real tests from the production domain.
Domain launch
The launch checklist covers public routes, direct redirects, canonical URLs, robots rules, sitemaps, forms, analytics, fonts, assets, and production settings. Preview stays private until the approved site is ready.
Ongoing editing
Goals, brand voice, design tokens, reusable components, sample content, and agent instructions live beside the code. Claude Code, Codex, or Cursor can use that context for the next landing page or site update.
Start with the services the live site uses, then rebuild and review one complete page in the Agentic Website Template. Choose the hosting setup after the site's runtime needs are clear.
Start with the Agentic Website TemplateRecord public and localized routes, CMS Collections, form destinations, fonts, assets, redirects, custom code, analytics, and important animation or interaction states.
Use the live Framer page as the visual reference. Ask your coding agent to recreate it in the starter, then review the layout and behavior at desktop, tablet, and mobile sizes.
Import Collection data, build its routes, add licensed font files and assets, reconnect form delivery, and configure redirects, metadata, analytics, and crawler files.
Create a preview through the chosen hosting account. Crawl the routes and test forms, redirects, fonts, tracking, and mobile behavior before updating DNS to the approved production deployment.
The repository, hosting account, environment settings, production releases, and domain configuration sit under accounts your company manages.
Your team can brief an AI coding agent, review a working preview, and publish new pages with the same brand, components, and release checks.
CMS content, forms, fonts, assets, redirects, analytics, and search settings have a documented home and a clear way to test them.
Clear answers for teams deciding how to move a Framer-origin website onto infrastructure they control.
Framer's specific self-hosting guide says it does not provide a supported standalone HTML bundle because published sites depend on managed rendering, images, fonts, caching, and delivery. For an owned hosting setup, rebuild the site in a framework such as Next.js and move each connected service.
Yes. Framer supports third-party custom domains through DNS records, while the published site continues to run on Framer's infrastructure. A reverse proxy is another documented option for some advanced setups, and Framer remains the content origin.
Framer CMS content can be read and exported through plugins in formats such as CSV or JSON. Rebuild the Collection model and routes in the new site. Recreate each form and connect it to the email, CRM, database, or webhook that should receive the submission.
Next.js supports Node.js servers, Docker containers, static exports with limited feature support, and compatible deployment platforms. The Agentic Website Template works naturally with Vercel, and the owned repository lets your team choose another provider that supports the Next.js features you use.
