---
title: FAQ
description: Common questions and what is not supported yet.
sidebar:
  order: 9
---

**Do I need to change my Astro site?**

No. Gitupcms reads `content.config.ts` and `astro.config.*`. Optional features (language kit, page settings, comments) install with a commit or pull request you can read first.

**Where is my content stored?**

In your GitHub repository, as files. The Gitupcms database holds users, workspaces, settings, media metadata (alt text, captions), comments and feedback pins.

**Does it work with sites that are not Astro?**

No. Detection is built on Astro's content collections and config.

**Can clients without GitHub use it?**

Yes. Invite them; they sign in with a code sent to their email.

**Which AI models does it use?**

Any OpenAI-compatible endpoint you configure with `AI_BASE_URL`, `AI_API_KEY` and `AI_MODEL`.

**Does it support GitLab or Bitbucket?**

No, GitHub only.

## Not supported yet

- Images and tables inside the rich body editor (such bodies open in Source mode).
- Folder navigation in collections, and renaming entries.
- New site data stored as part of a shared YAML/TOML file.
- Media tags and image size variants.
- GitHub App installations and webhooks.
- A branch switcher and a cache admin page.
- Billing.