---
title: Gitupcms
description: "A git-based CMS for Astro sites. No config file, no build plugin: it reads what your Astro project already has."
---

Gitupcms edits Astro sites that live on GitHub. It reads your `content.config.ts`, `astro.config.*` and the files in the repo, and turns them into forms, a media library, menus, redirects and an AI editor. Every save is a git commit (or a pull request, if you turn on reviews).

:::tip[No `.pages.yml`, no `config.yml`]
Other git CMSs need a config file in every repo. Gitupcms needs none. Sign in with GitHub, pick a repository, start editing.
:::

**[Quickstart](/quickstart)**

Sign in, open a site and make your first commit.

**[How detection works](/content/detection)**

What Gitupcms reads from your Astro project.

**[AI Editor](/editing/ai-editor)**

Click an element on the live preview and describe the change.

**[Feedback pins](/editing/feedback)**

Clients pin comments on the site; you turn them into AI prompts.

**[Gitupcms SEO](/plugins/seo)**

Site-wide SEO checks with agents that fix what they find.

**[Self-hosting](/self-hosting)**

Run it on your own server with SQLite and one Node process.

## What you get

| Area | Features |
| --- | --- |
| Content | Collections and fields from your Zod schemas, site data files, Configure site, languages |
| Media | Repo folders, S3 / Cloudflare R2 buckets, external URLs; crop, WebP, move with reference rewriting |
| Editing | Entry editor with SEO sidebar, AI Editor on the live preview, Edit content in place, Undo |
| Site management | Pages (page settings), Menus, Redirects, GitHub Actions runs |
| Teams | Workspaces, roles (admin, reviewer, editor, viewer), invites, email sign-in for clients |
| Agencies | Client sites dashboard, Feedback pins, review before publishing |
| Plugins | Gitupcms SEO, Comments |