Websites and hosting decision
GitPage
A single developer can build the core generator, MCP endpoints, and GitLab-publish flow in about a week, but reproducing the vendor's free hosting, polished niche templates, integrated Claude UX, and support is operationally heavier—so build a focused replacement but keep paying if you need their turnkey hosting and service.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off34 h to build
$50/mo6 h/mo upkeep
No published price to break even against.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All GitPage alternatives, with the arithmetic →
What a replacement has to do
- Generate site HTML from a template using form answers; store site in a Git repo and push; expose MCP-style endpoints to read/edit/validate/preview/publish site files; preview drafts and publish to GitLab Pages; per-project access control and invitations.
What it still won’t have
- Free hosting provided by vendor (operational hosting and CDN)
- Pre-built niche templates and SEO toolkit tuned for conversions
- Vendor support, reviews-verified trust and on‑demand customer service
- Built-in MCP integrations with Claude and turnkey OAuth flows
- One-time purchase business model (you'd incur hosting and model costs monthly)
What remains hard
- Execution quality
Generate a real website in minutes, edit it from Claude Code over MCP, free hosting — forever.
- Integration maintenance
Gitpage ships a Model Context Protocol server.
- Execution quality
We charge once, hand you the source code, and host it on infrastructure you can walk away with.
First-year cost
No published price
GitPage does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build an MVP self-hosted AI-assisted static-site generator and MCP-compatible editor using: Next.js (or Hugo) for site generation, Node.js/Express for an MCP server, GitLab API for repo creation and CI-based Pages publishing, a simple SQLite for project and invite metadata, and Netlify or a cheap S3+CloudFront preview hosting for preview URLs. In scope: (1) a form-based site generator that renders HTML from templates and persists files to a git repo, (2) MCP endpoints: list_sites, read_site_file, edit_site_file (apply diffs to draft), validate_draft (basic lint/type checks), get_preview_url (create preview deploy), publish_draft (merge draft to main and trigger Pages publish), (3) per-project invites, owner/editor roles, and revoke, (4) CI pipeline to publish to GitLab Pages and generate preview URLs, (5) basic auth (email invites + token), error handling, and unit/integration tests for API flows. Out of scope: full commercial UI polish, built-in SEO copywriting models, one-click free vendor hosting, paid support. Provide automated tests for MCP endpoints, CI publish steps, and repo push flows.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 3 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productGitPage AI Website Builder — official site
- open sourcewebstudio-is/webstudio
- open sourcedecaporg/decap-cms
Integrity checks
What held up, and what did not.
