Sitepins vs Sveltia CMS
Compare Sitepins and Sveltia CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing.
Sitepins
Git-Based CMSSitepins is a Git-based headless CMS built for teams who want full content control without the technical overhead. It connects directly to your repository and lets anyoneβwhether they're a developer or notβmanage content, collaborate in real time and deploy without touching code. Sitepins is designed for simplicity, speed, and non-technical accessibility, and it is fully open source (AGPL-3.0) on GitHub, so you can self-host it or contribute.
Get Started with SitepinsSveltia CMS
Git-Based CMSSveltia CMS is a free, open-source, Git-based CMS built as a complete modern rewrite and successor to Netlify/Decap CMS. It runs as a single-page app served from a CDN, stores content directly in your GitHub, GitLab, or Gitea/Forgejo repository, and focuses on editor UX, digital asset management, and first-class internationalization. It is currently in beta, with version 1.0 (GA) scheduled for late 2026.
Visit Sveltia CMSOverview
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| CMS type | Git-Based (open source, AGPL-3.0 licensed) | Git-Based (open-source, MIT-licensed). Currently in beta; version 1.0 (GA) scheduled for late 2026. |
| SSG support | Astro, Next.js, Hugo, 11ty, Jekyll, SvelteKit, Nuxt + more | Astro, Eleventy, Hugo, Jekyll, Next.js, Nuxt, SvelteKit, VitePress, Docusaurus, Middleman, Zola + framework-agnostic support for vanilla JavaScript sites |
| Pricing entry point | $12/mo (monthly) or $10/mo (annual); $199 one-time lifetime | Free forever. Open source under the MIT license, free for personal and commercial use. No paid tier. |
| Free plan | β Yes β Free forever, with limitations (Hobby plan) | β Yes β The entire CMS is free and open source. No user, project, or feature limits. |
| Free trial (without credit card) | β Yes β 15 days (no card required) | β Yes β No trial needed. The CMS is permanently free. |
| Content security | β Yes β Highly secured. No database to hack; files are static and stored in Git | β Yes β Highly secured. No database and no CMS server; the app runs client-side and content is stored as static files in your own Git repository. |
| Native language support | β Yes β 12 languages natively (en, zh, ja, de, fr, es, pt, ru, ko, id, vi, bn) for a consistent and localized experience | β Yes β The admin UI is localized in Bulgarian, Catalan, Croatian, English (US/UK/CA), Greek, Japanese, Portuguese (Brazil), Russian, and Ukrainian. It auto-detects the browser language and can be switched in settings. |
| Mobile friendly | β Yes β Fully mobile and tablet optimized | β Yes β Fully responsive with dedicated mobile and tablet support, QR code login, and installable as a progressive web app (PWA). |
Setup & Configuration
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| Non-technical setup | β Yes β Zero configuration. Register, connect your repo and get started without any code or config. | β No β Requires developer setup. A developer must add two files to the project (admin/index.html and config.yml) and register an OAuth application with the Git provider before the CMS is usable. |
| Starter templates | β Yes β 100+ Astro, Hugo, and Next.js ready-made project templates to launch faster | β οΈ Yes but β The docs link to community templates for Astro, Eleventy, HonoX, Hugo, Jekyll, and Zola. These are third-party resources not reviewed by the Sveltia CMS team, and there is no curated official library. |
| Edit schema modifier | β Yes β Visual schema editor within the CMS. Adjust content field types and settings directly inside the CMS. | β No β Collections and fields are defined entirely in the config file (YAML, TOML, or JSON). There is no visual schema editor inside the CMS, though JSON Schema validation and IDE auto-completion are provided. |
Editing Experience
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| Editor | Visual editor + Markdown + Code | Rich text (Lexical-based WYSIWYG) + Markdown + Code. Content is written out as Markdown, YAML, JSON, or TOML. |
| Live preview system | β Yes β Sandbox live preview. See how your content looks on the site before publishing. | β οΈ Yes but β A preview pane is included, and custom preview templates and preview styles can be registered through the JavaScript API. Matching the preview to your siteβs frontend requires developer setup. |
| AI assistant integration | β Yes β Bring Your Own Key (BYOK) supporting OpenAI, Gemini, Claude, and Grok to generate or rewrite content inside the editor. | β οΈ Yes but β One-click AI translation is supported via Anthropic, OpenAI, and Google Cloud Translation using your own API key. There is no general-purpose AI writing or rewriting assistant; broader AI features sit beyond the v2.0 roadmap. |
| Collaborative editing | β Yes β Allows multiple users to edit content simultaneously. | β No β No simultaneous multi-user editing. Collaboration happens through Git commits. Multi-user support with edge-function-based user management is planned for v2.0. |
| iFrame embed preview | β Yes β Render embedded content like videos or charts live inside the editor. | β No β Not a native feature. iFrame or embed rendering inside the editor is not documented and not available out of the box. |
| Shortcode support | β Yes β Manage shortcodes and custom content blocks for powerful content structuring. | β Yes β Custom editor components can be registered through the JavaScript API to create reusable block-level components in the rich text editor, alongside the built-in code-block and image components. Configured by developers. |
| SEO tools | β Yes β Built-in tools to optimize and preview content for search engines, content analysis, slug editing, and SERP preview. | β No β No built-in SEO analysis, SERP preview, or content scoring. SEO fields must be modeled manually in the content configuration. |
| Dark mode | β Yes β Supports full platform dark mode, switchable between Dark and Light. | β Yes β Built-in light and dark themes. Follows the system preference by default and can be switched in app settings. |
Non-Technical User Experience
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| Designed for non-technicals | β Yes β Core product mission. | β οΈ Yes but β The UI is modern, accessible, and editor-friendly once configured. However, initial setup, schema changes, and authentication always require a developer, and every editor needs their own Git account. |
| Version rollback | β Yes β Undo changes and restore a previous version without touching Git, directly within the CMS. | β οΈ Yes but β Entries are automatically backed up to browser storage while editing and can be restored as drafts. Full version history lives in Git, and there is no in-CMS Git rollback UI. |
| Initial setup by non-dev | β Yes β Zero configuration. Can be set up easily without developer involvement. | β No β A developer must create the admin files, write the config, and register an OAuth app before the CMS is usable by anyone. |
Media Management
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| Media management | β Yes β Upload, organize, drag and drop, rename files and folders, replace images and delete directly from the CMS. | β Yes β Built-in digital asset management with drag-and-drop uploads, folder structures, search and filtering, configurable file size limits, and automatic image optimization (WebP conversion, resizing, SVG minification). |
| External image URL support | β Yes β Use images hosted on external CDNs or third-party services directly in the editor. | β Yes β Multiple external storage providers can be used at the same time: Cloudinary, Uploadcare, Amazon S3 and S3-compatible services (Cloudflare R2, Backblaze B2, DigitalOcean Spaces, Scaleway, Supabase Storage), plus stock photo integration with Pexels, Pixabay, and Unsplash. |
Collaboration & Teams
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| User access | β Yes β Invite editors by email. Possible without requiring a Git account. | β No β Every editor needs their own Git account with write access to the repository, signing in via OAuth or a personal access token. Git Gateway and Netlify Identity are not supported, so there is no email-only editor invite. |
| Custom roles | β Yes β Define specific permission levels for different types of users. E.g. Owner, Admin, Editor. | β No β No role management inside the CMS. Permissions are inherited from the Git providerβs repository access. Roles and user management are planned for v2.0. |
| Organization management | β Yes β Manage multiple teams and projects under one account. | β No β Each site gets its own admin instance. There is no centralized multi-project or multi-team dashboard. |
| Branch workflows | β Yes β Manage branches, create PRs, and merge directly from Sitepins. | β οΈ Yes but β A simple workflow (commit straight to a branch) and Open Authoring (external contributors submit pull requests) are supported. The Editorial Workflow with draft, review, and ready statuses is documented as βnot yet supported in Sveltia CMSβ and is planned before the 1.0 release. |
Git & Deployment
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| Git providers | GitHub (all plans), GitLab (Team plan) | GitHub, GitLab, and Gitea/Forgejo, plus a test backend and a local repository workflow. Bitbucket, Azure DevOps, and Git Gateway are explicitly not supported. |
| Vendor lock-in | β No β No vendor lock-in. Content is stored in your own repo, and Sitepins itself is open source (AGPL-3.0), so you can self-host the CMS too. | β No β No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source under the MIT license. |
| Deployment | β Yes β One-click Vercel deployment built-in. | Content commits trigger builds on any connected CI/CD platform. Works with Vercel, Netlify, Cloudflare Pages, GitHub Pages, and any Git-integrated host. No built-in one-click deployment. |
Accessibilities
| Feature | Sitepins | Sveltia CMS |
|---|---|---|
| Global search | β Yes β Cmd/Ctrl+K to search for files stored anywhere in the CMS. | β Yes β Instant full-text search across all collections, entries, and assets with Cmd/Ctrl+F, plus keyboard shortcuts for the content library (Alt+1), asset library (Alt+2), and new entries (Cmd/Ctrl+E). |
| Edit configs as code | β Yes β Direct access to configuration files. | β Yes β Configuration is written as code in YAML, TOML, or JSON, with JSON Schema validation, IDE auto-completion, TypeScript types, and a JavaScript API for customization. |
| Mermaid diagram preview | β Yes β Render Mermaid diagrams live while writing without leaving the CMS. | β No β Mermaid diagram preview is not a built-in or documented feature in Sveltia CMS. |
Which one is right for you?
A quick summary to help you choose the right Git-based CMS.
Choose Sitepins if:
- You want to get started without writing a single line of config
- Your team includes non-technical editors or clients who need to manage content independently
- You want built-in AI assistance, collaborative editing, and live previews out of the box
- You need editors who can join by email invite without a Git account
- You want a stable, production-ready platform with commercial support and migration help
Choose Sveltia CMS if:
- You want a completely free, MIT-licensed, self-hosted CMS with no paid tier at all
- Your team has a developer comfortable with YAML/TOML/JSON config and OAuth app setup
- You publish multilingual content and want first-class i18n with one-click AI translation
- Your editors already have GitHub, GitLab, or Gitea accounts with write access to the repo
- You are migrating off Netlify/Decap CMS and want a faster, modern drop-in replacement
Already using another CMS?
Whether you are coming from WordPress, Contentful, Sanity, or any other platform, our team is ready to help you migrate your content, structure, and workflows with zero downtime. Migration support is available for all users on the Team plan or the Lifetime deal. We handle the boring, tedious tasks so you can focus on launching as soon as possible.
Get Started with Sitepins
Get started for free today and discover easy, flexible, and full control over your content.