Comparison

Pagewell vs Flint: keep the source of truth in your repo, or move it to a platform?

Both create pages. They disagree on where the page system lives: in your repo with Pagewell, or on Flint's hosted platform.

$ bunx skills add ReScienceLab/pagewell --skill pagewell

Installs the Pagewell agent skill via skills.sh.

Read setup doc

Direct answer

Choose Pagewell when your website already lives in a repo and page generation should produce reviewable code changes. Choose Flint when the team wants a hosted platform for page creation, editing, publishing, and GTM workflows outside the existing codebase.

Pagewell

Stays in your repo

Best fit when agents should edit the existing codebase and produce routes, content, components, metadata, schema, QA notes, and discovery updates.

Flint

Hosted platform

Best fit when teams want an integrated platform for brand import, page creation, editing, hosting, publishing, and GTM workflows.

Decision

Choose by where you want control

The practical question is whether your source of truth should remain in the repo or move into a managed page platform.

Decision summary

Start with the system of record.

If marketing pages must be normal code reviewed through your existing repo, Pagewell is the more natural architecture. If the team wants a hosted product surface for page creation, editing, hosting, and GTM workflows, Flint may fit better.

Comparison table

Different systems for different operating models.

Dimension	Pagewell	Flint
System of record	Existing website repo	Hosted Flint platform
Primary user	Coding agents with developer review	Marketing and GTM teams using a product UI/API
Design source	DESIGN.md plus existing site components	Brand import from an existing website
Output	Normal code/content changes	Pages managed and hosted through Flint
Best-fit motion	SEO/GEO pages, docs, free tools, and repo-native page clusters	Ad pages, ABM pages, GEO pages, and programmatic hosted campaigns

Choose Pagewell when

The repo needs to stay the source of truth.

Your team wants to review page changes as diffs before merge.
Generated pages must reuse existing layouts, components, static generation, and deployment conventions.
You want claim checks, anti-generic QA, sitemap behavior, robots guidance, and llms.txt updates documented in the same repo.
Free tools or docs need to live beside the product website code rather than in a hosted page builder.

Choose Flint when

The marketing team needs an integrated page platform.

Marketers need a dedicated UI for creating and editing pages without opening a repo.
Hosted page workflows, brand import, publishing, and GTM integrations are the main requirement.
ABM or ad-page operations need a managed product surface rather than repo-based code review.

FAQ

Common questions, answered directly.

Is Pagewell a Flint alternative?

Only for teams that specifically want repo-native agent workflows. Flint is a hosted autonomous web platform; Pagewell is a skill pack that operates inside an existing website repo.

When should I choose a hosted platform like Flint?

A hosted platform can be a better fit when marketers need an integrated editing, hosting, publishing, and workflow surface without working in a codebase.

When should I choose Pagewell?

Choose Pagewell when your site already lives in code and you want agents to create routes, components, metadata, schema, and discovery updates as reviewable repo changes.

Install Pagewell

Ready to compare from your own source files?

Add Pagewell to your repo and generate comparison pages that use your product facts, claim rules, route patterns, and QA gates.