# Sitepins - Open Source Git-based Headless CMS for Static Sites URL: https://sitepins.com ## Open source content editor for static and vibe-coded sites URL: https://sitepins.com Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Join 1800+ users managing websites with Sitepins # Open source content editor for static and vibe-coded sites Sitepins lets anyone update your site visually, without touching the code. Connect your Git repo and get a clean visual editor. [Get Started for Free ](pricing?ref=banner)[Live Demo](https://demo.sitepins.com) ![Sitepins CMS Dashboard](/_vercel/image?url=%2Fimages%2Fsitepins-dark.png&w=1200&q=100&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![](/_astro/grids_w_boxes.DINs8k1j.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)![](/_astro/micro_stars.B8j_eEE1.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) For personal sites ## Write, commit, done Your blog lives in your repo. Edit in a clean visual editor and every save is a commit. Sign up, connect the repo, and start writing in minutes. - #### No database Content is markdown in your repo. Nothing to host, back up, or pay for. - #### Visual editing A clean WYSIWYG over your real files. Write, preview, publish. - #### Draft now, publish later Save a half-finished post instantly without rebuilding the site. It goes live only when you say so. - #### SEO built in Edit slugs, check a search preview, and get recommendations while you write. - #### Publish from your phone The full editor works on mobile and tablet. Fix a typo or ship a post from anywhere. [Get started free ](pricing?ref=audiences-personal) ![Sitepins markdown editor pane](/_vercel/image?url=_astro%2Fpersonal.DfInfsMw.png&w=828&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) For company sites ## Marketing edits. Engineering keeps control Give your team a real editing UI while every change still flows through Git: reviewable, revertible, and yours. - #### Roles & permissions Give marketing edit access without handing over the whole repo. - #### Review & revert Every change is a commit. Diff it, approve it, roll it back. - #### Branch previews Draft on a branch, preview it, merge when it's ready to ship. - #### Structure you define Lock down fields, types, and dropdowns once so no one can break the content model later. - #### Edit together, live Live cursors and avatars show who is working where, so two people never overwrite each other. [Get started free ](pricing?ref=audiences-company) ![Sitepins roles and commit review](/_vercel/image?url=_astro%2Fbusiness.B_ZAq4EI.png&w=828&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) For agencies & freelancers ## Hand it off without the hand-holding Built it with Claude, Lovable, or Replit? Push to GitHub, connect the repo, and give your client an editor they can actually use, with no terminal and no broken builds. - #### Invite by email Clients edit safely, with no GitHub account or terminal required. - #### Self-serve undo They can roll back their own mistakes without pinging you. - #### AI-builder ready Ship from Claude, Lovable, or Replit, then connect the repo. - #### Setup skill A guided flow gets any repo editable in minutes, not hours. - #### A workspace per client Separate organizations keep every client's sites, team, and permissions cleanly apart. [Get started free ](pricing?ref=audiences-agencies) ![Sitepins client editor invite by email](/_vercel/image?url=_astro%2Fagency.D8p9QClA.png&w=828&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) Key Features ## Features That Make Content Editing Effortless Everything your teammates or clients need to update content without touching code. ### Easy Setup No complicated setup. register, connect your repo, and you’re ready to go — even if you’ve never used a CMS before. ![Quick and Easy Setup](/_vercel/image?url=_astro%2Feasy-setup.DESJijM5.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Stay in control with Git Every edit is versioned, trackable, and reversible. You’ll always know who changed what. ![Git Integration in Sitepins](/_vercel/image?url=_astro%2Fgit-workflow.IAwiiopi.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Edit visually Update text, images, and content directly in the editor. No more back-and-forth with developers for small changes. ![Visual Markdown Editor](/_vercel/image?url=_astro%2Fwysiwyg-editor.CFWYt7f-.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Live Preview See your changes instantly in a sandbox preview without rebuilding the site. Your edits update in real time so you can verify content before publishing. ![Live Preview Sandbox](/_vercel/image?url=_astro%2Flivepreview.CClywa_3.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Keep media organized effortlessly Drag, drop, and reuse images right inside the CMS. ![Manage Media Files Easily](/_vercel/image?url=_astro%2Fmedia-management.D6KlzgEG.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Works with your favorite stack Sitepins supports Astro, Next.js, Hugo, and other leading static site generators. ![All Static Site Generators Support](/_vercel/image?url=_astro%2Fssg-support.CTABSsRp.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Support Shortcodes Easily manage shortcodes and custom content blocks for powerful content structuring. Save time and stay consistent. ![Shortcode Editing in CMS](/_vercel/image?url=_astro%2Fshortcode.dkOCMW9K.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Collaborate with your team safely Manage roles, permissions, and access for multiple users. Live presence indicators show exactly who is working and where ![User Roles and Permission Management](/_vercel/image?url=_astro%2Fpermission.B9HaNGsC.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Keep Complex Content Organized Maintain a clean content hierarchy, even for large sites — everything stays easy to find, edit, and manage visually. ![Nested Content Collections](/_vercel/image?url=_astro%2Fnested-collection.CU4iK8uC.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Compatible with all popular file formats Sitepins works with Markdown, JSON, YAML, and TOML — whatever your static site uses. ![Multi-format Content Support](/_vercel/image?url=_astro%2Ffiles-support.DPZJCI79.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Native Language Support Sitepins supports 12 (en, zh, ja, de, fr, es, pt, ru, ko, id, vi, bn) languages natively for a seamless, consistent, and localized experience. ![Native Translation Support](/_vercel/image?url=_astro%2Fmultilingual.D2aDITfI.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### AI Assistant Plug in your own API key (OpenAI, Gemini, Claude, Grok) to generate or rewrite contents inside the editor. ![AI Content Assistant](/_vercel/image?url=_astro%2Fai-assistant.BTrX11pe.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) How it Works ## Connect. Edit. Ship. Everything within minutes ![Connect Repo](/_astro/project-setup.0okJdjMy.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Connect Repo Connect your Git repository once. Sitepins automatically detects your content structure. ![Edit Visually](/_astro/project-configure.Cq3OqEdc.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Edit Visually Your team edits Markdown, MDX, JSON, YAML, and more through a clean visual editor. No code required. ![Commit & Ship](/_astro/project-edit.BD4QGJqy.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Commit & Ship Every save is a Git commit, tracked and reversible, and flows straight to your live site. Works With Your Stack ## From Static Sites to Vibe-Coded Sites Sitepins works with your favorite static site generators, and the sites you shipped with Claude, Lovable, or v0. ![Astro](/_astro/astro.B0kbbGDX.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Next.js](/_astro/nextjs.r9RVkKBW.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Hugo](/_astro/hugo.sguaXCtV.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Svelte](/_astro/svelte.cTaBEOoE.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![11ty](/_astro/11ty.U9TRdOsx.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Jekyll](/_astro/jkyll.DXe2lFgk.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Claude Code](/_astro/claudecode.CVopZaDv.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Loveable](/_astro/loveable.DLB1BxKZ.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) > I've worked with almost every headless CMS out there. Sitepins is by far the best. Handing projects off to non-technical clients has never been smoother. All my Astro themes now come pre-configured with Sitepins and it's the default CMS for my clients' projects too. ### Christos Founder & Lead Designer, Oxygenna > I wanted to give our marketing team the ability to edit content without them poking me every time. So far, it’s going well. I can finally focus on more complex tasks rather than just changing a heading or triggering a rebuild. ### Somrat Developer Team Lead > I absolutely love the UI and the experience of working with it. The configuration and set-up was simple, smooth and easy. ### Emmanuel Chief Technical Officer > Sitepins looks pretty sweet. Great job. It’s just what I’ve been looking for. ### Jim Mitchell Developer and Tech Blogger > Sitepins looks really nice, it's just what I hoped to find. ### Joakim Freelance Developer ![Christos](/_vercel/image?url=_astro%2Fchirstos.DV2Y3f2T.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Somrat](/_vercel/image?url=_astro%2FSomrat.BwganZp8.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Emmanuel ](/_vercel/image?url=_astro%2FEmmanuel.Bsrg7jKY.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Jim Mitchell](/_vercel/image?url=_astro%2FJim-Mitchell.Dg26QtN6.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Joakim](/_vercel/image?url=_astro%2FJoakim.XmZu6oLf.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) Join the teams simplifying content editing with Sitepins. ![Themefisher](/_astro/themefisher.DdObPKXZ.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![GetHugoThemes](/_astro/gethugothemes.D4jOwvUz.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Statichunt](/_astro/statichunt.ogDzivN2.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Uihut](/_astro/uihut.DNlBUx8T.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Zeon Studio](/_astro/zeon-studio.Bn2Zoq8x.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Supernova](/_astro/supernova.DXiL8Uo6.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) FAQs ## Frequent Questions Got questions? We’ve got clear answers to help you get started. What is Sitepins? What is a Git-based CMS? Do I need to install anything to use Sitepins? Have more question? [Contact Us](contact) to inquire more! ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## The Story Behind Sitepins URL: https://sitepins.com/about Learn how Sitepins was born from frustration with existing CMSs. We're a bootstrapped team solving real problems for developers and founders who need visual content management for static sites. About Us # The Story Behind Sitepins ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) **We built Sitepins to solve our own problem. Now we’re sharing it with you.** In 2018, our world was perfect. As the founder of Themefisher and Gethugothemes, we were early adopters of the Jamstack concept. We were building high-performance static site themes with Hugo and Bootstrap. For content management, we had found a Git-based CMS that was a game-changer. It allowed us and our customers to edit sites visually without ever touching code. We were so all-in that we created tutorials showing developers how to use it with our themes. One video exploded [60,000+ views on YouTube](https://youtu.be/ResipmZmpDU), proving just how desperately developers needed this solution. Then everything changed. In 2023, the CMS we relied on announced it was shutting down!!! (RIP Forestry) The market was left in chaos. We were left supporting 100+ themes (Now 180+) with no good way forward. We searched desperately for alternatives: - Forestry team’s new product was focused on _enterprise clients_. Still, we tried to use and integrate it with our websites and themes, but it didn’t work out like Forestry did. - CloudCannon was fully commercial and too expensive. It also wasn’t compatible to work with our themes out of the box. - DecapCMS (formerly Netlify CMS) was not actively maintained, and Netlify announced they would no longer work on it. There were hundreds of unaddressed bugs and a UX that made simple tasks feel like a struggle. - We even tried to clone and modify Decap CMS since it was open source, but found a fragmented architecture that was beyond saving. Meanwhile, our own team was stuck in a loop of manual updates. Our marketing team couldn’t manage content on our own sites without developer time. We couldn’t scale. It wasn’t sustainable. **The problem got bigger…** At the same time, we expanded our offering. We found Astro and Next.js were also great for creating modern websites. We started releasing themes for them, and developers loved our products just like they loved our HTML and Hugo themes. But then developers started asking: _“We work with non-technical clients and teammates. When we hand off sites to them, they need a CMS. What do you suggest?”_ We couldn’t suggest anything. No CMS we found was perfect. Those developers were frustrated with existing solutions. They knew static sites were great, but couldn’t use them for their non-technical clients and teammates because of the missing “CMS” piece. That’s when it hit us. If we wanted a tool that actually worked for Astro, Hugo, and Next.js (one that met the standard we’d once had), we would have to _build it ourselves_. **The birth of Sitepins** Our idea was simple: You don’t need to set up anything extra to use the CMS. You can build the site as you like. You can connect your repository and start editing visually. No custom schema creation needed. The CMS should do it for you or make it easy for you. We found a web-based solution would be best for this. After months of working, we found it works for our own use case! Though it wasn’t perfect, it served our needs. Then we opened it to the world. When we launched the _beta_, something unexpected happened. 1800+ people (and counting) registered without any heavy promotion so far. We realized we weren’t alone in our struggle. We had built something others desperately needed. **Why we’re bootstrapped (and why that matters)** We’re building Sitepins without outside funding. No investors. No venture capital. Just a small team solving a real, niche problem. This gives us freedom. _We answer to our users, not shareholders._ We can focus on what actually matters: building a tool that works, consistently, for developers and their teams. **SITEPINS IS NOT A SIDE PROJECT OR An EXPERIMENT** We’ve been building products for the modern web development industry for _over 8 years_. Today, all our websites (_Themefisher_, _Gethugothemes_, _UIHut_, _Statichunt_, _Zeon Studio_, _Sitepins Itself_ and more) managed via Sitepins. That’s why we improve the product every single day. We live on it. We’re committed to making it better continuously. **Sitepins is open source, so even if we ever run out of business (we hope that never happens), you can continue using and building on it yourself.** As an early adopter, you’re part of building something meaningful. And we’re grateful to have you here. Thank you. Mehedi Sharif _On behalf of the Sitepins team_ ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Git-based Headless CMS for Astro URL: https://sitepins.com/astro-cms Sitepins gives your non technical clients and teammates a visual editor to manage content on Astro Astro CMS # Git-based Headless CMS for Astro Sitepins gives your non technical clients and teammates a visual editor to manage content on Astro. [Sign up for FREE ](https://sitepins.com/pricing) No credit card required. Free tier forever. ![sitepins cms nextjs](/_vercel/image?url=_astro%2Fcode-editor.CPXDpsp8.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![sitepins cms nextjs](/_vercel/image?url=_astro%2Fsitepins-landing.DmBPf6R4.png&w=1920&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![](/_vercel/image?url=_astro%2Four_story_bg.4SkuIFY4.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) How it Works ## Connect. Configure. Start Editing. Everything within minutes ![Connect Repo](/_astro/project-setup.0okJdjMy.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Connect Repo Connect your Git repository once. Sitepins automatically detects your Astro content collection structure. ![Configure](/_astro/project-configure.Cq3OqEdc.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Configure Sitepins automatically reads your content files (Markdown, MDX, JSON) and presents them as simple, easy-to-edit structured forms. ![Start Editing](/_astro/project-edit.BD4QGJqy.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Start Editing Your team can start editing immediately. Every save is tracked and fully reversible, so you never have to worry about breaking the site. FOR EDITORS ## Content Editing Simplified. Streamline your content editing process. Let your team edit and publish directly while keeping full version history. ### Empower your Content Team - Edit content using a visual editor. No coding or technical knowledge required. - Easily update metadata, tags, dates and other SEO configurations. - Manage media assets easily with a focused library using the drag-and-drop feature. ![sitepins cms astro visual editor](/_vercel/image?url=_astro%2Fcms-editor.ogjQw1_r.png&w=828&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) FOR DEVELOPERS ## Preserves Astro’s code, Speed and Integrity. Hand off your site to clients with ease. Editors get a simple visual tool to update contents, keeping your Astro code clean and uninterrupted. ### Streamline your Dev Workflow - Content is versioned within your Git repository, synchronized with your code. - Sitepins preserves Astro's zero-JavaScript default and optimal Server-First rendering. - Editors can update content via a visual editor, keeping them out of your codebase. ![sitepins cms astro visual editor](/_vercel/image?url=_astro%2Fastro-cms.DVFQNEvn.png&w=828&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Key Features ## Features That Make Content Editing Effortless Everything your teammates or clients need to update content without touching code. ### Easy Setup No complicated setup. register, connect your repo, and you’re ready to go — even if you’ve never used a CMS before. ![Quick and Easy Setup](/_vercel/image?url=_astro%2Feasy-setup.DESJijM5.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Stay in control with Git Every edit is versioned, trackable, and reversible. You’ll always know who changed what. ![Git Integration in Sitepins](/_vercel/image?url=_astro%2Fgit-workflow.IAwiiopi.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Edit visually Update text, images, and content directly in the editor. No more back-and-forth with developers for small changes. ![Visual Markdown Editor](/_vercel/image?url=_astro%2Fwysiwyg-editor.CFWYt7f-.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Live Preview See your changes instantly in a sandbox preview without rebuilding the site. Your edits update in real time so you can verify content before publishing. ![Live Preview Sandbox](/_vercel/image?url=_astro%2Flivepreview.CClywa_3.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Keep media organized effortlessly Drag, drop, and reuse images right inside the CMS. ![Manage Media Files Easily](/_vercel/image?url=_astro%2Fmedia-management.D6KlzgEG.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Works with your favorite stack Sitepins supports Astro, Next.js, Hugo, and other leading static site generators. ![All Static Site Generators Support](/_vercel/image?url=_astro%2Fssg-support.CTABSsRp.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Support Shortcodes Easily manage shortcodes and custom content blocks for powerful content structuring. Save time and stay consistent. ![Shortcode Editing in CMS](/_vercel/image?url=_astro%2Fshortcode.dkOCMW9K.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Collaborate with your team safely Manage roles, permissions, and access for multiple users. Live presence indicators show exactly who is working and where ![User Roles and Permission Management](/_vercel/image?url=_astro%2Fpermission.B9HaNGsC.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Keep Complex Content Organized Maintain a clean content hierarchy, even for large sites — everything stays easy to find, edit, and manage visually. ![Nested Content Collections](/_vercel/image?url=_astro%2Fnested-collection.CU4iK8uC.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Compatible with all popular file formats Sitepins works with Markdown, JSON, YAML, and TOML — whatever your static site uses. ![Multi-format Content Support](/_vercel/image?url=_astro%2Ffiles-support.DPZJCI79.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Native Language Support Sitepins supports 12 (en, zh, ja, de, fr, es, pt, ru, ko, id, vi, bn) languages natively for a seamless, consistent, and localized experience. ![Native Translation Support](/_vercel/image?url=_astro%2Fmultilingual.D2aDITfI.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### AI Assistant Plug in your own API key (OpenAI, Gemini, Claude, Grok) to generate or rewrite contents inside the editor. ![AI Content Assistant](/_vercel/image?url=_astro%2Fai-assistant.BTrX11pe.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Free Templates ## Start With a Template Launch your project faster with our pre-configured starters. ![PowerAI Astro](https://assets.teamosis.com/thumbs/powerai.png) ### PowerAI Astro astrosaas [Get Start For Free]() ![Astroplate](https://assets.teamosis.com/thumbs/astroplate.png) ### Astroplate astroblog [Get Start For Free](https://app.sitepins.com/new/clone?name=Astroplate&repository=https://github.com/zeon-studio/astroplate) ![Geeky Astro](https://assets.teamosis.com/thumbs/geeky.png) ### Geeky Astro astroblog [Get Start For Free]() ![Hydrogen Astro](https://assets.teamosis.com/thumbs/hydrogen.png) ### Hydrogen Astro astroblog [Get Start For Free]() ![Dockit Astro](https://assets.teamosis.com/thumbs/dockit.png) ### Dockit Astro astrodocs [Get Start For Free]() ![Pinwheel Astro](https://assets.teamosis.com/thumbs/pinwheel.png) ### Pinwheel Astro astrosaas [Get Start For Free]() [View All Templates ](https://app.sitepins.com/templates) > I've worked with almost every headless CMS out there. Sitepins is by far the best. Handing projects off to non-technical clients has never been smoother. All my Astro themes now come pre-configured with Sitepins and it's the default CMS for my clients' projects too. ### Christos Founder & Lead Designer, Oxygenna > I wanted to give our marketing team the ability to edit content without them poking me every time. So far, it’s going well. I can finally focus on more complex tasks rather than just changing a heading or triggering a rebuild. ### Somrat Developer Team Lead > I absolutely love the UI and the experience of working with it. The configuration and set-up was simple, smooth and easy. ### Emmanuel Chief Technical Officer > Sitepins looks pretty sweet. Great job. It’s just what I’ve been looking for. ### Jim Mitchell Developer and Tech Blogger > Sitepins looks really nice, it's just what I hoped to find. ### Joakim Freelance Developer ![Christos](/_vercel/image?url=_astro%2Fchirstos.DV2Y3f2T.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Somrat](/_vercel/image?url=_astro%2FSomrat.BwganZp8.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Emmanuel ](/_vercel/image?url=_astro%2FEmmanuel.Bsrg7jKY.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Jim Mitchell](/_vercel/image?url=_astro%2FJim-Mitchell.Dg26QtN6.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Joakim](/_vercel/image?url=_astro%2FJoakim.XmZu6oLf.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Join the teams simplifying content editing with Sitepins. ![Themefisher](/_astro/themefisher.DdObPKXZ.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![GetHugoThemes](/_astro/gethugothemes.D4jOwvUz.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Statichunt](/_astro/statichunt.ogDzivN2.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Uihut](/_astro/uihut.DNlBUx8T.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Zeon Studio](/_astro/zeon-studio.Bn2Zoq8x.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Supernova](/_astro/supernova.DXiL8Uo6.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) FAQs ## Frequent Questions Got questions? We’ve got clear answers to help you get started. How fast can I start editing my Astro site with Sitepins? Does Sitepins work with Astro Content Collections? Do I need to install anything to use Sitepins? Is Sitepins free to use? Have more question? [Contact Us](contact) to inquire more! ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Insights, Updates & Stories URL: https://sitepins.com/blog Updates and insights on building tools for the static web. Sitepins Blogs # Insights, Updates & Stories Updates and insights on building tools for the static web. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) [](/blog/whats-new-in-sitepins-august-2026) #### [What's new in Sitepins — August 2026](/blog/whats-new-in-sitepins-august-2026) - Redwan - August 31, 2026 [![Astro Visual Editor: Give Non-Technical Users Edit Access](/_vercel/image?url=_astro%2Fvisual-editor-for-astro.Ct6sFj2h.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)](/blog/visual-editor-for-astro-websites) [Astro,](/categories/astro)[CMS](/categories/cms) #### [Astro Visual Editor: Give Non-Technical Users Edit Access](/blog/visual-editor-for-astro-websites) - Farhad - August 24, 2026 [![What's New in Sitepins — July 2026](/_vercel/image?url=_astro%2Fwhats-new-in-sitepins-july-2026.CcCEYxeg.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)](/blog/whats-new-in-sitepins-july-2026) #### [What's New in Sitepins — July 2026](/blog/whats-new-in-sitepins-july-2026) - Redwan - August 04, 2026 [![Sitepins CMS is now open source](/_vercel/image?url=_astro%2Fsitepins-open-source-git-based-cms.DJaziaAv.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)](/blog/sitepins-cms-is-now-open-source) [Others](/categories/others) #### [Sitepins CMS is now open source](/blog/sitepins-cms-is-now-open-source) - Farhad - July 28, 2026 [![What is a Git-based Headless CMS? ](/_vercel/image?url=_astro%2Fgit-based-headless-cms.D5iAl43B.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)](/blog/git-based-headless-cms) [CMS](/categories/cms) #### [What is a Git-based Headless CMS?](/blog/git-based-headless-cms) - Redwan - July 27, 2026 [![6 Signs It's Time to Leave WordPress (And What to Use Instead)](/_vercel/image?url=_astro%2Fwordpress-alternatives.BFPmRCaZ.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)](/blog/wordpress-alternatives) [CMS,](/categories/cms)[Web Development](/categories/web-development) #### [6 Signs It's Time to Leave WordPress (And What to Use Instead)](/blog/wordpress-alternatives) - Farhad - July 12, 2026 ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Astro in 2026: Performance, Features, and the Cloudflare Acquisition URL: https://sitepins.com/blog/astro-sitepins-2026 Following Cloudflare's acquisition, Astro 6 Beta introduces great new features. Learn why it's one of the best frameworks for performance-focused developers. # Astro in 2026: Performance, Features, and the Cloudflare Acquisition - Redwan - January 25, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Astro in 2026: Performance, Features, and the Cloudflare Acquisition ](/_vercel/image?url=_astro%2Fsitepins-astro-cloudflare.aCWLHVr0.webp&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) The web development landscape has shifted from “JavaScript everywhere” to a performance-focused approach that delivers exactly what users need. Astro, now part of Cloudflare following its January 2026 acquisition, redefines website building in 2026 with its new v6 Beta, which introduces a redesigned development server that runs applications in the same runtime as production, bridging the dev-production gap. For modernizing stacks or building client sites manageable by non-technical users, Astro excels in performance and pragmatism, especially when paired with CMS tools like Sitepins CMS. ## What Makes Astro Different? Astro shifts web development by shipping minimal JavaScript to browsers via its “islands” architecture. Unlike typical frameworks, it prioritizes zero-JS-by-default for faster loads and better Core Web Vitals. ## What’s New in Astro 6 Beta Astro 6 Beta represents a major architectural shift that eliminates the traditional gap between development and production environments. Here’s what’s new: - **Re-designed dev server**: Leverages Vite’s Environment API and workerd (Cloudflare’s runtime) for identical dev/production behavior. Developers access real Cloudflare Workers features like Durable Objects, KV, R2, and D1 locally without needing mocks. - **Stable Live Content Collections**: Allows runtime data fetching instead of build-time only, perfect for dynamic content like real-time inventory or personalized dashboards. - **First-class Content Security Policy (CSP) support**: Now fully stable, making it easier to build secure websites. This was Astro’s most-requested feature. ## The Cloudflare Acquisition On January 16, 2026, Cloudflare acquired The Astro Technology Company team, bringing all full-time employees under Cloudflare’s umbrella. Astro remains fully open source under the MIT license, with Cloudflare committing to long-term development and the Astro Ecosystem Fund alongside partners like Webflow, Netlify, Wix, and Sentry. Astro supports most UI framework: React, Vue, Svelte, Solid, or others with no lock-in. Benefits include: - Gradual migrations from existing projects - Best-tool selection for specific jobs - Future-proofing as preferences evolve - Easy onboarding regardless of framework background ## Performance Highlights Astro sites often achieve perfect Lighthouse scores through minimal JS, smart bundling, and no hydration by default. Core Web Vitals improve SEO, UX, and conversions. Performance stats: According to our analysis, 60% of Astro sites score “Good” on Core Web Vitals versus 38% for WordPress/Gatsby sites. The zero-JavaScript-by-default approach ensures blazing-fast initial page loads with no massive framework bundles or unnecessary hydration. ## Developer Experience Astro prioritizes developer productivity with modern tooling and intuitive conventions that reduce friction in your daily workflow: - **Content Collections**: Provide type-safe content management with full TypeScript support and autocomplete. - **File-based routing**: Intuitive structure where files in `src/pages` create routes; brackets enable dynamic routes; rest parameters catch remaining segments. - **Reliable HMR**: Preserves state during development, making the development loop feel instantaneous. - **View Transitions API**: Enables smooth, app-like transitions between pages using native browser APIs. - **Built-in Image optimization**: Automatically generates WebP/AVIF formats, responsive variants, and lazy-loads properly. - **Markdown/MDX support**: Integrates components directly into content with remark and rehype plugin support. ## Built for the Modern Web Astro generates semantic HTML for better SEO and accessibility. Static output means search engines can crawl and index content without executing JavaScript. ## Where to Use Astro: Real-World Use Cases Astro excels in content-driven projects where performance directly impacts business outcomes. Major brands like Porsche, IKEA, Unilever, Visa, NBC News, and OpenAI already trust Astro for their web presence. Here’s where it shines: - Marketing sites and landing pages that need to convert - Blogs and content sites where performance impacts engagement - Documentation sites developers enjoy using - Portfolio sites showcasing work without slowdowns - E-commerce storefronts where milliseconds matter for revenue ## The Content Management Challenge Static sites deliver excellent performance and security, but present a familiar problem: how do clients update content without touching Git or redeploying? This gap between static site benefits and practical content management needs is where Sitepins comes in. ## Integration with Sitepins CMS [Sitepins](https://sitepins.com/) CMS is a _git-based headless CMS_ built for static site generators like Astro. Unlike traditional systems requiring databases and servers, it uses a Git-based workflow where client changes automatically commit to your repository and trigger builds. Few Benefits include: - Version control: change review, rollbacks, and complete history - Clean visual editor for clients without code or Git exposure ### Why Sitepins + Astro Works Sitepins bridges the gap between developer workflow and client needs without compromising either side. Here’s what makes the combination effective: - **Visual editing for non-technical users**: Clients get a clean, intuitive interface to edit content and upload images without touching code. You maintain full control over structure and deployment. - **Git-based workflow**: Sitepins commits changes directly to your Git repository, preserving version control. Every content change is tracked, reviewable, and reversible. - **Type-safe content schemas**: Define content models with validation and type safety. Sitepins enforces schemas, preventing clients from breaking sites with invalid data. ### Developer Benefits - No backend to maintain or secure - No database to backup or migrate - No plugin updates or security patches - Sites remain purely static and blazing fast - Content updates trigger existing CI/CD pipelines - Code changes through normal Git workflow ### Client/Editor Benefits - Friendly interface they can actually use - No fear of breaking the site - No technical knowledge required - Access from anywhere with a browser ## Conclusion In 2026, web development is about smart choices benefiting developers and end users. Astro, now backed by Cloudflare’s resources and infrastructure, delivers exceptional performance and developer experience. Sitepins CMS bridges the gap between modern static site architecture and real-world content management needs. Whether building your next client project or considering a framework switch for your agency, you may consider the Astro + Sitepins combination. It’s not about following trends but about choosing tools that make your work better and your clients happier. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/astro-sitepins-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## 7 Benefits of Headless CMS for Modern Web Development in 2026 URL: https://sitepins.com/blog/benefits-headless-cms Explore the benefits of headless CMS for modern web development. From Astro and Hugo compatibility to clean, non-technical client handoffs. # 7 Benefits of Headless CMS for Modern Web Development in 2026 - Redwan - May 19, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![7 Benefits of Headless CMS for Modern Web Development in 2026](/_vercel/image?url=_astro%2Fbenefits-headless-cms.DQhKO-b6.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) A headless CMS separates the content management backend from the frontend presentation layer, delivering content via REST API or GraphQL to any frontend framework. It gives development teams faster builds, cleaner architecture, and safer client handoffs than traditional monolithic platforms. This separation lets developers choose the best tool for each job (Astro for content-heavy static sites, Next.js for hybrid applications, Hugo for blazing-fast builds) without being constrained by the CMS vendor’s templating system. For teams deploying to Netlify, Cloudflare Pages, or Vercel, it removes server-side infrastructure entirely, replacing it with pre-built HTML served from a CDN. **TL;DR:** Headless CMS unlocks framework freedom, faster performance, and safer client collaboration, without the coupling of a monolithic system. **Key Takeaways** - Headless CMS decouples content from presentation, letting you use Astro, Next.js, Hugo, Nuxt, SvelteKit, Eleventy, or Jekyll without compromise. - Static site output combined with CDN delivery (Netlify, Cloudflare Pages, Vercel) eliminates per-request server rendering, improving Time to First Byte measurably. - Git-based headless CMS stores every content change as a Git commit, giving you full version control and rollback without a separate backup system. - Non-technical clients get a visual editor; developers retain complete code control, with no risk of accidental theme or code changes. - For static sites with client handoff requirements, Git-based tools like Sitepins eliminate the database and server infrastructure entirely. ## What Is a Headless CMS? A headless CMS is a content management system that stores and manages content without providing a built-in frontend rendering layer. It exposes content through a REST API or GraphQL endpoint, which any frontend (Astro, Next.js, Hugo, Nuxt, SvelteKit, Eleventy, or Jekyll) can consume at build time or request time. This architecture matters because it removes the tight coupling between content operations and frontend delivery that has historically forced development teams into the constraints of a single vendor’s templating engine. ## How Is Headless CMS Different from a Traditional CMS? A traditional CMS like WordPress bundles content management, templating, and server-side rendering into a single monolithic system. A headless CMS handles only content management, exposing data through an API and delegating rendering entirely to the developer’s chosen frontend. The practical consequence: a WordPress site serves HTML from PHP on every request; a headless setup serves pre-built static HTML from a CDN with no runtime dependency on the CMS. ## The Benefits of Headless CMS The case for headless CMS is not theoretical. It shows up in faster deployments, fewer post-launch support calls, and development workflows that do not require a database administrator. The seven benefits below cover what changes when you move away from a monolithic CMS and why those changes matter for the teams building and maintaining modern websites: ### 1\. Use Any Frontend Framework A headless CMS imposes no opinion on your frontend stack. Use Astro for content-heavy static sites, Next.js for hybrid applications, Hugo for sub-second builds, or SvelteKit, Nuxt, Eleventy, and Jekyll. The content model stays the same regardless. Switching frontends later does not require touching content, which is structurally impossible in WordPress without substantial rework. ### 2\. Faster Page Performance Static output served from a CDN removes per-request server computation entirely. A page on Cloudflare Pages or Netlify delivers Time to First Byte in single-digit milliseconds, compared to the 200–800ms typical of uncached WordPress responses _(Cloudflare, 2024)_. There is no PHP runtime, no database query, and no plugin chain on any page load. The performance gain is structural, not a caching layer applied to an inherently slower system. ### 3\. Better SEO Out of the Box Static HTML pre-built at deploy time and served from a CDN gives headless CMS sites a structural SEO advantage. Faster page loads improve Core Web Vitals scores, Largest Contentful Paint in particular, which Google uses as direct ranking signals. Developers also have full control over semantic HTML output, metadata, canonical tags, and structured data, with no plugin required and no theme overriding markup decisions. ### 4\. Better Developer Experience A Git-based headless CMS fits directly into the workflow developers already use: branch, commit, pull request, merge. Content lives in the same GitHub or GitLab repository as the site code, with no separate database to back up or replicate. Staging environments are Git branches; `git clone` and `npm install` produce a fully working local environment with no database dump required. ### 5\. Safe Client Hand-off In WordPress, the same admin panel where clients edit posts is also where plugins are updated and themes are switched. One wrong click can break the site. A headless CMS eliminates this by design: editors access a visual interface scoped only to content, with no visibility into templates, configuration, or deployment settings. Developers retain full control of the codebase in GitHub or GitLab. ### 6\. Built-In Content Version History In a Git-based headless CMS, every content save is a Git commit. Teams get a complete, timestamped audit trail of every change without additional tooling, and rolling back is `git revert` rather than a database restore. Git-based tools like Sitepins, TinaCMS, Keystatic, and Decap CMS unify code and content history in one repository, a concrete advantage for teams with compliance or audit requirements. ### 7\. It Scales With Your Project A headless CMS setup scales from a solo developer with one client to a 12-person agency managing 40 sites without architectural changes. Role-based access controls let the lead developer decide which editors can publish directly and which must submit for review. Sitepins supports this model across the full range, from a freelancer with a single client to a multi-editor agency team. ## When Should You Use a Headless CMS? Use a headless CMS when the project targets a specific frontend framework (Astro, Next.js, Hugo, Nuxt, SvelteKit, Eleventy, or Jekyll), requires high page performance, or involves handing off content to non-technical editors. It is also the right choice when the same content must serve multiple surfaces from a single model via REST API or GraphQL. Teams deploying to Netlify, Cloudflare Pages, or Vercel will find it a natural fit. ## When Do You Not Need a Headless CMS? Avoid headless CMS when the client needs a large plugin ecosystem, WooCommerce-based e-commerce, or the ability to manage the site entirely without developer support. WordPress or Squarespace are better fits in those cases. Headless also introduces a build step, so if a client requires immediate live edits with no deployment latency (flash sales, real-time pricing), an API-first CMS with server-side rendering or incremental static regeneration is the more practical choice. ## Popular Headless CMS Examples **Git-based (no database, content stored in your repo):** - **Sitepins** Built for non-technical client handoff on static sites (Astro, Hugo, Next.js). Visual editor, no Git knowledge required for editors. - **Decap CMS** Open-source, Netlify-native. Strong Hugo and Jekyll support. Simple YAML-configured editorial UI. - **TinaCMS** Open-source with inline visual editing. Deep Astro and Next.js integration. Schema defined in code. - **Keystatic** Schema-as-code approach, local and GitHub modes. Great for developer-controlled content structures. ​ **API-first (hosted database, content via REST/GraphQL):** - **Contentful** Enterprise-grade, mature ecosystem, strong localization support. - **Sanity** Highly customizable with a real-time collaborative editor (Sanity Studio). Flexible content modeling. - **Storyblok** Visual block-based editor. Popular with Next.js and Nuxt teams. - **Strapi** Self-hosted, open-source. Full REST and GraphQL API. Good for teams wanting backend control. ## Conclusion Headless CMS removes the constraints that monolithic platforms impose on modern development teams. Framework freedom, faster performance, cleaner developer workflows, and safe client handoffs are not incremental improvements over traditional CMS. They are structural advantages that compound over the life of a project. For teams building on Astro, Next.js, Hugo, or any other static site generator, a Git-based headless CMS eliminates the database, the server, and the risk of a client breaking something they should never have had access to in the first place. The architecture fits the way developers already work, and the editorial experience fits the way non-technical clients need to work. That combination is why the shift to headless is not a trend. It is where modern web development has settled. #### FAQ ##### What is the difference between headless CMS and traditional CMS? A traditional CMS like WordPress couples content management, templating, and server-side rendering into one system. A headless CMS manages only content and delivers it via REST API or GraphQL, so the frontend (Astro, Next.js, Hugo) is chosen and changed independently. ##### Is headless CMS good for SEO? Yes. Static output served from a CDN produces faster page loads, improving Core Web Vitals scores that Google uses as ranking signals. It also eliminates render-blocking PHP execution and database queries on every request. ##### Can non-technical users use a headless CMS? Yes, when the CMS provides a visual editor. Tools like TinaCMS, Storyblok, and Contentful offer editorial interfaces that require no knowledge of Markdown, YAML, or Git. ##### What is a Git-based CMS? A Git-based CMS stores content as files (Markdown, JSON, YAML, TOML) in a Git repository rather than a hosted database. Every edit creates a Git commit, giving teams automatic version history and rollback. Sitepins, TinaCMS, Keystatic, Decap CMS are the primary options in the modern web development era. ##### Which headless CMS is best for Astro? The strongest options for Astro are Git-based tools that write Markdown files compatible with Astro’s content collections natively: TinaCMS for open-source inline editing, Keystatic for schema-as-code control, and Sitepins for teams handing off to non-technical editors. ##### Which headless CMS is best for Hugo? Hugo works well with Git-based CMS tools that write Markdown with YAML or TOML frontmatter directly into the Hugo content directory. Decap CMS is the established open-source choice for Hugo on Netlify; Sitepins and Keystatic are the main alternatives. ##### Do I need a database to use a headless CMS? Not with Git-based tools. TinaCMS, Keystatic, Decap CMS, and Sitepins store all content as files in a Git repository with no database required. API-first tools like Contentful, Sanity, and Storyblok use a vendor-managed database, accessed only through their API. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/benefits-headless-cms) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## CMS for SEO in 2026: Architecture, Speed & What to Look For URL: https://sitepins.com/blog/best-cms-for-seo-in-2026 How CMS architecture affects Core Web Vitals, TTFB, and AI search visibility in 2026. Compare Git-based, headless, and traditional CMS options. # CMS for SEO in 2026: Architecture, Speed & What to Look For - Redwan - March 16, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![CMS for SEO in 2026: Architecture, Speed & What to Look For](/_vercel/image?url=_astro%2Fcms-for-seo.BBfOnhiy.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) The best CMS for SEO in 2026 is one that produces clean, crawlable HTML with no JavaScript rendering bottlenecks, stores content in a way that serves AI retrieval, and lets editors publish without engineering support. Git-based CMS tools have pulled ahead of database-driven platforms like WordPress and Contentful for developer-led sites because they eliminate the rendering lag and infrastructure complexity that now actively penalise rankings. The right choice depends on your framework, team size, and publishing workflow. **​** **Key Takeaways** - Git-based CMS tools outperform database-driven CMS platforms on Core Web Vitals because they output static HTML with no server-side rendering delay - WordPress remains the easiest CMS for non-developers but requires significant plugin overhead to reach competitive Core Web Vitals scores in 2026 - Contentful and Sanity are strong for enterprise multi-channel publishing but add API latency and infrastructure complexity that hurts Time to First Byte (TTFB) - AI search visibility now depends on content structure and entity density, not just page speed ​ ## What effect does a CMS have on SEO? CMS architecture matters more in 2026 than it did in 2023 for two reasons. First, Google’s Core Web Vitals (Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS)) are now confirmed ranking factors, and CMS platforms that rely on client-side rendering to assemble pages consistently score worse than static-output platforms. Second, AI Overviews, ChatGPT, and Perplexity now retrieve and cite web content directly. Pages with clean semantic HTML structure, low TTFB, and well-organised headings are more likely to be selected as citation sources. ​ ## How CMS architecture affects Google’s Core Web Vitals Static site generators (Hugo, Astro, Eleventy) paired with a Git-based CMS output pre-built HTML files served directly from a CDN. There is no server-side rendering, no database query, and no PHP execution on page load. The result is TTFB consistently under 50ms on Cloudflare Pages or Netlify, which directly improves LCP scores. WordPress, running on a shared or managed host with a page builder like Elementor or Divi, typically produces TTFB between 200–800ms before caching plugins are applied (WP Rocket, W3 Total Cache). With aggressive caching, WordPress pages can reach competitive scores, but this adds plugin dependency and maintenance overhead that grows with site complexity. API-first headless CMS platforms like Contentful, Sanity Studio, and Storyblok decouple content from the frontend but require the frontend framework (Next.js, Nuxt, Remix) to fetch and render content at request time or build time. Build-time rendering produces static pages equivalent to Hugo or Astro; request-time (SSR) rendering reintroduces the TTFB problem. ​ ## CMS Comparison: SEO Performance at a Glance CMS Architecture Typical TTFB Core Web Vitals difficulty Best for Key SEO trade-off **Sitepins** Git-based / static output <50ms (CDN) Easy Hugo/Astro sites, developer-led teams Limited to static site frameworks **TinaCMS** Git-based / React inline editing <50ms (CDN) Easy Next.js, Astro, Docusaurus Requires React knowledge to customise **Keystatic** Git-based / local-first <50ms (CDN) Easy Astro, Next.js, Remix Newer ecosystem, fewer integrations **WordPress** Monolithic / server-rendered 200–800ms (uncached) Moderate–Hard Non-developers, plugin-heavy sites Requires caching stack to compete **Contentful** API-first headless Depends on frontend Moderate Enterprise, multi-channel API latency; SSR adds TTFB **Sanity Studio** API-first headless Depends on frontend Moderate Developer teams, custom schemas GROQ query complexity at scale **Ghost** Node.js / server-rendered 100–300ms Moderate Publishers, newsletters Self-hosted complexity; limited static output **How to read this table:** the right CMS depends on your framework, team, and deployment setup. Git-based tools suit static sites; API-first tools suit multi-channel or enterprise needs; WordPress suits non-technical teams comfortable managing a plugin stack. ​ ## A Few CMS Tools in Brief ### Sitepins A Git-based visual CMS built specifically for Hugo and Astro. Content is stored as Markdown or MDX files in your repository with no external database. It is not designed for WordPress sites, React-only projects, or enterprise content modelling. ### TinaCMS A Git-based CMS with live inline editing, best suited for Next.js and Astro. TinaCMS 2.x added structured field validation and block-based layouts, making it a solid choice for design-system-driven teams. ### WordPress 6.x Powers approximately 43% of all websites as of early 2026 (W3Techs, 2026). Its SEO ceiling is high with the right stack: Yoast SEO or Rank Math, WP Rocket, and Cloudflare. The trade-off is ongoing plugin maintenance and hosting overhead. ### Contentful A widely used API-first headless CMS for enterprise use. Its Growth plan starts at $300/month as of Q1 2026, covering 5 users and 2 environments. It suits multi-channel publishing but adds cost and complexity that smaller static sites do not need. ​ ## What to Look for in a CMS that’s Optimized for SEO Not every CMS is built with SEO in mind. Before committing to a platform, there are a few things worth verifying. ### Performance - Outputs static HTML or CDN-cached pages with TTFB under 100ms, no custom caching configuration required - Handles image optimisation natively: WebP conversion, responsive `srcset` attributes, and lazy loading built in, not plugin-dependent ### Content Structure - Enforces a structured content schema with field-level validation for title, meta description, canonical URL, and Open Graph tags - Generates sitemaps and robots.txt automatically, or makes them configurable without a third-party plugin - Produces clean semantic HTML with no injected wrapper divs, inline styles, or JavaScript-dependent rendering ### Easy to Overlook - Bot accessibility: GPTBot, ClaudeBot, PerplexityBot, and Google-Extended should not be blocked by the CMS’s default configuration. Being crawled is a prerequisite for being cited. - Editor access: non-technical editors should be able to publish and update content without touching the repository or waiting on a developer ​ ## Conclusion CMS choice affects SEO primarily through page speed, HTML structure, and crawlability. Git-based tools have a technical advantage for static sites because they eliminate server-side rendering and database overhead entirely. But that advantage only matters if the content itself is structured for retrieval. No CMS guarantees rankings or AI citations on its own. The platforms covered here each suit different teams, frameworks, and use cases. Choosing the right one comes down to your stack, your editors, and how much infrastructure you want to maintain. Start there, then focus on the content. ​ ## FAQ ### When does it make sense to use Sitepins? Sitepins is a practical fit if you are already building with Hugo or Astro and need non-technical editors to manage content without a Git workflow. It is not the right choice for WordPress sites, React-heavy projects, or teams that need enterprise content modelling. TinaCMS, Keystatic, or Contentful are better suited to those cases. ### Does WordPress still rank well in 2026? Yes, with the right stack: WP Rocket, Cloudflare CDN, and Yoast SEO or Rank Math. The gap with static-output tools has narrowed, but maintaining that stack adds ongoing overhead. ### Does CMS choice affect AI search citations? Indirectly. CMS choice affects crawlability, but citation eligibility is driven by content structure, entity density, and specificity. Any CMS can produce GEO-ready content with the right writing approach. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/best-cms-for-seo-in-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## 6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026 URL: https://sitepins.com/blog/decapcms-alternatives Looking for a Decap CMS alternative? Here are 6 of the best Git-based and visual CMS options for static site generators like Astro, Hugo, and Next.js — ideal for developers, agencies, and clients. # 6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026 - Farhad - June 10, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/_vercel/image?url=_astro%2Fdecapcms-alternatives.CELW-JIt.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Why Look Beyond Decap CMS? Decap CMS (previously known as Netlify CMS) was one of the first Git-based CMS options for static sites. It helped developers give clients a simple way to edit content visually while keeping everything versioned in Git… But it’s 2026, and the landscape has shifted: - Netlify officially stopped supporting it. - The UI feels outdated compared to newer tools. - No longer actively maintained or adding new features. - Community activity has slowed down significantly. - Better, easier, and more modern tools have emerged. If you’re building client sites with Astro, Hugo, Next.js, 11ty, or SvelteKit and want to hand off content editing to non-developers, here are the 6 best Decap CMS alternatives to consider. ### Sitepins ![sitepins](/images/blog/sitepins.webp) Sitepins is made for developers and agencies who want to give clients a clean UI to manage site content without touching code. It works out of the box. Unlike other tools, no config or manual schema setup is required. Just connect your GitHub repo, select your content folder, and go. What makes it stand out: - Zero setup. No config files or field definitions needed. - Web-based visual editor with intuitive UI. - Mobile Friendly - Version Rollback & Restore - Live Preview System - Native Multilingual Support (upto 12 Languages) - Collaborative Editing - Works with modern SSGs like Astro, Hugo, Next.js, 11ty, and SvelteKit. Pricing: - Free plan available - Premium starts at $12/month; $10/month (annual plan) - Always free for NGOs and charities [Try Sitepins for Free](https://sitepins.com) ### Sveltia CMS ![svelti](/images/blog/sveltia.png) Sveltia CMS positions itself as a modern rewrite of Decap CMS with better performance, modern UI, and built-in i18n. It even lets you reuse many existing Decap config files. Pros: - Lightweight - Built-in translation and i18n - Fast performance and small bundle size Cons: - Still evolving, limited community compared to older tools Pricing: - Free and open source [Visit Website](https://github.com/sveltia/sveltia-cms) ### Keystatic ![keystatic](/images/blog/keystatic.png) Keystatic is designed for developers who want structured content editing inside their codebase. It supports editing Markdown, JSON, and YAML files through a web-based admin UI. Schemas are defined using TypeScript, and content can be stored locally or in GitHub. Pros: - Developer-friendly with strong TypeScript support - Local-first and Git-based - Can be used with or without cloud - Open source and flexible Cons: - Requires coding knowledge to set up - Limited visual editing Pricing: - Free for solo/local or GitHub use (up to 3 users) - Pro starts at $10/month per team - $5/user/month after 3 users (Cloud plan) [Visit Website](https://keystatic.com) ### Outstatic ![outstatic](/images/blog/outstatic.png) Outstatic gives you a simple admin dashboard to manage markdown content and commit changes directly to your GitHub repo. It’s open source and designed for quick publishing with zero backend. Pros: - Fast and easy to set up - Free and open source - AI-assisted content creation - Direct GitHub integration Cons: - GitHub login only - No multi-user or approval workflows - Built mainly for Next.js Pricing: Free and open source [Visit Website](https://outstatic.com) ### Tina ![tina](/images/blog/tina.png) Tina CMS is a powerful React-based CMS that stores content in Git. It offers both self-hosted and cloud versions and is popular in more complex setups where content structure is known in advance. Pros: - Git-backed, React-native editing - Flexible content modeling - Rich editing interface - Open-source with cloud backend option Cons: - Requires manual schema definition - Setup can be complex for small projects or non-React stacks Pricing: - Free for open source and personal use - Paid plans start at $29/month [Visit Website](https://tina.io) ### CloudCannon ![cloudcannon](/images/blog/cloudcannon.png) CloudCannon is a commercial Git-based CMS with a visual interface, team workflows, and built-in hosting. It’s popular among agencies handing off polished sites with a visual editor baked in. Pros: - Visual editor with Git version control - Team access, approval workflows, live previews - Hosting and deployment included (optional) Cons: - Not open source - Paid plans required for full feature set [Visit Website](https://cloudcannon.com) ## Conclusion Decap CMS helped popularize Git-based content workflows. But in 2026, there are better options depending on your project needs. Whichever you choose, these tools let you build fast, secure static sites while giving editors the experience they expect from a modern CMS. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/decapcms-alternatives) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## EmDash vs Sitepins: Best Headless CMS for Astro URL: https://sitepins.com/blog/emdash-vs-sitepins-headless-cms-for-astro Compare EmDash and Sitepins as modern headless CMS options. Explore the strengths, limitations, and ideal use cases of each for Astro websites. # EmDash vs Sitepins: Best Headless CMS for Astro - Farhad - April 05, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![EmDash vs Sitepins: Best Headless CMS for Astro](/_vercel/image?url=_astro%2Femdash-cms-vs-sitepins-cms.Djf6zKrT.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) EmDash and Sitepins both live in the headless CMS space, but they optimize for very different **control planes.** EmDash is a serverless, database‑backed, Astro‑first CMS running on Cloudflare Workers, D1, and R2, while Sitepins is a Git‑based visual layer on top of repositories on GitHub (and other Git providers) with first‑class Astro support. EmDash feels closer to WordPress or Sanity, whereas Sitepins is an alternative to TinaCMS, Decap CMS or Cloudcannon embedded into your existing Git workflow. ## EmDash CMS vs Sitepins CMS at a glance Criteria EmDash CMS Sitepins CMS Primary model Serverless, database-backed headless CMS on Cloudflare Workers, D1, and R2. Git-based headless CMS layered on GitHub repositories. Framework Support Astro Astro, Hugo, NextJs, 11ty, Jekyll and other SSGs. Content storage Portable Text JSON in SQL tables via Kysely (SQLite, D1, PostgreSQL, etc.). Markdown/MDX and JSON config files in the repo (e.g., src/content, theme.json). Plugins & extensibility Sandboxed plugins in Worker isolates with explicit capability manifests. Extensibility via repo-level customization; no separate plugin runtime. Hosting & infra Optimized for Cloudflare; also runs on Node.js with SQLite. Works with any Git-based CI/CD (Vercel, Netlify, GitHub Pages, etc.). Editor experience WordPress-like admin, TipTap editor, roles (Administrator, Editor, Author, Contributor). Visual editor mapped to folders/files; configurable sidebar groups and headings. Governance & audit DB-backed revisions and audit logs; capability-based plugin security. Git history and pull requests as the audit trail. Ecosystem maturity Early Beta (v0.1.0); plugin/theme ecosystem still forming. Full Release; 2+ years of refinement and 1,000+ active users. Integration Effort High. Requires modifying code. Zero. Connects to existing repositories with no code changes. Project Structure Strict; must follow EmDash conventions to utilize schema and plugins. Flexible; you define your own code structure. ## When EmDash is the right CMS choice EmDash wins for TypeScript‑heavy teams who want Cloudflare‑native infrastructure, Portable Text content, and a plugin model closer to WordPress but sandboxed like Cloudflare Pages Functions. Think: a SaaS product company migrating from WordPress or Drupal, an agency standardizing on Astro + Cloudflare for clients, or a platform team used to tools like Sanity, Strapi, and Contentful but wanting to collapse infra onto D1/R2. It is especially attractive if you care about fine‑grained plugin capabilities, MCP/agent integration, and running many low‑traffic sites that benefit from “scale‑to‑zero” economics on Cloudflare Workers. ## When Sitepins is the right CMS choice Sitepins wins for Git‑native teams who already ship with GitHub, Vercel, or Netlify and want a clean WYSIWYG layer on top of Markdown/MDX content collections in Astro without adding a separate database. It is a strong fit for small team, solo developers, and documentation teams used to GitHub pull requests, where authors can log into Sitepins for a visual editor while developers keep full control of the repo. If you value Git‑based audit trails and minimal infrastructure (no D1/R2, no separate auth stack), Sitepins is ideal choice. If a Git‑native, repo‑first workflow sounds closer to how your team already ships, spin it up in practice instead of theory. Try Sitepins for free and see how it fits your project. 👉 [**Try Sitepins for free.**](https://sitepins.com/pricing) ​ ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/emdash-vs-sitepins-headless-cms-for-astro) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What is a Git based Headless CMS? URL: https://sitepins.com/blog/git-based-headless-cms A secure architecture that uses Git to store content as files, eliminating the need for databases for speed and reliable version control. # What is a Git based Headless CMS? - Redwan - July 27, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What is a Git-based Headless CMS? ](/_vercel/image?url=_astro%2Fgit-based-headless-cms.D5iAl43B.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) A **Git-based Headless CMS** is a content management tool that lets you create, edit, and update your website contents using a simple visual interface. It is a modern architecture that decouples content from the website’s design, storing everything in a Git repository instead of a proprietary database. Every time you edit something, the CMS automatically registers it as a Git commit, saving that content as flat files (Markdown, JSON, or YAML). This makes managing content safer, more transparent, and especially friendly for teams working with modern stack. This guide is designed for web-tech enthusiasts, aspiring developers, and mid-range professionals looking to understand Git-based headless CMS architecture, its benefits, and how to choose the right solution for their projects. Whether you’re building a personal blog, documentation portal, or managing content for multiple static sites, this comprehensive guide will help you make informed decisions. ## TL;DR: What you need to know - **Storage:** Content and code are saved in your Git provider (e.g. GitHub, GitLab) - **Workflow:** Every content update triggers a version control commit and a site rebuild - **Security:** Creates static files, eliminating the database vulnerabilities found in traditional CMSs - **Best For:** Developer-focused teams, documentation sites, and high-performance static websites. - **Future-Proof:** Your content is stored in open formats (Markdown/JSON), preventing vendor lock-in. ## What does “Git-Based” mean? Git was designed to track changes in source code, and this same power applies to content management. Every edit creates a commit with metadata including who made the change, when it happened, and what exactly was modified. This level of control eliminates the pain of losing content or breaking your live site. If something goes wrong, you can always roll back to a previous version. Here’s a list of things you can do in a git environment: - **Review** the complete history of any piece of content - **Compare** different versions side-by-side - **Revert** to previous states with a single click - **Create** branches to test content changes before publishing - **Merge** collaborative edits without conflicts ## How the Git Architecture Works? Unlike traditional systems that build pages on the fly when a user visits, a Git-based CMS pre-builds the site whenever content changes. Here’s the step-by-step workflow: - **Content Creation:** An editor logs into the CMS interface and saves a new blog post. - **Commit:** Behind the scenes, the CMS takes that content, converts it into a file (like `blog-post.md`), and pushes it to your Git repository. - **Trigger:** Your hosting provider (like Vercel or Netlify) detects this new commit. - **Build:** A Static Site Generator (like Hugo, Jekyll, or Next.js) automatically rebuilds the entire website, incorporating the new content. - **Deployment:** The updated static files are deployed to a global Content Delivery Network (CDN), making the changes live instantly. ## What is a “Headless CMS”? Traditional monolithic CMSs like Wordpress or Drupal bundle everything together: content storage, the editing interface, and front-end rendering. While functional, monolithic systems present several challenges: - **Tightly Coupled Data:** Content is locked into platform-specific database structures. - **Limited Versioning:** History is often restricted to individual posts rather than the entire site state. - **High Maintenance:** Requires constant database server management and security patching. A Headless CMS breaks the limitations of that monolith by removing the front-end entirely, hence the term “headless.”. It acts as a backend-only content repository that delivers data dynamically through API calls to your frontend. Your website (built with React, Astro, Next.js, or Hugo) fetches the content it needs at build time or runtime and renders it however you’ve designed. ## How They Work Together? A Git-based Headless CMS takes it a bit further and eliminates the limitations. Instead of using a traditional cloud database managed via an API, it uses Git repositories as the primary storage mechanism. Your content is stored as files, typically Markdown, JSON, or YAML directly in your project repository alongside your code. When you create or edit content through the CMS interface, it automatically translates those changes into Git commits. Which means: - **Complete History:** Every blog post, page update, and image upload becomes part of your project’s version history, tracked and reversible. - **Developer Friendly:** Content lives where the code lives, allowing for seamless branching and merging. - **No Database Overhead:** You remove the need for constant database server management and security patching. ## Git-Based vs. API-Based CMS: What’s the Difference? As we have discussed, there are two types of headless CMS architectures. The core difference between these two architectures lies in their fundamental approach to data storage and content delivery. - **API-Based Headless CMS** stores content in a proprietary database and delivers it dynamically through API calls made by the frontend, offering flexibility but relying on the database’s security and uptime. - **Git-Based Headless CMS** eliminates the database entirely, storing content as flat files in a Git repository. Content changes trigger a Static Site Generator (SSG) to pre-build the entire site, resulting in superior security and increased performance. While both systems are headless, they handle data storage and delivery very differently. ### Feature Comparison Feature Git-Based CMS API-Based CMS **Data Storage** Flat files (Markdown/JSON) stored in a Git repository Database hosted by the vendor **Content Delivery** Push-based: Changes trigger a rebuild (Static Site Generation) Pull-based: Content is fetched via API calls on load **Version Control** Native Git history: You can roll back every single content change Vendor-limited: Relies on the vendor’s “Undo” history limits **Security** High: No database to hack; files are static Moderate: Relies on API security and endpoint protection **Best For** Static websites, documentation, and developer-heavy teams Enterprise apps, omnichannel (web + mobile), and high-frequency updates ## Why Choose a Git-Based CMS? ### For Content Teams The editor never has to see a terminal or understand Git. They get the familiar experience they need: - **Intuitive Editing:** Use WYSIWYG or Markdown editors. - **Content Governance:** Use “Draft → Review → Publish” stages with clear audit trails. - **Safety:** Accidental deletions can be recovered instantly through the version history. ### For Developers Treating content as code simplifies your entire infrastructure: - **Zero Infrastructure:** No database servers or API keys to manage across environments. - **Local Development:** Work completely offline. Your content is just a set of files in your repo. - **Framework Agnostic:** Works with React (Next.js), Vue (Nuxt), Astro, Hugo, or SvelteKit. ### For Organizations - **No Vendor Lock-in:** Your content is in your repo. If you leave the CMS, your data stays with you. - **Security:** With no database to hack, your attack surface is nearly zero. - **Performance:** Static files served from a CDN scale infinitely and load instantly. ## Potential Limitations to Consider To ensure you select the right tool, it’s important to understand where this architecture might struggle. - **Long Build Times:** Since the site must be rebuilt every time content changes, this approach performs poorly for sites with thousands of pages. Modern SSGs like Hugo can build 1,000 pages in under a second, but slower frameworks like Gatsby might take several minutes. - **Asset Management:** Handling heavy media libraries (large video files or thousands of high-resolution images) inside a Git repository can bloat the repo size and slow down cloning. - **Real-Time Content:** This architecture is not suitable for dynamic content that changes second-by-second (like stock prices or live comments) because of the build-time latency. ## Git-Based CMS Tools If you’re looking to evaluate tools in this space, these are currently the most recognized options in the market: - [Sitepins](https://sitepins.com/) **:** An open-source git based CMS tool built for non-technical clients and teammates. It provides a visual editor to manage sites made with SSGs like Astro, Next.js, and Hugo - [Decap CMS](https://decapcms.org/) (formerly Netlify CMS): An open-source, React-based CMS that wraps around your Git workflow. - [TinaCMS:](https://tina.io/) Focuses on visual editing, allowing you to click and edit directly on the live preview of your site. - [CloudCannon:](https://cloudcannon.com/) A hybrid tool that acts as a Git-based CMS but offers strong support for non-technical editors and agency workflows. > Want to know which is the right CMS tool for you? [Read this](https://sitepins.com/blog/headless-cms-tool-for-static-site)​ ## Conclusion A Git-based headless CMS eliminates the “infrastructure tax” of traditional web builds. Since content follows your code workflow, features like pull requests and rollbacks work out of the box. ​[Sitepins](https://sitepins.com/) bridges the gap between developer power and client simplicity. You can connect your GitHub repository, configure which content fields are editable, and share a login link with your client. They edit through a clean dashboard. Every change becomes a commit. The site rebuilds. Sitepins ensures every update is tracked, versioned, and deployed automatically. - **Developers:** Keep your Git-driven workflow s and reproducible builds - **Clients:** Use a clean, visual dashboard with zero training required. ### Frequently Asked Questions (FAQ) #### Is a Git-based CMS free? Yes, most Git-based headless CMS options are free to use. Sitepins is open source, so people can either self-host it if they’re capable of supporting the cost of hosting and maintenance, or subscribe to the free Hobby tier on Sitepins Cloud instead (up to 3 sites, with 1 private repo allowed). Paid plans start at $12/month for the Pro tier, aimed at individuals who need more sites and features. Decap CMS and TinaCMS are also free. #### Do I need to know how to code to use one? No. While the backend is code-heavy, the actual CMS interface usually looks just like a standard text editor. Writers and marketing teams can use the visual dashboard without ever seeing a line of code or a Git command line. #### Do editors need a GitHub account? Depends. CMS like Sitepins handles the authentication behind the scenes. Editors log in to the CMS, and the CMS talks to GitHub for them. #### Does using a Git-based CMS limit my choice of frontend framework? No, it does not. Git-based CMSs are designed for composable architecture and are compatible with any modern front-end framework that uses a Static Site Generator (SSG). This includes popular options like Next.js, Gatsby, Hugo, and Astro. #### What happens to my content if my Git-based CMS provider stops functioning? Your content is safe. Because it’s stored directly in your own GitHub or GitLab repo, typically as Markdown or MDX files (though HTML, JSON, YAML, TOML, TS, and JS are also supported), you can simply point a different Git-based CMS at your files or edit them manually. There’s no vendor lock-in ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/git-based-headless-cms) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Git Based vs. API First Headless CMS: The Ultimate Comparison URL: https://sitepins.com/blog/git-based-vs-api-based Git-based vs API-first headless CMS: understand the architectural differences, pros and cons, and which approach fits your project best. # Git Based vs. API First Headless CMS: The Ultimate Comparison - Redwan - February 23, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Git-Based vs. API-First Headless CMS: The Ultimate Comparison ](/_vercel/image?url=_astro%2Fgit-based-cms-vs-api-first-cms.DupST9ld.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) The primary difference between Git-based and API-first systems is where your content is stored and how your team manages it every day. An API-first Headless CMS stores content in a hosted database and delivers it through REST or GraphQL or runtime. While a Git-based CMS stores your content as files in your Git repository, such as Markdown, YAML, JSON, or TOML and uses your existing version control workflow to manage changes and work naturally with static site generators. Both are legitimate approaches, but they suit fundamentally different architectures. ## Defining the Two Approaches The right choice between the two approaches depends on your infrastructure preferences, team workflow and whether you need real-time content updates or can work with build-time content generation. However, both are “headless”, meaning they don’t dictate how you display content. But the underlying architecture shapes everything from deployment to collaboration. In a **Git-based CMS**, when an editor makes a change through the CMS interface, it commits that change to Git. Your site pulls content from these files at build time, usually through a static site generator like Hugo, Astro, or Next.js. The git repo becomes your single source of truth (SSOT) for both code and content. Git-based CMS tools include: - Sitepins - CloudCannon - Decap CMS (formerly Netlify CMS) - Tina CMS - Keystatic > For a detailed, comprehensive guide on Git-based headless CMS, read this: [What is a Git Based Headless CMS?](https://sitepins.com/blog/git-based-headless-cms) When working in an **API-first CMS** Editors work in a web-based interface that writes to the database. Your front-end application fetches content from the API, either at build time, request time, or through a hybrid approach. In that case, database becomes your SSOT for content, while your code lives separately. API-first CMS tools include: - Contentful - Sanity - Strapi - Directus - Payload CMS. ## How Content Flows: Git-Based vs API-First Headless CMS ### Git-Based Content Flow 1. Editor opens the CMS interface 2. Creates or modifies content 3. CMS commits changes to Git repository 4. Commit triggers a build (via webhook or CI/CD) 5. Static site generator reads files from Git 6. Generator builds static pages 7. Static pages deploy to CDN or static host 8. End users receive pre-built HTML **Content becomes HTML at build time.** This means a delay between “save” and “live” but it also means your site serves pre-rendered pages that load instantly. ### API-First Content Flow 1. Editor opens the CMS interface 2. reates or modifies content 3. CMS writes changes to database 4. Content is immediately available via API 5. Front-end requests content (build time or runtime) 6. API responds with JSON/GraphQL data 7. Front-end renders content 8. End users receive rendered result **Content can be fetched at build time (static), request time (dynamic), or incrementally (ISR/DPR).** This flexibility is powerful but adds architectural complexity. ## Git-Based vs API-First Headless CMS: Detailed Comparison Aspect Git-Based CMS API-First Headless CMS **Content Storage** Files in Git (Markdown, YAML, JSON) Database (PostgreSQL, MongoDB, etc.) **Content Access** Read files from repository HTTP API calls (REST/GraphQL) **Version Control** Native Git history on every change Varies (some have versioning, many don’t) **Publishing Speed** Requires build (seconds to minutes) Instant API updates **Infrastructure** Git provider + static hosting Database + API server + hosting **Operational Complexity** Low (just Git + static host) Medium to high (manage API, DB, auth) **Cost at Scale** Very low (static bandwidth is cheap) Moderate to high (API calls, database, hosting) **Developer Workflow** Integrated with code repository Separate content API **Content Branching** Git branches (native) Limited or manual implementation **Offline Editing** Possible (clone repo, edit locally) Requires internet connection **Content Relationships** Manual (references between files) Database relationships (easier) **Multi-environment Setup** Git branches per environment Separate database instances **Rollback Capability** Git revert (instant, complete) Depends on platform (often limited) **Security Surface** Minimal (static output) Larger (API, auth, database) **Real-Time Updates** No (build required) Yes (content updates instantly) **Multi-Channel Delivery** Build for each channel separately Single API serves all channels ## Git-Based vs. API-First Pros and Cons ### Git-Based: #### Pros - **Version control is built-in and comprehensive.** Every content change is a Git commit with a full audit trail. You can see exactly who changed what, when, and why (if they wrote a commit message). Branching lets editors work on drafts in separate branches before merging to production. - **Infrastructure is simple and cheap.** You need a Git provider (GitHub, GitLab, Bitbucket) and static hosting (Netlify, Vercel, Cloudflare Pages, or even S3). No databases to manage, no API servers to scale, no complex authentication systems. - **Content and code live together.** Developers can update both content and code in the same pull request. Content changes flow through the same CI/CD pipeline as code changes, ensuring consistency. - **Performance is excellent by default.** Static pages served from a CDN load instantly. No database queries, no server rendering on every request, no API latency. - **Security risks are minimal.** Static sites have a tiny attack surface. No database means no SQL injection. No server-side code execution means no remote code execution vulnerabilities. #### Cons - **Publishing isn’t instant.** Every content change triggers a build, which can take seconds to several minutes depending on site size. For a news site publishing breaking content, this delay is unacceptable. - **Content relationships are manual.** Linking content across files requires manual references. There’s no database enforcing referential integrity. If you rename a file, you need to update references manually or with build-time checks. - **Non-technicals might find Git concepts confusing.** Even with a friendly CMS interface hiding the complexity, concepts like branches, commits, and merge conflicts can be intimidating for pure content teams. - **Querying content is limited.** You can’t run complex queries against Markdown files the way you can against a database. Filtering, sorting, and searching happen at build time, not query time. - **Real-time features are difficult.** If you need user-generated content, comments, personalization, or anything that updates without a build, you need to add a separate backend service. ​ ### API-first: #### Pros - **Content updates are instant.** The moment an editor hits “publish,” the content is available via the API. No build step, no waiting. This matters for news, e-commerce, or any scenario where timeliness is critical. - **Content relationships are powerful.** Database-backed systems handle complex content models with references, one-to-many relationships, and join queries. You can build sophisticated content structures more easily. - **Multi-channel delivery is natural.** A single API can serve your website, mobile app, digital signage, and anything else that can consume JSON. Create once, deliver everywhere. - **Rich querying is built-in.** Most API-first platforms offer powerful filtering, sorting, search, and aggregation. You can fetch exactly the content you need with a single API call. - **Flexible rendering strategies.** You can render at build time (SSG), request time (SSR), incrementally (ISR), or mix approaches. Next.js and similar frameworks make hybrid rendering straightforward. - **Real-time features are easier.** User-generated content, comments, personalized experiences, and dynamic data fit naturally since you’re already running a backend. #### Cons - **Infrastructure is more complex.** You’re managing an API server, a database, authentication, and potentially separate hosting for your front-end. More moving parts mean more things that can break. - **Costs scale with usage.** API calls, database queries, and hosting for dynamic services cost more than serving static files. At high traffic, these costs can become significant. - **Version control requires extra work.** Most API-first platforms don’t have Git-level versioning built-in. Some offer version history as a feature, but it’s not as comprehensive or standard as Git. - **Developer workflow is split.** Content lives in one system (the CMS database), code lives in another (your repository). This separation can make it harder to coordinate changes or ensure consistency. - **Security surface is larger.** You’re exposing an API with authentication, managing database security, and handling more potential attack vectors than a static site. - **Performance requires optimization.** Without caching layers, API-backed sites can be slower than static sites. You need to think about cache invalidation, CDN strategies, and API performance. ​ ## When to Choose Git-Based CMS **Choose a git-based CMS when:** - Your content doesn’t need instant publishing (a few minutes delay is acceptable) - Your team already uses Git and understands version control. - You value simplicity and low operational overhead. - You need a cost-effective hosting and infrastructure solutions. - Security and performance are top priorities. - You’re building a site ranging from few hundred to a few thousand pages. - Content and code are closely related (documentation, developer blogs, marketing sites) - You want complete content history and easy rollbacks. - No vendor lock-in. So you can switch CMS providers or hosting platforms whenever you want. **Ideal use cases:** marketing websites, documentation, blogs, agency client sites, developer portfolios, project websites, landing pages. ## When to Choose API-First Headless CMS **Choose an API-first headless CMS when:** - Content must publish instantly with no build delay - You’re delivering content to multiple channels (web, mobile, IoT) - Your content model has complex relationships - You need advanced querying, filtering, and search - Your team isn’t comfortable with Git workflows - You want flexibility in rendering strategies (SSG, SSR, ISR mixed) - You’re building an application with real-time or user-generated content - You have the infrastructure expertise to manage APIs and databases **Ideal use cases:** e-commerce, news sites, mobile apps, multi-platform content delivery, SaaS products, complex web applications, large-scale sites with thousands of pages. > For a comprehensive list and detailed comparison of CMS tools, check out: [Choosing the Right CMS Tool for Your Static Site](https://sitepins.com/blog/headless-cms-tool-for-static-site) ## Combining Both Approaches Some projects use a git-based CMS for marketing pages and documentation while using an API-first CMS for product data or user-generated content. Next.js makes this easy: fetch some content from files and other content from APIs. You could even use both for different content types on the same site. Blog posts in Markdown files (git-based), product catalog from an API (API-first). The lines are also blurring. Some git-based platforms now offer API access to content. Some API-first platforms offer Git sync features. The categories help you understand architectural tradeoffs, but real-world implementations often blend approaches. ## Making Your Choice - **Start with your publishing requirements.** If you need instant content updates, API-first is the clearer choice. If you can accept a build step, git-based offers simplicity and performance. - **Consider your team’s skills.** If your developers love Git and your workflow is already Git-centric, a git-based CMS feels natural. If Git seems like unnecessary complexity, an API-first platform with a familiar database-backed interface makes more sense. - **Evaluate your infrastructure comfort.** Are you prepared to manage databases, APIs, and authentication? Or do you prefer the simplicity of static hosting? Both are valid, but they require different skill sets. - **Think about content complexity.** Simple, document-based content fits naturally in files. Highly relational content with complex queries works better in a database. Neither approach is objectively better. They solve different problems. Choose based on your specific needs, not on what’s trendy or what you’ve heard is “best.” The best CMS is the one that fits your workflow and lets your team ship great content without fighting the tools. Sitepins fits perfectly here if you’re building an Astro, Hugo, or Next.js static site and want a simple way to let non-technical editors manage content without leaving the Git workflow, it gives you the best of both worlds. ​[**Try Sitepins for FREE ➡**](https://sitepins.com/pricing)​ ​ ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/git-based-vs-api-based) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Choosing the Right CMS Tool for Your Static Site URL: https://sitepins.com/blog/headless-cms-tool-for-static-site Discover the perfect CMS for your static site. Learn the key differences between Git-based and API-based headless architectures to boost speed and security. # Choosing the Right CMS Tool for Your Static Site - Redwan - November 18, 2025 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Choosing the Right CMS Tool for Your Static Site](/_vercel/image?url=_astro%2Fheadless-cms-git-based-api-first.CJB43JNU.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Whether you’re a Web developer needing to hand off a beautiful site so your non-technical client can seamlessly edit their own content, a CTO requiring a dedicated tool for the marketing team to efficiently manage the company website, or just a blogger seeking a simple, secure editor to focus entirely on writing without dealing with complex code or frustrating server setups, you need a Content Management System (CMS). The challenge, of course, is knowing which CMS to choose from the countless options out there. Don’t worry; we have analyzed the landscape to help you find the perfect solution for your specific needs. In this article, we will explore how to select the perfect CMS tool required to maintain your static site. ## Understanding the Shift From Monolithic to Headless A Content Management System or CMS is an essential software designed to simplify the creation, management, and modification of digital content on a website without requiring specialized technical knowledge. While traditional or Monolithic CMS (like WordPress or Drupal) manages both the content and the front-end presentation in one unified system, modern development favors Decoupled or Headless CMS. Today we are going to be focusing on the Headless CMS and explore it further. > For a broader comparison of other headless static CMS on the market, see the [Decap CMS alternatives and headless CMS roundup](https://sitepins.com/blog/decapcms-alternatives) ### What is a Headless CMS? A Headless CMS is a content management system that provides a backend interface for content creation, storage, and management (the body), but intentionally lacks a dedicated frontend presentation layer (the head). Basically, a Headless CMS separates the content- which it stores in a structured database- from the presentation layer, making the content accessible via APIs to any platform (websites, mobile apps, IoT devices), thus offering greater flexibility, speed, and security, especially when paired with a Static Site Generator (SSG). In simple terms, it’s a CMS that treats content as pure, queryable data, focusing solely on managing that content without dictating how it looks or where it’s displayed To manage and deliver content, the Headless CMS architecture is primarily divided into two major types: the **API-Based CMS and the Git-Based CMS.** ## How to Know Which Headless CMS Architecture fits your needs? Both Git-based and API-based systems effectively serve the Composable Web Architecture, but they cater to fundamentally different core needs. The choice between them depends entirely on whether your priority is workflow integrity, security, and developer control (Git-based) or omnichannel distribution, real-time updates, and complex data relationships (API-based). Let’s dive further into the primary differences between a **Git-based CMS** and an **API-based CMS**: ### Git-Based CMS: Control and Simplicity This architecture is best when your main focus is website performance, security, and tight integration with the developer workflow. This focus means the content is treated as versioned files- Markdown, YAML, or JSON that reside directly within your source code repository (Git). The Git-based CMS excels in environments where the final output is a secure, static website, as this approach provides built-in version control for every content change and eliminates the public database necessary for API systems. It is the preferred choice when the highest priorities are simplified client handoff for static sites and maintaining the integrity, auditability, and speed. - Primary Goal: Building a highly secure, fast, and scalable static website (blog, documentation, marketing site). - Content Nature: Content is primarily text-based (Markdown, YAML, JSON) and closely linked to the website’s structure and code. - Workflow Priority: You need ultimate version control (every change is a Git commit), simple developer handoff, and full content ownership. - Security Concern: You want to eliminate the risk of database hacks by having no live, publicly accessible database. #### Git-Based CMS (✅ Pros) **Feature** **Description** Highest Security Content lives as simple files within your Git repository, meaning there’s no live, publicly accessible database to hack. Ultimate Version Control Every content save is automatically logged as a Git commit, offering a full audit trail and easy content rollback. Zero Vendor Lock-in Content is stored in standard, open formats like Markdown or YAML, ensuring you have full ownership and can move providers easily. Simple Integration It seamlessly integrates with virtually all Static Site Generators (SSGs) (Astro, Hugo, Next.js) because SSGs are built to read files directly from Git. #### Git-Based CMS (❌ Cons) **Limitation** **Description** Less Dynamic It’s less ideal for complex, sub-second, real-time dynamic data (e.g., live e-commerce inventory stock or rapidly changing data feeds). Media Management Requires extra attention for extremely large media files, often necessitating the use of third-party storage solutions (though many top Git-CMS tools handle this automatically). Setup Nuance Initial configuration requires a basic understanding of your repository and file structure to map the CMS fields correctly. > To Read further on the architecture of this CMS you may read [What is a Git-based Headless CMS?](https://sitepins.com/blog/git-based-headless-cms) ### API-Based CMS: Scalability and Omnichannel This architecture is best when your main focus is content distribution, real-time data querying, and massive scalability for complex applications. This focus dictates that content must be treated as pure data, decoupled entirely from the presentation layer, allowing it to be accessed and updated instantaneously across numerous endpoints. Specifically, the API-Based CMS shines when your goal is omnichannel delivery, meaning you need a single, consistent source of content to feed not just your website, but also mobile apps, smart devices, interactive kiosks, and other third-party services, all relying on the CMS to fulfill high-volume, dynamic data requests via robust REST or GraphQL APIs. The API-Based CMS architecture is defined by its ability to treat content as pure, queryable data: - Primary Goal: Distributing content to multiple diverse platforms simultaneously (websites, mobile apps, smart devices, kiosks). - Content Nature: Content is treated as queryable data (like a product catalog or complex data sets) that requires intricate relationships. - Workflow Priority: You require sub-second, real-time updates and massive scalability for complex data loads and high-frequency content querying. - Flexibility Need: You need a single content source to power various frontends, prioritizing omnichannel capabilities over single-site security and workflow simplicity. #### API-Based CMS (✅ Pros) **Feature** **Description** Omnichannel Excellence It’s perfectly suited for distributing a single source of content to multiple diverse endpoints simultaneously (websites, mobile apps, kiosks, etc.). Massive Scalability & Real-Time Data Highly effective for managing huge content volumes and data that requires instantaneous updates and complex queries (often via GraphQL). Separation of Concerns Provides a clean, total separation of content management from the frontend code base, which aids in maintaining microservices architecture. Powerful Querying Offers advanced tools to query and filter content based on complex data relationships. #### API-Based CMS (❌ Cons) **Limitation** **Description** Vendor Lock-in Content is stored in a proprietary database, which can make data migration difficult and tie you to the provider’s ecosystem. Costly Pricing is frequently based on API calls (requests and bandwidth), which can lead to unpredictable and high costs as traffic or complexity increases. Build Bottleneck Your site’s build and performance are directly dependent on the API’s uptime and response speed. Higher Complexity Generally requires a more complex setup, configuration, and integration process for developers. ## Top Static Site CMS Platforms: A Detailed Comparison Now that you know which architecture fits your goals, let’s look at the major players the CMS scene along, with their Pros, Cons and how they may serve your purpose. ### Top Git-Based CMS Platforms: Pros and Cons #### 1\. Sitepins **Aspect** **Details** Description Sitepins is built to eliminate complexity, offering a streamlined, secure platform with a powerful visual editor to abstract the Git workflow for non-technical users. ✅ Pros Instant Setup, Visual Editing (WYSIWYG editor), Streamlined Workflow, Universal SSG Support. 💡 Why It’s Different Focus on Abstraction (hides Git complexity), Integrated AI Assistant for content generation. [Try Sitepins for Free!](https://sitepins.com) #### 2\. CloudCannon **Aspect** **Details** Description CloudCannon is a fully managed service that provides specialized hosting and a world-class on-site visual editing experience perfect for client handoffs and agency workflows. ✅ Pros Exceptional Visual Editing (contextual), Managed Service, Easy Client Handoff. ❌ Cons Higher Cost, Proprietary Tools. [Visit Website](https://cloudcannon.com/) #### 3\. Decap CMS (formerly Netlify CMS) **Aspect** **Details** Description Decap CMS is a free, open-source, community-driven solution that provides a simple form-based editor directly reading and writing to your Git repository. ✅ Pros Zero Cost, High Flexibility (works with any SSG/Git), Simple Form Editor. ❌ Cons Manual Setup (YAML/JSON config), Less Visual (primarily form-based) [Visit Website](https://decapcms.org/) #### 4\. TinaCMS **Aspect** **Details** Description TinaCMS is an open-source tool built around React frameworks (like Next.js), providing developers with a powerful, customizable content editing sidebar and a flexible data layer. ✅ Pros Deep React Integration, Live Sidebar Editor, Hybrid Data (Git files and Cloud DB). ❌ Cons React Dependency (less versatile for non-React SSGs), Setup Complexity. [Visit Website](https://tina.io/) ### Top API-Based CMS Platforms: Pros and Cons #### 1\. Contentful **Aspect** **Details** Description Contentful is a market-leading, fully managed proprietary service known for its robust features, reliability, and enterprise-level tools for structuring and distributing content globally. ✅ Pros Highly Reliable, User-Friendly Interface, Strong Ecosystem (SDKs/Integrations). ❌ Cons High Cost, Vendor Lock-in, Strict API Call Limits. [Visit Website](https://www.contentful.com/) #### 2\. Sanity **Aspect** **Details** Description Sanity is a developer-centric CMS that treats content as pure data, featuring the unique, powerful GROQ query language and a highly customizable, open-source editing environment called Sanity Studio. ✅ Pros Ultimate Customization (Sanity Studio), Powerful GROQ Queries, Real-Time Collaborative Editing. ❌ Cons Steeper Learning Curve, Blank Slate (must build UI/frontend), Usage Costs scale by API calls. [Visit Website](https://www.sanity.io/) #### 3\. Strapi **Aspect** **Details** Description Strapi is the leading open-source headless CMS, built on Node.js. It offers maximum control over your data, database, and infrastructure since you host and maintain the platform yourself. ✅ Pros Open Source & Free (core), Full Data Control (choose your DB), Rapid API Generation. ❌ Cons Maintenance Burden (hosting, scaling, security), Fewer Built-in Features (requires plugins), Upgrade Challenges. [Visit Website](https://strapi.io/) ## Conclusion The Git-based CMS is ideal for content that is file-based and closely tied to your website’s codebase, providing maximum security and developer transparency. Conversely, the API-based CMS is best suited for scenarios where content must be treated as queryable data and fed instantly to multiple diverse platforms, excelling at high-volume, dynamic content that requires a dedicated database. Choosing the right tool ensures your site is not just fast and secure, but also easily manageable for everyone on your team. ## Quick-Guide FAQ - **What is a Headless CMS?**It’s a system that manages content (the body) but intentionally lacks a dedicated front-end (the head), delivering content via APIs or files. - **Why is Git-based CMS good for Composable Web Architecture?**It offers high security (no database to hack), full version control, and integrates perfectly with SSGs because content lives in the Git repository. - **When should I use an API-based CMS?**Use it when you need real-time updates and must distribute content to many different platforms simultaneously (omnichannel). - **What are the most popular Static Site Generators (SSG)**Astro, Next.js, Hugo, Gatsby, Jekyll, Eleventy (11ty), and Nuxt.js. - **What is unique about Sitepins?**It combines Git security with a visual, on-page editor and an integrated AI Assistant to simplify content handoff for non-technical users. - **Can non-technical people use Headless CMS?**Yes. Modern platforms (especially Git-based ones) provide simple visual interfaces that hide the technical complexities of Git or APIs. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/headless-cms-tool-for-static-site) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Should you migrate from WordPress to a Static Site Generator in 2026? URL: https://sitepins.com/blog/migrating-wordpress-static-site Thinking of leaving WordPress? Explore the performance, security, and scalability benefits of migrating to a Static Site Generator (SSG) architecture in 2026. # Should you migrate from WordPress to a Static Site Generator in 2026? - Redwan - January 04, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Should you migrate from WordPress to a Static Site Generator in 2026?](/_vercel/image?url=_astro%2Fwordpress-static-migration.DZa0t0dv.webp&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) WordPress has powered over 590 million websites since 2003, making it the world’s most popular content management system. But despite its dominance, the platform faces persistent challenges: slow page loads caused by database queries, frequent security patches, and scaling limitations that become expensive to solve. If you’re experiencing these frustrations, there’s a different approach worth considering. Static site generators offer a fundamentally different way to build websites. Instead of creating pages on the fly every time someone visits, they build everything once and serve pre-made files. This transition offers transformative improvements in performance, security, and operational simplicity. ## Is This Approach Right for Your Site? ### When Static Sites Make Sense Static sites work best for content that doesn’t change constantly. Think company blogs, marketing websites, documentation sites, or portfolio pages. If your content updates happen on a schedule rather than every few minutes, you’re already a good candidate. **You should consider migrating if:** - **Your team cares about site speed** - WordPress sites average only 43% passing scores on Google’s Core Web Vitals. That’s not great when speed directly affects your search rankings and sales. Static sites routinely score above 95%. - **Security is a priority** - If you’re tired of weekly plugin updates and worried about vulnerabilities, static sites eliminate most of those concerns. No database means no SQL injection. No PHP means no server-side exploits. - **You publish on a schedule** - Media companies, content marketers, and anyone with an editorial calendar will find the workflow natural. Your content gets reviewed, approved, and published at scheduled times. - **Traffic spikes stress your server** - Does your site slow down or crash when you get featured somewhere? Static files served from a CDN handle traffic surges without breaking a sweat or breaking the bank. ### When to Stick with WordPress Static sites aren’t the answer for everything, and forcing them where they don’t fit creates more problems than it solves. - **You’re running an online store** - Real-time inventory, shopping carts, and order processing need dynamic functionality. While headless commerce exists, it’s complex and expensive to implement properly. - **Your site depends on user interaction** - Forums, membership sites, or social platforms where users create and share content need WordPress’s dynamic capabilities. - **Non-technical staff update content multiple times daily** - If your team isn’t comfortable with new workflows and updates happen constantly throughout the day, the WordPress dashboard might be worth keeping. - **You’re on a tight budget with no developers** - Migration takes time and technical skill. If you don’t have either, the upfront cost might outweigh the long-term savings. ## Understanding the Difference ### How WordPress Actually Works Every time someone visits a WordPress page, the server does a lot of work. It queries the database (typically 50-100 times per page, sometimes thousands), runs PHP code, loads plugins, applies your theme, and finally spits out HTML. This happens fresh for every single visitor. All that processing takes time. Most WordPress sites take 200-1000 milliseconds just to start sending data. That might not sound like much, but studies show that even a one-second delay can cost you 7-20% of your conversions. The database also becomes a single point of failure. If it goes down or gets corrupted, your entire site goes offline. ### How Static Sites Work Differently Static site generators turn your content into HTML files during a build process. You make a change, trigger a build, and create a complete website made of simple HTML, CSS, and JavaScript files. When visitors show up, they just get those pre-made files. No database queries. No PHP processing. No waiting. The result? Pages start loading in under 50 milliseconds. Your site can handle massive traffic because you’re just serving files. And since there’s no server-side code running, thus there’s nothing to hack. ## The Real-World Benefits of Static Sites ### Speed That Actually Matters Here’s what the performance difference looks like in practice. Static sites consistently score 95 or higher on Google’s Lighthouse performance tests. WordPress sites typically struggle to break 60, even with caching plugins and optimization. Why does this matter? It is important for SEO. Google uses site speed as a ranking factor. Slower sites rank lower. More importantly, faster sites convert better. When your pages load instantly instead of taking several seconds, more visitors stick around and take action. The speed comes from eliminating database lookups. WordPress makes 50-100 database queries per page. Complex sites with lots of plugins can hit thousands. Static sites make zero. The data is already in the HTML. ### Security You Can Actually Maintain WordPress security is a constant battle. New vulnerabilities appear regularly. Plugins need updating. Core files need patching. Miss an update, and you’re vulnerable. It’s exhausting, especially for small teams. Static sites sidestep most of this. Without PHP or a database, the most common attack vectors simply don’t exist. Nobody can inject malicious code into your database because there isn’t one. Nobody can exploit PHP vulnerabilities because there’s no PHP running. You would only need to secure your hosting and build process, but that’s about it. ## The Migration Challenges ### Replacing Dynamic Features WordPress makes certain features easy. Comments, search, and contact forms work out of the box. With static sites, there are alternatives. - For comments, services like Disqus or Giscus work well. They load comments through JavaScript, so your pages stay static while comments remain dynamic. - For search, you have options. Lightweight libraries like Lunr.js or Pagefind can search your content right in the browser. For larger sites, services like Algolia provide powerful hosted search. - For forms, services like Netlify Forms, Formspree, or Getform handle submissions. You add a simple form to your page, and they handle the backend processing. ## Choosing Your Static Site Generator The static site ecosystem is rich with options. You’ll find generators for nearly every programming language and use case: Jekyll (Ruby), Eleventy (JavaScript), Gatsby (React), Nuxt (Vue), SvelteKit (Svelte), and many more. Each has its strengths and dedicated communities. That said, three generators stand out as particularly strong choices for teams migrating from WordPress. They offer the best combination of performance, features, community support, and long-term viability. Let’s look at each: ### Hugo: Fast and Straightforward Hugo builds sites incredibly fast. We’re talking thousands of pages in seconds. It’s built with Go, which means you just download one file and you’re ready to go. No dependency installation, no version conflicts. Hugo excels at content-heavy sites. If you have a blog, documentation site, or marketing site with lots of pages, Hugo handles it smoothly. The template language is straightforward once you get past the initial learning curve. ### Astro: Modern and Flexible Astro is newer but thoughtfully designed. Its killer feature is “partial hydration.” Pages are static by default, with zero JavaScript. You then choose exactly where you need interactivity and add it selectively. You can also mix frameworks. Use React for one component, Vue for another, or just plain JavaScript. This flexibility is valuable if you’re working with existing component libraries or have specific framework preferences. ### Next.js: Powerful but Complex Next.js offers the most features but comes with the most complexity. It can do static generation, server-side rendering, or a mix of both. It’s built on React, so your team needs React knowledge. Choose Next.js when you need that flexibility or when you’re building something that blends static content with dynamic features. It’s overkill for a simple blog but excellent for more complex applications. ## Is This Migration Worth it? Moving from WordPress’s average 43% Core Web Vitals pass rate to consistently scoring 95%+ improves your search rankings and conversion rates. Security becomes simpler. You’re not constantly patching plugins or worrying about database vulnerabilities. Hosting gets cheaper because serving static files costs less than running WordPress infrastructure. However, migration takes time and requires technical skills. If your site depends heavily on dynamic features, if your team isn’t ready for new workflows, or if you lack the resources to execute properly, it might not be the right move. For content-focused sites with technical teams, scheduled publishing workflows, and performance or security concerns, static site generators paired with a good headless CMS offer real advantages. The web is constantly evolving, and this architecture reflects where modern web development is heading. ## How do you Manage Your Content After Migration? ### You Still Need an Editing Interface Here’s the problem: static sites store content as Markdown files in a code repository. That’s great for developers but intimidating for content editors who are used to WordPress’s visual editor. This is where a Git-based headless CMS comes in. It gives your content team a familiar editing interface while storing everything as files in your repository. Editors get their visual editor, developers get their version control, and everyone’s happy. ### How It Actually Works A Git-based headless CMS connects directly to your repository on GitHub or GitLab. When an editor makes changes through the CMS interface, those changes get committed to the repository just like code changes would. That commit triggers your build process, which rebuilds the affected pages and deploys them. The “headless” part means the CMS doesn’t control how your content looks. It just manages the content itself. That content can then go to your website, your mobile app, or anywhere else you need it. Everything stays in version control, so you can always see who changed what and roll back if needed. Your content team gets to work in an interface that feels familiar. Your development team gets content stored as portable, version-controlled files. It’s the best of both worlds. ​ > To learn more about Git-based Headless CMS read: ​[What is a Git based Headless CMS?](https://sitepins.com/blog/git-based-headless-cms) ## Sitepins CMS ​[Sitepins](https://sitepins.com/) was built specifically for teams making this transition. It provides an editing interface that feels familiar to WordPress users while managing content as files in your Git repository. Your developers get proper version control and automated deployments. Your editors get a visual interface they can actually use. The key features that help with WordPress migrations: - **Familiar editing experience** - Your content team doesn’t need to learn Git or Markdown. They can just edit content like they always have. - **Multi-site management** - Handle multiple static sites from one dashboard if you manage several properties. - **Version control built in** - Every change is tracked. Rolling back is simple. - **Works with Hugo, Astro, Next.js and more** ## Conclusion Migrating from WordPress to a static site generator takes effort, but the payoff is substantial for content-focused sites. You’ll see measurably faster load times that directly improve conversions, dramatically simpler security that eliminates constant patching, and lower hosting costs that compound over time. With modern tools like Git-based headless CMS platforms bridging the gap between developer workflows and content team needs, the migration process has become more straightforward than ever. If your site publishes content on a schedule and performance matters to your business, static architecture offers a proven path to a faster, more secure, and more maintainable web presence. ​ ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/migrating-wordpress-static-site) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Insights, Updates & Stories URL: https://sitepins.com/blog/page/2 Updates and insights on building tools for the static web. Sitepins Blogs # Insights, Updates & Stories Updates and insights on building tools for the static web. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![What's New in Sitepins — June 2026](/_vercel/image?url=_astro%2Fwhats-new-in-sitepins-june-2026.BCydbFid.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/whats-new-in-sitepins-june-2026) #### [What's New in Sitepins — June 2026](/blog/whats-new-in-sitepins-june-2026) - Redwan - July 07, 2026 [![6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/_vercel/image?url=_astro%2Fdecapcms-alternatives.CELW-JIt.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/decapcms-alternatives) [CMS,](/categories/cms)[Git based](/categories/git-based) #### [6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/blog/decapcms-alternatives) - Farhad - June 10, 2026 [![What's New in Sitepins — May 2026](/_vercel/image?url=_astro%2Fwhats-new-in-sitepins-may-2026.BLZ2v1Zh.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/whats-new-in-sitepins-may-2026) #### [What's New in Sitepins — May 2026](/blog/whats-new-in-sitepins-may-2026) - Redwan - June 03, 2026 [![Sitepins Now Speaks Your Language: Native i18n Support Is Here](/_vercel/image?url=_astro%2Fsitepins-i18n-support.BhlgOUOm.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/sitepins-i18n-launch) [Announcement,](/categories/announcement)[I18n](/categories/i18n) #### [Sitepins Now Speaks Your Language: Native i18n Support Is Here](/blog/sitepins-i18n-launch) - Farhad - June 03, 2026 [![7 Benefits of Headless CMS for Modern Web Development in 2026](/_vercel/image?url=_astro%2Fbenefits-headless-cms.DQhKO-b6.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/benefits-headless-cms) [Headless,](/categories/headless)[CMS](/categories/cms) #### [7 Benefits of Headless CMS for Modern Web Development in 2026](/blog/benefits-headless-cms) - Redwan - May 19, 2026 [![When Not to Use an API-Based Headless CMS with Astro or Next.js](/_vercel/image?url=_astro%2Fwhen-not-to-use-api-based-headless-cms.CckSL2CJ.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/when-not-to-use-headless-cms) [Headless,](/categories/headless)[CMS](/categories/cms) #### [When Not to Use an API-Based Headless CMS with Astro or Next.js](/blog/when-not-to-use-headless-cms) - Farhad - May 11, 2026 ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Insights, Updates & Stories URL: https://sitepins.com/blog/page/3 Updates and insights on building tools for the static web. Sitepins Blogs # Insights, Updates & Stories Updates and insights on building tools for the static web. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![What's New in Sitepins — April 2026](/_vercel/image?url=_astro%2Fapril-new-update.C0qad5cf.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/whats-new-in-sitepins-april-2026) #### [What's New in Sitepins — April 2026](/blog/whats-new-in-sitepins-april-2026) - Redwan - May 06, 2026 [![Sitepins Hits 1000 Users! 🥳](/_vercel/image?url=_astro%2Fsitepins-1000-users-milestones.CX96S8kO.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/sitepins-hits-1000-users) #### [Sitepins Hits 1000 Users! 🥳](/blog/sitepins-hits-1000-users) - Farhad - April 22, 2026 [![EmDash vs Sitepins: Best Headless CMS for Astro](/_vercel/image?url=_astro%2Femdash-cms-vs-sitepins-cms.Djf6zKrT.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/emdash-vs-sitepins-headless-cms-for-astro) [Astro,](/categories/astro)[Comparison](/categories/comparison) #### [EmDash vs Sitepins: Best Headless CMS for Astro](/blog/emdash-vs-sitepins-headless-cms-for-astro) - Farhad - April 05, 2026 [![What's new in Sitepins — March 2026](/_vercel/image?url=_astro%2Fwhats-new-sitepins-march-2026.BCdxOjAr.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/whats-new-in-sitepins-march-2026) #### [What's new in Sitepins — March 2026](/blog/whats-new-in-sitepins-march-2026) - Redwan - April 02, 2026 [![CMS for SEO in 2026: Architecture, Speed & What to Look For](/_vercel/image?url=_astro%2Fcms-for-seo.BBfOnhiy.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/best-cms-for-seo-in-2026) [SEO](/categories/seo) #### [CMS for SEO in 2026: Architecture, Speed & What to Look For](/blog/best-cms-for-seo-in-2026) - Redwan - March 16, 2026 [![What's new in Sitepins — February 2026](/_vercel/image?url=_astro%2Fsitepins-new-february-2026.DRYqSgnJ.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/whats-new-in-sitepins-february-2026) #### [What's new in Sitepins — February 2026](/blog/whats-new-in-sitepins-february-2026) - Redwan - February 26, 2026 ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Insights, Updates & Stories URL: https://sitepins.com/blog/page/4 Updates and insights on building tools for the static web. Sitepins Blogs # Insights, Updates & Stories Updates and insights on building tools for the static web. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Git-Based vs. API-First Headless CMS: The Ultimate Comparison ](/_vercel/image?url=_astro%2Fgit-based-cms-vs-api-first-cms.DupST9ld.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/git-based-vs-api-based) [CMS,](/categories/cms)[API First,](/categories/api-first)[Git Based](/categories/git-based) #### [Git-Based vs. API-First Headless CMS: The Ultimate Comparison](/blog/git-based-vs-api-based) - Redwan - February 23, 2026 [![What's new in Sitepins — January 2026](/_vercel/image?url=_astro%2Fwhat-new-sitepins-2026.CymELbSH.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/whats-new-in-sitepins-january-2026) #### [What's new in Sitepins — January 2026](/blog/whats-new-in-sitepins-january-2026) - Farhad | Redwan - February 01, 2026 [![Astro in 2026: Performance, Features, and the Cloudflare Acquisition ](/_vercel/image?url=_astro%2Fsitepins-astro-cloudflare.aCWLHVr0.webp&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/astro-sitepins-2026) #### [Astro in 2026: Performance, Features, and the Cloudflare Acquisition](/blog/astro-sitepins-2026) - Redwan - January 25, 2026 [![Should you migrate from WordPress to a Static Site Generator in 2026?](/_vercel/image?url=_astro%2Fwordpress-static-migration.DZa0t0dv.webp&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/migrating-wordpress-static-site) [Static Site,](/categories/static-site)[CMS](/categories/cms) #### [Should you migrate from WordPress to a Static Site Generator in 2026?](/blog/migrating-wordpress-static-site) - Redwan - January 04, 2026 [![Choosing the Right CMS Tool for Your Static Site](/_vercel/image?url=_astro%2Fheadless-cms-git-based-api-first.CJB43JNU.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/headless-cms-tool-for-static-site) [CMS](/categories/cms) #### [Choosing the Right CMS Tool for Your Static Site](/blog/headless-cms-tool-for-static-site) - Redwan - November 18, 2025 ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins CMS is now open source URL: https://sitepins.com/blog/sitepins-cms-is-now-open-source Sitepins is now open source under AGPL-3.0, giving teams full source access, self-hosting, and a more durable CMS path. # Sitepins CMS is now open source - Farhad - July 28, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Sitepins CMS is now open source](/_vercel/image?url=_astro%2Fsitepins-open-source-git-based-cms.DJaziaAv.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins is now open source under AGPL-3.0. You can read the code, self-host it for free, or keep using the managed cloud. Here is what led to it. ### The problem we had In 2018 we built Hugo and Bootstrap themes as Themefisher and Gethugothemes. Our customers needed to edit their sites without touching code. We found a Git-based CMS that did the job well, and we integrated it across our themes, our client projects, and our own websites. In 2023, that CMS shut down. We were supporting 100+ themes, with no editor to hand our customers. We tested every replacement we could find. One was priced for enterprise budgets and would not work with our themes. One had stopped receiving maintenance and carried hundreds of open bugs. We forked an open source option and abandoned the fork after the architecture proved too fragmented to build on. Our own marketing team could not update our sites comfortably without a developer. Around the same time we started shipping Astro and Next.js themes, and the developers buying them kept asking the same question: what CMS should they give a non-technical client or teammate? We had nothing to suggest them. ### What we built Most Git-based CMS tools make you write the schema by hand. You declare every collection, every field, and every field type in a config file before the editor shows you anything. Get one path wrong and it renders nothing. That was true when we started in 2023, and it is still true for most of them today. Sitepins detects the schema instead. Connect a GitHub or GitLab repo, and it reads the content files already there, reads the structure from your frontmatter, and builds the editing interface from what it finds. No config file to write first. You can still change any of it. Field types, labels, default values, dropdowns, and required or hidden flags are all editable from the UI. Detection gives you a working editor on day one, and you refine it from there. Every save becomes a Git commit. Your content stays in your repo the entire time. We built it for our own sites first. Then we shared it with our existing audience. The beta launched July 7, 2025 with no major promotion, and 1,800+ people have signed up since. We shipped fixes and features from their feedback every month. ### Why we waited We could have opened the repo on day one. But handing developers a half-built codebase would have cost us more trust than it earned. We wanted the product stable before anyone read it or ran it. It is stable now. Every site we own runs on Sitepins: Themefisher, Gethugothemes, UIHut, Statichunt, Zeon Studio, and Sitepins itself. We use it daily, which is why it improves daily. ### What AGPL-3.0 gets you - Full source code, free to read and modify. - Free self-hosting for personal and commercial projects, with no usage limits. - One condition: if you modify Sitepins and run it as a service for other people, you publish your modified source too. Self-hosting needs Node.js 22+, pnpm, MongoDB, and an S3-compatible bucket for media. Docker Compose brings up the stack in one command. > If you want to sell a hosted product built on Sitepins without publishing your modifications, we offer a commercial license under the Agency white label plan. ### Why this matters for a CMS Our old CMS shut down and left us stranded with 100+ themes. Anyone picking a CMS today is placing a bet on the company behind it lasting. AGPL removes the bet. If we disappear, the code is yours and your sites keep running. ### Nothing changes for Cloud users Your plan, your data, and your workflow stay exactly as they are. Open source adds a self-hosting path for people who want one. ### What comes next AI builders changed who can ship a website. Building is fast now. Maintaining what you built is still slow. A website is not a one-time deliverable. It is a product you keep updating with new posts, changed pricing, new screenshots, and rewritten copy. Most AI-built sites are not structured for that work. Every small text change goes back through a prompt, burns tokens, and risks breaking something that already worked. That does not hold up over a year of ownership. The framework choice matters here too. Most AI builders default to a React app. For a content site, Astro, Next.js, and Hugo produce better results: faster pages, stronger SEO, and content stored in files rather than buried inside components. We expect more people to move toward those frameworks as they hit the limits of app-shaped output. None of those frameworks ship a CMS. So the next question is which kind of CMS to add. API-based platforms like Sanity, Strapi, and Contentful solve a real problem when one content source has to feed several applications. Most websites do not have that problem. For a marketing site, a blog, a docs site, or a client project, keeping content in the repo as Markdown is simpler and cheaper, and it stays portable. That is the audience Sitepins is built for. We plan to keep serving it. More frameworks supported, a sharper editing experience, and fewer steps between connecting a repo and handing the site to a client. Now that the code is public, we hope some of that work comes from you. Open an issue, send a pull request, or tell us what breaks. ### Start here - Code: [github.com/sitepins/sitepins](https://github.com/sitepins/sitepins) - Free plan: [app.sitepins.com](https://app.sitepins.com) - Live demo: [demo.sitepins.com](https://demo.sitepins.com) - Developer docs: [developer.sitepins.com](https://developer.sitepins.com) ​ ​ ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/sitepins-cms-is-now-open-source) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins Hits 1000 Users! 🥳 URL: https://sitepins.com/blog/sitepins-hits-1000-users Sitepins started when our favorite CMS shut down. Today, 1,000 people use it to manage content on Astro, Hugo, and Next.js sites. Here's how we got here. # Sitepins Hits 1000 Users! 🥳 - Farhad - April 22, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Sitepins Hits 1000 Users! 🥳](/_vercel/image?url=_astro%2Fsitepins-1000-users-milestones.CX96S8kO.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) **Sitepins hits 1,000 users this week.** It’s a small number in the world of SaaS, but it means something to us. Sitepins started as a frustration. For years, we relied on Forestry CMS that worked beautifully across our themes, our websites, and the client sites we served at Themefisher, Gethugothemes, and Zeon Studio. Then in 2023, it shut down. We were left supporting 100+ themes (now we have [200+ themes](https://themefisher.com/)) with no good path forward. We tried every alternative back then. Nothing worked the way Forestry did. So we built our own. Today, **1,000+ people** use Sitepins to manage content on their Astro, Hugo, and Next.js websites. Teams use it. Solo developers use it. Freelancers managing client sites use it. They’re people who didn’t want to buy a massive CMS or fork over infrastructure costs. They just wanted a visual editor that works with their existing workflow. ## Learning from the Early Days The early users taught us what matters. They showed us that a CMS doesn’t need to be complex to be useful. They needed to: - **Edit content and images** without rebuilding from the command line. - **Give clients access** without handing them the keys to production. - **Use something that played nicely** with static sites, not against them. We listened. We kept it simple. We made it fast. Building Sitepins has been about finding the gap between two worlds. On one side, developers who love Git, version control, and simplicity. On the other, people who just want to edit content visually without knowing what a repository is. We built Sitepins in that gap. ## A Milestone of Feedback The weird thing about 1,000 users is it feels both huge and impossibly small. We know many of you by name. We read your feature requests. We see how you use the editor: what works, what breaks, and where you get stuck. That feedback has shaped everything we’ve built. **You made this real.** - **To our first hundred users:** Thank you. You took a chance on something unproven. You sent us bugs, feature ideas, and encouragement when we needed it most. Your names are still on our Discord, Internal Documents. - **To everyone who joined after:** Thank you for believing in the vision. For integrating Sitepins into your workflows, recommending it to colleagues, and sticking with us through the rough edges. ## What’s Next? We aren’t slowing down. Sitepins was built specifically for static site generators like Astro, Hugo, and Next.js, and we’re focused on making it more useful for every workflow they power. We’re also learning that Sitepins fits into workflows we didn’t expect. Each of those use cases is teaching us something new about what Sitepins can be. We’re also thinking beyond today’s web. AI and agentic workflows are changing how content is created and managed. We’re building Sitepins to be ready for that shift, so your content infrastructure works not just for you, but for the agents working alongside you. ## This Is Just the Beginning 1,000 users tells us one thing clearly: we are solving a real problem. We haven’t cracked it perfectly yet. But we’re doing our best every day, and that’s worth celebrating. If you’re reading this and you’re not yet a Sitepins user, we’d love to have you. [Try it for free](https://sitepins.com/). Thank you to everyone who got us here. Let’s build something even better from here. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/sitepins-hits-1000-users) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins Now Speaks Your Language: Native i18n Support Is Here URL: https://sitepins.com/blog/sitepins-i18n-launch Sitepins now has native internationalization (i18n) support for 6 languages. No browser extensions needed. Learn what's included and how to contribute your language. # Sitepins Now Speaks Your Language: Native i18n Support Is Here - Farhad - June 03, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Sitepins Now Speaks Your Language: Native i18n Support Is Here](/_vercel/image?url=_astro%2Fsitepins-i18n-support.BhlgOUOm.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins now has native internationalization (i18n) support for 6 languages. No browser extensions needed. Learn what’s included and how to contribute your language. > **Note:** As of June 3rd 2026 We have updated this list to include 6 more languages, such as: Japanese (日本語, ja), French (Français, fr), Russian (Русский, ru), Korean (한국어, ko), Indonesian (Bahasa Indonesia, id), and Vietnamese (Tiếng Việt, vi. Sitepins now supports a total of 12 languages. ## TL;DR - Sitepins now ships with native internationalization (i18n) support. No external extensions required. - Six languages are available at launch: English, Chinese (中文), German (Deutsch), Spanish (Español), Portuguese (Português), and Bengali (বাংলা). - The native implementation preserves UI layout and keeps technical terms accurate - something browser-based translation tools cannot do. - If your language is not here, let us know we’ll add it. ## Why We Built This: Our Users Were Already Working Around It We got feedback from users using browser extensions to translate the Sitepins interface. We get it, if a tool does not speak your language, you find a way to make it work. But external translation tools are a rough fix. They break layouts. They mistranslate some terms into phrases that do not mean the same thing in a CMS context. And they require every user to set it up individually, with no consistency across a team. That told us something clearly: Sitepins has users who need this, and they needed it to work properly. So we built native i18n support directly into the product. ## What “Native” i18n Actually Means for Your Workflow Native i18n means the language switching is handled inside Sitepins itself, not by a third-party extension parsing your DOM after the fact. Here is what that difference looks like in practice: - **Layout stays intact.** Every string in the interface was written to fit the components it sits in. No text overflow, no broken menus, no clipped labels. - **Technical terms stay accurate.** Git terminology is translated with context, not word-for-word. A “commit” in German is still a “Commit” - because that is the correct term for German developers too. - **Individual flexibility.** Each team member picks their own language in their account settings. A developer in Berlin and a content editor in New York can work in Sitepins side by side, each in their own language, on the same project. ## The Six Languages Available at Launch Sitepins i18n launches with support for these six languages: Language Code Region Focus English `en` Default Chinese (中文) (Simplified) `zh-CN` Mainland China, Singapore German (Deutsch) `de` Germany, Austria, Switzerland Spanish (Español) `es` Spain, Latin America Portuguese (Português) `pt` Brazil, Portugal Bengali (বাংলা) `bn` Bangladesh, West Bengal English remains the default. All other languages are available through the language selector in your settings. We chose these six based on where our active users are. If your language is not here, let us know we’ll add it. > **Note:** Our updated list includes 6 more languages, such as: Japanese (日本語, JA), French (Français, FR), Russian (Русский, RU), Korean (한국어, KO), Indonesian (Bahasa Indonesia, ID), and Vietnamese (Tiếng Việt, VI). Sitepins now supports a total of 12 languages. ## How to Switch Your Language in Sitepins Switching languages takes about ten seconds: 1. Open Sitepins and go to **Preferences**. 2. Find the **Language** option and select your language. 3. The interface updates immediately. No reload needed. Your language preference saves to your account. If you use Sitepins across multiple devices, the setting follows you. ![](/images/blog/sitepins-preference-setting.png) ![](/images/blog/sitepins-language-setting.png) ## Help Us Improve and Expand Language Support Six languages is a starting point, not a finish line. If your language is not on the list, let us know. [Tell us](https://sitepins.com/contact) which language you need. We will prioritize additions based on demand and add them in future releases. **A note on translation accuracy** The current translations were built with tool assistance. We are not native speakers of every language we ship, which means some strings may be slightly off, awkward phrasing, a wrong technical term, or an inconsistency between screens. If you spot something that does not read right in your language, please tell us. Your language knowledge is something we genuinely need and we will credit every correction in the release notes. Try the update today. ## Frequently Asked Questions About Sitepins i18n ### Which languages does Sitepins support? Sitepins currently supports English (default), Chinese (Simplified), German, Spanish, Portuguese, and Bengali. We will prioritize additions based on demand and add them in future releases. ### How do I request a new language for Sitepins? Tell us which language you need, we add it. The more requests a language gets, the higher it moves on our list. ### What if I find a translation error in my language? Contact us directly with what the translation currently says, and what it should say. We will fix it and credit you in the release notes. Try the update today. And if you want to help expand it, the repo is open. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/sitepins-i18n-launch) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Astro Visual Editor: Give Non Technical Users Edit Access URL: https://sitepins.com/blog/visual-editor-for-astro-websites Astro has no built-in CMS. Here's how to add an Astro visual editor in 10 minutes so non-technical editors can publish without touching Markdown or Git. # Astro Visual Editor: Give Non Technical Users Edit Access - Farhad - August 24, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Astro Visual Editor: Give Non-Technical Users Edit Access](/_vercel/image?url=_astro%2Fvisual-editor-for-astro.Ct6sFj2h.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Astro doesn’t come with an admin panel. There’s no login screen, no dashboard, no editor UI. Your content sits as Markdown files in `src/content/`, and changing it means opening a code repository. So how can you enable others to edit your Astro site? There is a solution. Connect your repository to an Astro visual editor like Sitepins. Setup takes about 10 minutes and requires no code changes. Point it at your `src/content/` folder and invite your editor by email. They work in a form-based interface, never in Markdown or Git. Every save becomes a commit in your repository and triggers your existing Vercel or Netlify deploy. This tutorial covers the complete setup for Astro sites. It also covers the exact editor experience your non-technical user will have once it’s live. **TL;DR, Key Takeaways** - Astro sites built with Content Collections work out of the box. No `astro.config.mjs` changes required - Editors see a clean form interface, not code or file trees - Every save becomes a Git commit, so your deploy pipeline triggers automatically - Editors do not need a GitHub account - 34% of Sitepins users build on Astro, so the CMS is purpose-tested against Astro’s content model - Setup takes 10 to 15 minutes. Editor onboarding takes under 5 ## What Is an Astro Visual Editor? An Astro visual editor is a separate web interface that lets your editor create, edit, and publish content. They access it at a URL, not in your codebase. They never touch Markdown files, frontmatter syntax, or Git. Under the hood, an Astro visual editor writes directly to your existing files. It edits the same `.md` and `.mdx` files in `src/content/` that you work with as a developer. The difference is presentation. You open a `.md` file in VS Code and edit raw text. Your editor opens a form with labelled fields (Title, Date, Body, Featured Image) and a rich text toolbar. The body field is a WYSIWYG editor. Text appears close to how it will publish, so an Astro WYSIWYG editor removes the gap between writing and previewing. When they save, the CMS commits the updated file to your GitHub or GitLab repository. From your side, it looks identical to a commit you made yourself. The file changes are in Git history, reversible, and auditable. **What it is not:** An Astro visual editor is not a page builder, drag-and-drop layout tool, or site redesign interface. It manages content: words, images, metadata. It does not manage design or code structure. If you are searching for a visual builder for Astro and expecting a layout canvas, this is a different category of tool. ## Why Non-Technical Editors Struggle with Astro by Default Astro is a developer-first framework. Its content layer is powerful and predictable for developers. That layer includes Content Collections, frontmatter schemas defined in `src/content/config.ts`, and Markdown and MDX files. For non-technical editors, it presents three specific problems. **1\. No editing interface ships with Astro.** Astro has no built-in CMS panel or admin UI. A non-technical user handed access to a GitHub repository will see a file tree, not an editorial interface. They cannot edit content without understanding Git, Markdown syntax, and file structure. **2\. Frontmatter syntax is fragile for non-developers.** A content entry in Astro looks like this: ``` --- title: "How We Built Our Product" date: 2026-03-15 description: "A case study about our build process." image: "/images/product-build.jpg" draft: false tags: ["product", "engineering"] --- Body content starts here... ``` A non-technical editor making a direct edit to this file on GitHub can easily break frontmatter syntax. A missing quote, a misformatted date, or a stray character causes a build failure. The editor sees nothing, but the entire site deploy breaks. **3\. Publishing requires understanding Git.** Even if an editor successfully edits a file in GitHub’s web interface, they need more context. They need to understand what “commit to main” means and what a pull request is. They also need to know why their changes may not appear immediately on a branch. A dedicated CMS layer removes all three problems. ## What You Need Before You Start - An Astro site with content in `src/content/` using Content Collections, or plain `.md` files in `src/pages/` - The site hosted on GitHub (all plans) or GitLab (Team plan and above) - Private repositories are supported on every plan. The free Hobby plan covers 1 private repo - A Sitepins account. [Start free at sitepins.com](https://sitepins.com/pricing) - Your Astro site already deployed on Vercel, Netlify, or Cloudflare Pages (optional, but required for the automatic deploy pipeline) - Your editor’s email address You do **not** need to install any npm packages, modify your `astro.config.mjs`, or make any changes to your repository before starting. ## Step-by-Step: Connect Sitepins to Your Astro Site ### Step 1: Create a project in Sitepins Sign in to [app.sitepins.com](https://app.sitepins.com) and click **New Project**. Sitepins will prompt you to connect a Git provider. Choose **GitHub**, or **GitLab** if you’re on the Team plan or above, and authorise the OAuth connection. You’ll see a searchable list of your repositories. Select the repository containing your Astro site and click **Continue**. Sitepins reads your repository’s file structure at this point. It does not commit anything to your repo during setup. ### Step 2: Select your content folder Sitepins shows your repository’s directory tree. Go to the folder containing your content files. For a standard Astro Content Collections project: - Choose `src/content/blog/` to give editors access to blog posts only - Choose `src/content/` to expose all collections (blog, docs, authors, etc.) Click **Confirm**. Sitepins scans the folder, detects your `.md` and `.mdx` files, and lists them as editable entries. **If you have multiple content types:** You can add multiple folders as separate sections. Editors see them as labelled groups in the sidebar (Blog, Docs, Authors) and switch between them with one click. ### Step 3: Confirm your content schema Sitepins reads the frontmatter fields in your existing content files and builds an editing form automatically. You do not need to define a CMS schema separately. Check that the detected fields match what you’d expect: - `title` → single-line text field - `date` → date picker - `description` → multi-line text area - `image` → media picker with upload support - `tags` → tag-adding widget - `draft` → toggle switch If you use a Zod schema in `src/content/config.ts`, required fields appear in every entry’s form and cannot be saved empty. Optional fields appear but can be left blank. ### Step 4: Set your media folder Choose the folder where uploaded images should be stored. Common choices for Astro projects: - `public/images/` is served directly at `/images/` in the built site. It works for frontmatter image paths referenced by URL - `src/assets/` is processed by Astro’s built-in image optimisation. It works for images imported in components When an editor uploads an image, Sitepins commits it to this folder. It then inserts the correct path into the content field automatically. All media is stored in your repository. No external CDN or third-party asset service is added. ### Step 5: Invite your editor Open **Settings → Team → Invite member** in your Sitepins project. Enter your editor’s email address and assign the **Editor** role. Editor access allows them to create, edit, and delete content entries. It does not allow access to project settings, repository configuration, or billing. Click **Send invite**. Your editor receives an email with a setup link. They create a password and access the editor directly. No GitHub or GitLab account required. Setup is complete on your end. ## What Your Editor Sees and How They Work Your editor’s experience is entirely separate from your development workflow. Here’s what they encounter. ![sitepins-dashboard-overview](/images/blog/sitepins-overview.png) ### The content list After logging in, the editor sees a clean sidebar with their content sections (Blog, Docs, etc.). Clicking a section shows a list of all content entries with titles, publish dates, and draft status. Entries can be filtered by status and sorted by date. There is no file tree, no raw Markdown, no Git interface. ### Opening and editing a post Clicking an entry opens the editing view. The frontmatter fields appear as a structured form on the left, or on top on smaller screens. The body content appears in a rich text editor. ![sitepins-single-post-editor-preview](/images/blog/sitepins-single-post-editor-preview_copy\(1\).png) The body editor works like a simplified word processor: - **Visual mode:** Toolbar with bold, italic, headings H1 to H4, links, ordered and unordered lists, blockquotes, inline code, code blocks, and image insertion. No Markdown knowledge required. - **Markdown mode:** Raw Markdown for editors who prefer it. Both modes stay in sync. Switching between them preserves all content. ### Adding images The editor clicks the image icon in the toolbar or the image field in the frontmatter form. A media panel opens showing previously uploaded images. They can drag in a new file or click to browse. Sitepins handles the upload, Git commit, and path insertion without any developer input. ### Saving and publishing When the editor clicks **Save**, Sitepins commits the changed file to your repository’s default branch (`main` or `master`). There is no separate “publish” step visible to the editor. Save means the content goes live as soon as your deploy pipeline completes. That is typically 1 to 2 minutes on Vercel and 1 to 3 minutes on Netlify. The editor sees a success confirmation with a note that the site is updating. They do not see a deploy log, build output, or any technical feedback. ### Creating new posts The editor clicks **New Entry** in the content section. A blank form opens with all the frontmatter fields from your schema. They fill in the fields, write the body, and save. Sitepins creates the `.md` file in your `src/content/blog/` folder, or wherever you pointed it. The filename is generated from the entry title. ## How Edits Flow Back to Your Codebase Every save in Sitepins creates a standard Git commit. From your side, it looks identical to any other content commit: 1. Editor clicks **Save** in Sitepins 2. Sitepins creates a commit: `Update: "Post title"` on your `main` branch 3. The commit appears in your GitHub or GitLab repository history with the changed `.md` file 4. Vercel, Netlify, or Cloudflare Pages detects the push and triggers a build 5. `astro build` runs, and your updated content is deployed to the CDN 6. The live site reflects the editor’s changes, typically within 1 to 3 minutes From your local machine, running `git pull` brings the editor’s content changes into your working directory as normal files in `src/content/`. The files are identical to what you’d write yourself. No proprietary format, no CMS-specific metadata appended. **Git history stays clean.** Sitepins commits are clearly labelled. You can `git revert` any individual editor commit to undo a specific content change. You can `git blame` a content file to see the full edit history. ## Using Branches to Add a Review Step By default, Sitepins commits directly to your main branch, so editor saves go live immediately. If your workflow requires review before publishing, you can configure a staging branch. **How to set up a review workflow:** 1. Create a `staging` branch in your GitHub repository 2. In Sitepins **Settings → Project → Branch**, change the target branch from `main` to `staging` 3. Editors now save to `staging`. Their changes do not trigger a production deploy until you or they merge the branch. When an editor is ready to publish, Sitepins lets them open a pull request from `staging` to `main` directly from the CMS interface. No GitHub knowledge needed. You review the PR and merge it when ready. Vercel or Netlify detects the merge and deploys the production build. This workflow is useful for: - Teams where a developer or manager reviews content before it goes live - Sites where content errors have a high cost, for example legal or compliance review - Multi-author setups where you want a centralised review step ## Frequently Asked Questions ### How can I enable others to edit my Astro site? Connect your Astro repository to a Git-based visual editor such as Sitepins. Point it at your `src/content/` folder and invite your editor by email. They get a form-based editing interface and never see Git or Markdown syntax. Every save they make commits to your repository and triggers your existing deploy pipeline. Setup takes about 10 minutes and requires no changes to your Astro project. ### Does adding Sitepins require any changes to my Astro project? No. You don’t modify `astro.config.mjs`, install npm packages, change your content collection configuration, or add any files to your repository. Sitepins connects externally via your Git provider’s API and reads and writes your existing Markdown files. Your project structure is unchanged. ### Can Sitepins work with Astro’s Content Collections schema defined in `config.ts`? Yes. Sitepins reads your frontmatter fields and reflects them in the editing form. Fields marked required in your Zod schema appear as mandatory form fields that cannot be saved empty. Fields marked optional appear but can be left blank. Sitepins does not read the `src/content/config.ts` file directly. It infers field types from your existing content. For a more precise schema mapping, you can manually configure field types in Sitepins project settings. ### What happens to my Astro site’s content if I stop using Sitepins? Nothing. All content files remain in `src/content/` in your repository, in standard Markdown and MDX format. Stopping Sitepins removes the editorial interface only. Your content, your Git history, and your deploy pipeline are entirely unaffected. ### Do editors need to know Markdown or Git? No. The visual editor covers all common formatting without any Markdown syntax. That includes headings, lists, links, images, bold, italic, and code. Editors who prefer working in Markdown can switch to raw mode. Git is invisible to the editor entirely. ### Can I use Sitepins with an Astro site deployed on Vercel? Yes. Sitepins connects to your Git repository. Vercel connects to the same repository for deployment. They operate independently. Every Sitepins save triggers a Vercel deployment automatically via the standard GitHub push webhook. No additional configuration needed. ### What if my Astro site has content outside `src/content/`? If your content is in `src/pages/` as plain `.md` files without Content Collections, Sitepins works the same way. Point it at `src/pages/` or whatever subdirectory contains your content files. You can also add multiple content directories as separate sections within the same Sitepins project. ### Can multiple editors work on the same Astro site? Yes, on a paid plan. The free Hobby plan includes 1 user. Pro supports 3 users per organization across 3 roles. Team and Agency support 5 users per organization. Each editor has their own login. Concurrent editing on the same file is handled with a lock mechanism. If two editors open the same entry simultaneously, the second sees a notification that it’s being edited. ### Is there a free plan? Yes. The Hobby plan is free forever. It covers 3 sites, 1 organization, and 1 user, including 1 private repository. Paid plans are billed monthly or yearly: - **Pro, $12/month** ($10/month billed yearly). 6 sites, 2 organizations, 3 users per organization, 3 roles. - **Team, $29/month** ($24/month billed yearly). 15 sites, 5 organizations, 5 users per organization, GitLab support. - **Agency, $49/month** ($40/month billed yearly). 30 sites, 10 organizations, 5 users per organization. Lifetime licences are also available: $249 Pro, $519 Team, $729 Agency. Every new account gets a 15-day Pro trial. No credit card required. **Try Sitepins free. Give your Astro site a visual editor in 10 minutes.** [Start your free trial](https://sitepins.com/pricing)​ ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/visual-editor-for-astro-websites) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's New in Sitepins — April 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-april-2026 Sitepins' April 2026 update focuses on stability, bug fixes, and a smoother CMS experience. Plus, a new schema editor and the free PowerAI Astro template. # What's New in Sitepins — April 2026 - Redwan - May 06, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's New in Sitepins — April 2026](/_vercel/image?url=_astro%2Fapril-new-update.C0qad5cf.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) In April, we spent the month heads-down on what matters just as much as shipping new features: stability, bug fixes, and refining the overall CMS experience. If things have been feeling a little smoother lately, that is why. Our focus was entirely on improving your content management experience and ironing out the rough edges across the board. ### TL;DR - **Edit and Modify Schema** — Customize your schema fields, field types, and input styles directly from the CMS. - **PowerAI Template** — A free AI SaaS starter template built with Astro, now available in the Sitepins template library. - **Bug Fixes and Stability Improvements** — A focused month of fixes and performance improvements across the CMS. ​ ### Edit and Modify Schema ![](/images/blog/product-update-april-2026/edit-schema.png) **What:** You can now open the Edit Schema panel directly from within Sitepins and fully customize your content structure. For each field, you can set the field type, label, description, default value, and input style, and mark fields as required or hidden. Switch any field from a standard textbox to a dropdown, populated either with static options you define manually or pulled automatically from a folder in your repository. **Why:** Freeform text fields lead to inconsistent data: typos in author names, broken category slugs, mismatched tags. With schema editing, you define the structure once and editors work within it. Cleaner data, fewer errors, and a faster editing experience for everyone on the team. ​ ### PowerAI Template ![](/images/blog/product-update-april-2026/power-ai-sitepins.png) **What:** We added a new free template: **PowerAI**. Dark-themed AI SaaS starter template built with Astro. It comes with 15+ pre-built pages and 47 components and shortcodes, covering everything you would expect for a SaaS site: pricing, features, integrations, case studies, blog, careers, and more. It’s pre-configured and ready to use with Sitepins in one click. check out the demo right [**here.**](https://powerai-astro.pages.dev/)​ **Who is it for:** If you’re building an AI product or SaaS and need a polished site up fast, PowerAI gives you a solid, production-ready starting point without building from scratch. You can also test how easy it is to use with Sitepins to manage your content. ​ ### Bug Fixes and Stability Improvements The bulk of April went into this. We worked through a range of fixes and under-the-hood improvements to make the CMS more reliable, more consistent, and better performing across the board. ​ ## Closing Sitepins just crossed **1,300 users** and growing fast. We remain committed to delivering our users the best possible experience and keeping your content management seamless. If you are already using Sitepins, we would love to hear your feedback. If you need support you can reach us out via Discord or just [Contact Us.](https://sitepins.com/contact) - [Our Roadmap](https://updates.sitepins.com/) - [Follow us on X](https://x.com/sitepinscms) - [Discord (Support and Community)](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-april-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's new in Sitepins — August 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-august-2026 Sitepins August 2026 update: new languages with RTL support, Progressive Web App support, and a round of UI and quality of life improvements. # What's new in Sitepins — August 2026 - Redwan - September 01, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's new in Sitepins — August 2026](/_vercel/image?url=_astro%2Fwhats-new-in+sitepins-august-2026.CsfbGZeu.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) This month’s updates was about reach and access. We added new languages with full right-to-left support, made a Progressive Web App available so you can install Sitepins to your home screen, and shipped a round of UI and quality of life improvements based on your feedback. Here’s everything we shipped in August 2026: ### TL;DR - **New Languages & RTL Support** — Hindi, Arabic, and Italian are now available, with full right-to-left support. - **Progressive Web App Support** — A PWA is now available, with offline access and faster load times. - **Improved User Experience and UI** — Visual polish and usability across the app. - **Quality of Life Improvements** — A profile status indicator, a refreshed toolbar and editor interface, better drag and drop, and a smarter SEO panel. ### New Languages & RTL Support ![new-languages-rtl-support](/images/blog/product-update-august-2026/new-languages-rtl-support.png) **What:** Sitepins now supports Hindi (हिन्दी, HI), Arabic (العربية, AR), and Italian (Italiano, IT). Arabic comes with full right-to-left (RTL) layout support, so the interface reads and lays out correctly instead of being forced into a left-to-right layout. **Why:** More native language coverage means more teams can work in Sitepins comfortably, without translating the interface in their head first. RTL support specifically makes Sitepins usable for Arabic-speaking teams. ### Progressive Web App ![progressive-web-app-support](/images/blog/product-update-august-2026/progressive-web-app-support.png) **What:** Sitepins now has a Progressive Web App (PWA) available. You can install it directly to your desktop or phone home screen and open it like a native app, outside the browser. **Why:** A PWA loads faster, works with some offline access instead of failing outright when your connection drops, and let’s you access Sitepins with one tap instead via an app on your device. ### System Status Updates ![system-status-updates](/images/blog/product-update-august-2026/system-status-updates.png) **What:** You can now check Sitepins’ system status directly from your profile menu. It links out to a live status page showing whether Sitepins API, the Sitepins Web Application, and GitHub services and sync are operational, along with uptime history and response times, refreshed automatically. **Why:** This gives you a direct way to check if there’s issue on the server end of Sitepins. ### Quality of Life and UI improvements We also shipped a round of visual and usability improvements across the editor and app. - Improved toolbar and editing interface. - Drag and drop has been refined for a smoother experience. - Multilingual and translation has been improved throughout all languages - The SEO panel no longer overlays the editor and covers your content. It now docks as a side panel and pushes the editor over to make room, so you can see your content and your SEO analysis at the same time. ### Closing We keep building Sitepins around the people actually using it, and now that it’s open source, it’s better than ever. If you run into a bug or have thoughts on what feature you’d like next, drop them in our roadmap, Discord, or reach out to us via support. - [Our Roadmap](https://updates.sitepins.com/) - [Follow us on X](https://x.com/sitepinscms) - [Discord (Support and Community)](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-august-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's new in Sitepins — February 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-february-2026 Discover what’s new in Sitepins for Febuary 2026: version rollback a mermaid previews, git repo switching and more. See how it can make your workflow even faster. # What's new in Sitepins — February 2026 - Redwan - February 26, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's new in Sitepins — February 2026](/_vercel/image?url=_astro%2Fsitepins-new-february-2026.DRYqSgnJ.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) We kept the momentum going in February. The biggest change: Sitepins now works on mobile. Manage your content, push changes, and stay on top of your site from any device. On top of that, we shipped a round of improvements focused on reliability, control, and a smoother editing experience. Here’s everything we shipped. ### TL;DR - **Mobile Friendly** — Sitepins now looks and works great on mobile and tablet. - **Version Rollback & Restore** — Undo changes directly in the CMS. - **Mermaid Preview Support** — Live diagrams and charts in the editor. - **Organization Overview Layout** — Better management for teams and projects. - **Improved Loading** **Screen** — Skeleton state loading screens. - **Flexible Repository Switching** — Change your Git repository direct from the project settings - **Edit Configs as Code** — Direct access to configuration files. - **UI/UX Overhaul** — A faster, more consistent component library interface. - **Bug Fixes and Improvements** — Minor bug fixes and stability. ​ #### Mobile Friendly ![](/images/blog/product-update-february-2026/sitepins-mobile-optimized.png) **What:** We’ve optimized Sitepins to work seamlessly on mobile, tablet, and desktop. **Why:** Managing content shouldn’t be tied to your desk. A mobile-friendly experience means you can push changes, review content, and manage your site from any device without breaking your workflow. ​ #### Version Rollback & Restore ![](/images/blog/product-update-february-2026/version-rollback.png) **What:** You can now roll back any CMS change to a previous version and restore it with a single click. No Git history digging, no developer needed. **Why:** Content teams can now experiment freely. If something goes wrong, you can undo it instantly. It’s the safety net that makes editing less stressful. ​ #### Mermaid Preview Support ![](/images/blog/product-update-february-2026/mermaid-preview.png) **What:** Write Mermaid.js diagram code in your Markdown and see it render into a chart or flowgraph instantly, right inside the editor. **Why:** If you’re building technical documentation or blogs with diagrams, you no longer need external tools to preview your work. Write the code, see the result immediately. ​ #### Organization Overview Layout ![](/images/blog/product-update-february-2026/new-layout-for-organization.png) **What:** We’ve redesigned the layout where you can manage your organizations and teams. **Why:** For agencies and teams managing dozens of sites, the old list was getting a bit crowded. The new layout is cleaner, more searchable, makes it easier to switch between repositories and manage team permissions. **​** #### Improved Loading Screen ![](/images/blog/product-update-february-2026/skeleton-loading-screen.png) **What:** Content lists and dashboard elements now use skeleton state loading screens instead of blank screens. **Why:** Speed feels better when you can see what’s loading. Skeleton screens reduce frustration and set clear expectations while your files render. **​** #### **Flexible Repository Switching** ![](/images/blog/product-update-february-2026/flexible-repository-switching.png) **What:** You can now disconnect or change your connected Git repository directly from project settings, without deleting and recreating your project. **Why:** Migrating to a new repo or pointing Sitepins to a different source is now a settings change, not a full rebuild. Just disconnect or switch from the settings page. ​ #### Edit Configs as Code ![](/images/blog/product-update-february-2026/edit-config-as-code.png) **What:** Power users can now edit Sitepins’ configuration files directly as code within the editor. **Why:** Visual settings work great for most users. But when you need to tweak a config file directly, this gives you full control without ever leaving the browser. ​ #### UI/UX Overhaul **What:** We implemented a new design system, bringing a more consistent, accessible, and modern look across every part of the application. **Why:** Adopting a modern, accessible component library means faster performance, better navigation and a more consistent feel across every button, modal and menu. The CMS now would feel lighter and more responsive than ever. ​ #### Bug Fixes and Stability Issues We also shipped minor bug fixes and stability improvements to keep everything running smoothly. ​ ### Closing: As we speak, over 800 users are trusting Sitepins to manage their static sites.We’re constantly shipping updates and patches based on your feedback: building a tool that genuinely simplifies your daily workflow. If you’re already using Sitepins, we’d love to hear your feedback. If you’re new, [**try it today**](https://sitepins.com/pricing) and see how you can streamline content management for you, your team or clients. - [**Our Roadmap**](https://updates.sitepins.com/) - [**Follow us on X**](https://x.com/sitepinscms) - [**Join Our Discord Community**](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-february-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's new in Sitepins — January 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-january-2026 Sitepins CMS January 2026: Deploy to Vercel instantly, 100+ Astro/Hugo/Next.js templates, GitLab integration, email-based access & improved SEO tools. See what's new. # What's new in Sitepins — January 2026 - Farhad | Redwan - February 01, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's new in Sitepins — January 2026](/_vercel/image?url=_astro%2Fwhat-new-sitepins-2026.CymELbSH.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) We kicked off 2026 with some major updates. This month’s release is all about improving your experience and providing more flexibility. We’ve focused on removing friction, enhancing collaboration, and giving you more control over your workflow. Here’s everything we shipped this month: ### TL;DR - **100+ Pre-configured Templates** — One-click setup with Astro, Hugo, and Next.js templates. - **Vercel Deployment** — Deploy and auto-sync changes directly from Sitepins. - **GitLab Integration** — Now supporting GitLab alongside GitHub - **Email-based Access** — Grant access to teammates and clients without requiring Git accounts. - **GitHub Branching Support** — Manage branches, create PRs, and merge directly from Sitepins - **SEO Suggestion Improvements** — More accurate SEO suggestions and SERP preview. - **Global Search** — Find files easily with Cmd/Ctrl + K - **Media File Rename** — Rename files directly in the CMS - **UI/UX Revamp** — A more polished, consistent, and user-friendly experience - **Bug Fixes** — Various bug fixes and performance improvements ​ ## 100+ Pre-configured Templates ![](/images/blog/product-updates/100-themes.png) **What:** We’ve added over [100+ pre-configured templates](https://app.sitepins.com/templates) built with Astro, Hugo, and Next.js by Themefisher and Gethugothemes. **Why:** If you’re creating a new site, choose your preferred template and customize it directly in Sitepins. They’re pre-configured, so there’s nothing to set up — one click and you’re ready to go. ## Deploy to Vercel ![sitepins-deploy-vercel](/images/blog/product-updates/sitepins-to-vercel-deploy.png) **What:** Direct Vercel deployment from Sitepins with automatic sync for every content change. **Why:** If your site isn’t published yet, Vercel is a great choice. Connect your repository to Vercel directly from Sitepins. Every time you make a change, Git automatically triggers a rebuild and Vercel updates your site. You’ll see your changes live almost instantly. No manual builds, no deployment steps, just a seamless pipeline from editing to production. _(Note: We’re not affiliated with Vercel, we just love the product.)_ ## GitLab Repository Support ![gitlab-sitepins-support](/images/blog/product-updates/sitepins-gitlab.png) **What:** In addition to GitHub, Sitepins now supports GitLab repositories. **Why:** Many teams rely on GitLab for source control and CI/CD. This update allows Sitepins to integrate into those existing workflows without requiring repository migration or process changes. You can use Sitepins regardless of whether they prefer GitHub or GitLab. ## Multiple Branching Support ![create-gir-branch](/images/blog/product-updates/git-branch.png) **What:** Sitepins now supports full GitHub branch management. You can create branches, make changes, open pull requests, and merge them directly from the Sitepins interface. **Why:** Branching allows teams to experiment and review changes without affecting the main branch. This is useful for redesigns, content experiments, and staged updates. Developers can keep production stable while still enabling collaboration and iteration. ## Email-based Access ![email-based-action](/images/blog/product-updates/email-based-permission.png) **What:** You can now grant access using only an email address. Invited users do not need a GitHub or GitLab account. All changes are still committed through the primary Git account. **Why:** A lot of you asked for this feature, we listened. Not everyone on your team needs or wants has a GitHub/GitLab account and they don’t need one either. Your clients and non-technical team members can join your org. and start editing content without creating Git account. ## Improved SEO Suggestions ![sitepins-seo-tools](/images/blog/product-updates/sitepins-seo-tools.png) **What:** We’ve improved SEO recommendations and added small features to fine-tune the UX and on-page structure. Now, content editors can: - Edit slug within the tool - Get search previews - Content/Link Analysis tool - SEO best practice recommendations **Why:** It ensures content remains optimized for search engines. It gives users guardrails to prevent broken links or poorly formatted URLs during the editing process. ## UI/UX Revamp ![ui-ux-dasboard](/images/blog/product-updates/ui-ux-dashboard.png) **What:** The interface has been refined across the application with a more consistent left-side navigation, clearer layout, and better organization. **Why:** Project and organization switching is now simpler, key information is easier to find, and settings are more structured and accessible. These improvements help users navigate more efficiently, reducing time spent searching for options and ensuring a smoother overall experience. ​ ## Global Search (Cmd/Ctrl + K) ![global-search](/images/blog/product-updates/global-search.png) **What**: A global search feature that lets you search across the entire repository using a keyboard shortcut. **Why:** For large websites, finding the right file becomes time-consuming. Global search allows you to locate content and files instantly, improving daily workflow efficiency. ## Media File and Folder Rename ![](/images/blog/product-updates/file-folder-rename.png) **What:** Media files and folders can now be renamed directly within Sitepins. **Why:** Clear file naming improves organization, SEO, and long-term maintainability. This update allows users to manage media properly without accessing the repository directly. ## Bug Fixes and Stability Improvements **What:** January included fixes for several minor bugs affecting user experience and stability. - Fixed cursor positioning issues when switching between Markdown and Rich Text editor modes - Resolved extra HTML entities being added when using shortcodes - Fixed AI suggestions appearing across the entire document instead of only the selected text - Corrected plan name not updating after purchase or trial activation - Fixed content not rendering due to schema mismatches - and more.. **Why:** These fixes improve editor reliability and prevent unexpected issues. ## Closing: Today, all our websites are managed through Sitepins. Our content team relies on it daily, and over **600 users** (and counting) trust Sitepins to manage their sites as well. Whenever we spot bugs or opportunities for improvement, we fix them immediately. We’re committed to continuously making Sitepins better. If you’re already using Sitepins, we’d love your feedback to help us improve. If you’re new, [**try it today**](https://sitepins.com/pricing) and see how it can streamline content management for your team. - [**Our Roadmap**](https://updates.sitepins.com/roadmap) - [**Join Our Discord Community**](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-january-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's New in Sitepins — July 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-july-2026 Sitepins July 2026 update: Sitepins goes open source, improve and Advanced SEO Analyzer and security improvements. # What's New in Sitepins — July 2026 - Redwan - August 04, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's New in Sitepins — July 2026](/_vercel/image?url=_astro%2Fwhats-new-in-sitepins-july-2026.CcCEYxeg.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) July was a big one. We open-sourced Sitepins under GNU Affero General Public License Version 3.0 (AGPLv3), shipped an Advanced SEO Analyzer for Team plans and up, and rolled out another round of quality of life and security improvements. Here’s everything we shipped in July 2026: ### TL;DR - **Sitepins is Now Open Source** — Sitepins is now open source under AGPL-3.0 - **Advanced SEO Analyzer** — Get actionable SEO recommendations directly inside the editor, available on Team plans and up. - **Bug Fixes and Security Improvements** — Security and quality of life improvements across the platform. ### Sitepins is now Open Source! ![open-source](/images/blog/sitepins-open-source-git-based-cms.png) **What:** Sitepins’ CMS is now open source under AGPL-3.0 license. You can read the full announcement, including what this means for self-hosting and contributing, here: [Sitepins CMS is now open source](https://sitepins.com/blog/sitepins-cms-is-now-open-source). **Why:** Going open source means more transparency into how Sitepins works. You can read the actual source code if you wish. That makes it easier to trust, easier to audit for security or compliance needs, and easier for the community to spot bugs, suggest fixes, or contribute improvements directly. It also gives anyone the freedom to self-host, with full control over their own infrastructure. _Note: Self-hosting and modifying Sitepins is free as long as you publish your changes when running it as a service for others, but if you want to white-label it and resell it under your own brand without that requirement, you’ll need to get in touch with us about the Agency white-label plan._ ### Advanced SEO Analyzer ![sitepins-advanced-seo-analyzer-improvements](/images/blog/product-update-july-2026/sitepins-advanced-seo-analyzer-improvements.png) **What:** Set a target keyword for any piece of content and Sitepins grades it against SEO best practices, built for how search and AI discovery work in 2026. You’ll see a 0–100 SEO score right on the SEO button, along with tips, recommendations, warnings, and a full content analysis breakdown. Results are grouped into Issues, Improvements, and Good Results, each with a specific recommendation. ![sitepins-advanced-seo-analyzer-issues-warnings](/images/blog/product-update-july-2026/sitepins-advanced-seo-analyzer-issues-warnings.png) **Why:** Most teams either skip SEO entirely or bounce out to a separate tool to check it. This puts the same checks directly in the editor, so you can fix issues before you publish instead of after. _Note: Advanced SEO is available on Team plans and higher._ ### Bug Fixes and Security Improvements This month’s fixes were focused on hardening security across the platform, tightening up a number of areas under the hood to keep your content and account safer. ### Quality of Life Improvements - Added the option to delete your profile picture from user, organization, and project settings. ### Closing Sitepins is now almost 2,000 users strong as of writing this. Since open-sourcing, we’ve already acquired 120+ (and counting) stars on GitHub. This goes to show the power of open source and the support of the community. We’re steadfast in our commitment to keeping Sitepins secure and reliable as more teams and self-hosters come on board. If you run into a bug or have thoughts on what feature you’d like next, drop them in our roadmap, Discord, or reach out to us via support. - [Our Roadmap](https://updates.sitepins.com/) - [Follow us on X](https://x.com/sitepinscms) - [Discord (Support and Community)](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-july-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's New in Sitepins — June 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-june-2026 Sitepins June 2026 update: draft saves locally, manual LLM selection, and advanced global search, bug fixes and more. # What's New in Sitepins — June 2026 - Redwan - July 07, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's New in Sitepins — June 2026](/_vercel/image?url=_astro%2Fwhats-new-in-sitepins-june-2026.BCydbFid.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) In June, we focused on smoothing out the everyday friction points in your writing and publishing workflow. We shipped a smarter way to save drafts without triggering a full rebuild, gave you the freedom to bring your own preferred LLM, and expanded global search to cover more than general settings and preferences as well. Here’s everything we shipped in June 2026: ### TL;DR - **Save as Draft Locally** — Save your work progress in the app without triggering a full site rebuild. - **Advanced Global Search** — Global search now covers organizations, settings, preferences, and support, not just files. - **Preferred LLM Input** — Choose any supported model from OpenAI, Anthropic, xAI, or Google Gemini. - **Bug Fixes and Security Updates** — A round of fixes across the platform for a smoother experience. ### **Save as Draft in the App** ![save-as-draft](/images/SP1.png) **What:** You might be mid-draft, waiting on a teammate’s review, or simply saving your progress so a closed tab or a dead battery could cost you your work. Saving as a draft now stores your content without triggering a full site rebuild. **Why:** Previously, every draft save, even for a single word or an extra space, triggered a full rebuild of the site. That is not practical, and it is not a good practice either. Now your content is stored instantly, without the overhead of rebuilding your site every time you save. ### Choose preferred LLM model ![choose-preferred-llm-model](/images/SP3.png) **What:** You are not limited to Sitepins’ default model selection. You can now manually input your preferred LLM from one of four supported providers: OpenAI, Anthropic, xAI, or Google Gemini. **Why:** Different workflows call for different models. This update gives you the flexibility to choose the LLM that best fits your use case. ### Advanced Global Search ![advanced-global-search](/images/SP2.png) **What:** Our global search has been upgraded to look beyond files. You can now search organizations, user settings, organization settings, preferences, support, and account settings, all from the same search bar. Hit CMD+K or Ctrl+K for Mac or Windows **Why:** We wanted to make it faster for users to find exactly what they are looking for without digging through multiple menus or memorizing navigation paths. This also makes Sitepins easier to navigate for non-technical users. ### Closing Sitepins has now crossed 1,700 users. We’re steadfast in our commitment to shipping updates based on feedback from the people using Sitepins every day. If you run into a bug or have thoughts on what feature you’d like next, drop them in our roadmap, Discord, or reach out to us via support. - [Our Roadmap](https://updates.sitepins.com/) - [Follow us on X](https://x.com/sitepinscms) - [Discord (Support and Community)](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-june-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's new in Sitepins — March 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-march-2026 Sitepins March 2026: live user presence indicators, external image URL support, iFrame preview in the rich editor, and a redesigned account overview. # What's new in Sitepins — March 2026 - Redwan - April 02, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's new in Sitepins — March 2026](/_vercel/image?url=_astro%2Fwhats-new-sitepins-march-2026.BCdxOjAr.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) We’ve been taking feedbacks from teams actually using Sitepins on their daily workflow, and this month’s updates reflect that. We focused mainly on user experience: live indication of who’s on the same file, more freedom with how you handle images, richer embed support in the editor, and a cleaner look at your account health. Here’s everything we shipped in March 2026: ### TL;DR - **Live user presence indicators** — Live avatar displays on the editor shows who’s currently on the same file. - **External Image URL Support** — Paste any external image URL directly into the editor - **iFrame Preview in Rich Editor** — Embed and preview iFrames (like YouTube videos) live inside the editor - **Account Overview Refresh**— A cleaner, more informative dashboard with proper metrics * * * ### Real-time User Indication ![](/images/blog/product-update-march-2026/live-avatar-idicators.png) **What:** Sitepins now displays live avatar indicators in the editor’s top bar, showing all users who are currently active on the same file as you. The presence updates in real time, so the moment someone opens or leaves a file, the indicator reflects that instantly. Hovering over any avatar reveals the user’s name, giving you a clear picture of exactly who is on the file at any given moment. **Why:** When multiple team members are working across the same files, it’s easy to step on each other’s work without knowing it. Seeing who’s present on a file at a glance helps teams coordinate better and avoid conflicts before they happen. * * * ### External Image URL Support ![](/images/blog/product-update-march-2026/external-image-url-support.png) **What:** The rich text editor now supports two types of image paths: relative paths (images stored in your repository) and absolute URLs (externally hosted images). **Why:** If you’re pulling assets from a CDN, a third-party service, or any external host, you no longer need to download and re-upload them. Just paste the URL and continue. * * * ### iFrame Preview in Rich Editor ![](/images/blog/product-update-march-2026/iframe-preview.png) **What:** The rich editor now renders a live preview of iFrames directly inside the HTML block. Write your embed code, and the preview appears right below it instantly. You can also modify the properties and see the changes reflected in the preview in real time. **Why:** Writing raw iFrame code and guessing what it’ll look like is not a practical approach. With live preview, you can verify exactly how your embed will appear to readers before hitting publish, saving you the back and forth of publishing just to check. _Note: This was a requested feature. One of our users reported that their team embeds charts as iFrames and found it difficult to reference the iFrame content in a separate window while writing inside Sitepins at the same time. The live preview eliminates that context switching entirely._ * * * ### Account Overview Refresh ![](/images/blog/product-update-march-2026/account-overview-ui.png) **What:** The Account Overview page has been refined to give you a clearer, more structured view of your account at a glance. It now displays your current plan, your organization count, number of sites, and users per organization, each with a usage indicator showing how much of your plan’s allocation you’ve used. **Why:** The new design surfaces the right numbers in the right places, so you always know your plan limits and can keep track of your billing history. * * * ### Closing As of writing this we are closing in on 1,000 users, a milestone we’re proud of. We’re committed to continuously improving Sitepins, shipping updates that make content management simpler and easier for everyone. Got an issue? Reach us on Discord. Have a feature request or feedback? Drop it on our Roadmap page. - [**Our Roadmap**](https://updates.sitepins.com/) - [**Follow us on X**](https://x.com/sitepinscms) - [**Join Our Discord Community**](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-march-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## What's New in Sitepins — May 2026 URL: https://sitepins.com/blog/whats-new-in-sitepins-may-2026 Sitepins May 2026 update: live preview, native multilingual support, real-time collaborative editing, and quality-of-life improvements across the CMS. # What's New in Sitepins — May 2026 - Redwan - June 03, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![What's New in Sitepins — May 2026](/_vercel/image?url=_astro%2Fwhats-new-in-sitepins-may-2026.BLZ2v1Zh.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) In May, we focused on pushing features that make content management more transparent and accessible to everyone. We implemented native multilingual support across 12 languages, introduced a live preview system for a better content editing experience, enabled real-time collaborative editing, and shipped a few quality-of-life improvements across Sitepins. Here’s everything we shipped in May 2026: ### TL;DR - **Live Preview System** — See your content changes reflected in real time before you publish. - **Multilingual Support (12 Languages)** — Sitepins now supports 12 languages natively. - **Collaborative Editing** — Live cursors and name labels show exactly who’s editing and where. - **Quality-of-Life Improvements** — Small user experience improvements across the entire CMS ​ ### Live Preview System ![live-preview-your-content](/images/blog/product-update-may-2026/live-preview.png) **What:** Sitepins now shows a live preview of your content as a web page and it would update dynamically as you make changes in the editor. What you see in the preview is exactly what will appear on the page once published. **Why:** A common issue editors ran into was content that looked fine in the editor but came out with unexpected formatting or layout issues after publishing. With live preview, you can verify how everything looks before it goes live, so there are no surprises after the fact. ​ ### Multilingual Support ![multilingual-support](/images/blog/product-update-may-2026/multilingual-support.png) **What:** We have expanded Sitepins’ native multilingual support to 12 languages (as of writing this). The full list now includes: - English (en) - Chinese (中文, zh) - Japanese (日本語, ja) - German (Deutsch, de) - French (Français, fr) - Spanish (Español, es) - Portuguese (Português, pt) - Russian (Русский, ru) - Korean (한국어, ko) - Indonesian (Bahasa Indonesia, id) - Vietnamese (Tiếng Việt, vi) - Bengali (বাংলা, bn) **Why:** Our users come from all over the world, and browser-based translation tools do not always produce accurate results. Native language support means enables editors to manage their content in their own language without having to rely on any third-party tools. > Read about Sitepins’ native i18n support: [Sitepins Now Speaks Your Language](https://sitepins.com/blog/sitepins-i18n-launch)​ ​ ### Collaborative Editing ![collaborative-editing](/images/blog/product-update-may-2026/collaborative-editing.png) **What:** Improving on the live avatar indicators we launched in March, collaborative editing now goes a step further. You can see other users’ cursor placements in real time, with their names displayed alongside, similar to Google Docs. You always know who is on the file, where they are, and what they are changing as it happens. **Why:** When multiple people work on the same file without any visibility into each other’s edits, it is easy to overwrite someone else’s changes without realizing it. Seeing exactly where each person is and what they are doing reduces editing conflicts. ​ ### Quality-of-Life Improvements A few smaller updates worth noting: - **Global Search is now visible.** Always accessible via `cmd + k` on Mac and `ctrl + k` on Windows, it now also appears as a visible element in the top left corner of the CMS. - **Build status indicators** have been improved for a clearer read on where your build stands. - **Recent File Changes** now captures the full picture: renames, updates, and other modifications, not just content edits. ​ ### Closing At Sitepins, we remain steadfast in our commitment to shipping updates that make your content management experience smoother and more reliable, all aimed at enhancing your experience and streamlining your workflow. If you are already using Sitepins, we would love to hear your feedback. Reach us on Discord or [contact us directly](https://sitepins.com/contact). - [Our Roadmap](https://updates.sitepins.com/) - [Follow us on X](https://x.com/sitepinscms) - [Discord (Support and Community)](https://discord.gg/SuNEuX2eFj) ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/whats-new-in-sitepins-may-2026) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## When Not to Use an API Based Headless CMS with Astro or Next.js URL: https://sitepins.com/blog/when-not-to-use-headless-cms Headless CMS is not the right fit for every Astro or Next.js project. Learn the exact situations where skipping it saves time, money, and complexity. # When Not to Use an API Based Headless CMS with Astro or Next.js - Farhad - May 11, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![When Not to Use an API-Based Headless CMS with Astro or Next.js](/_vercel/image?url=_astro%2Fwhen-not-to-use-api-based-headless-cms.CckSL2CJ.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Headless CMS is not the right fit for every Astro or Next.js project. Learn the exact situations where skipping it saves time, money, and complexity. ## TL;DR - A headless CMS is the wrong choice when your content rarely changes and your team has no one who can manage API credentials, webhooks, or build pipelines. - Small sites with under 50 pages and a single author get slower builds and higher bills from a headless setup, not better performance. - If your content editors need real-time preview, layout control, or drag-and-drop page building, most headless CMSes will frustrate them without significant custom development. - Git-based tools like Sitepins are often faster, cheaper, and easier to maintain for developer-owned projects in Astro or Next.js. - Use a headless CMS when content is high-volume, multi-channel, or managed by a non-technical team at scale - not by default just because you’re using a modern framework. ## What Is an API-Based Headless CMS? An **API-based headless CMS** is a content management system that stores your content in the cloud and delivers it to your site through an API (usually REST or GraphQL). The “headless” part means it has no built-in frontend. It gives you the data, and your framework (Astro, Next.js, etc.) renders it. Popular examples include Contentful, Sanity, Storyblok, Hygraph, and Payload CMS. They work well for the right projects. The problem is that developers often reach for them by default when building with modern frameworks, regardless of whether the project actually needs them. ## Why Developers Default to Headless CMS and When That Goes Wrong The assumption is: modern framework + headless CMS = professional setup. That logic breaks down fast on smaller or simpler projects. A headless CMS adds at least three moving parts your project didn’t have before: an external API dependency, a webhook-triggered build pipeline, and a separate login system for content editors. On a marketing site with 20 pages that gets updated once a month, those parts create overhead without solving any real problem. The actual question to ask before adding any headless CMS is: who is editing this content, how often, and does the delivery mechanism matter? If the answer is “a developer, rarely, and no,” you probably don’t need one. ## 6 Situations Where You Should Skip the Headless CMS ### 1\. Your Site Has Under 50 Pages and One Content Author Small sites don’t benefit from a headless CMS. If your Astro or Next.js project has a handful of blog posts, a few landing pages, and one person writing everything, MDX files in your repo are simpler and faster. With a Git-based setup, content lives in the same repository as your code. You edit a file, push a commit, and the site rebuilds. There’s no API token to rotate, no CMS dashboard to manage, and no third-party service in your critical path. Tools like **Sitepins** give you a clean editing UI on top of that Git workflow, so non-developers can still write content without touching a terminal. Astro’s content collections and Next.js’s `next-mdx-remote` both handle this setup cleanly without any external API dependency. ### 2\. Your Content Editors Need Real-Time Visual Editing Most API-based headless CMSes separate content entry from layout. An editor writes text in a structured form (title field, body field, image field), and a developer controls how that content looks on the page. That works fine for blog posts. It falls apart when your client or content team expects to drag elements around, adjust spacing, or build page sections visually without filing a developer ticket. Tools like Storyblok offer a visual editor, but even then, getting it to work correctly with Next.js or Astro requires custom block mapping, rendering logic, and non-trivial configuration. If your project needs true visual page building, a headless CMS is not the right tool. A builder like Framer, Webflow, or a WordPress block editor will match the editorial workflow better. ### 3\. You’re Building a Static Site That Rarely Changes Astro is purpose-built for static output. If you’re building a documentation site, a portfolio, or a company brochure site that gets updated a few times a year, pulling content from a remote API on every build is unnecessary complexity. The API-based model works well when content changes frequently enough to justify the pipeline. A site that changes quarterly doesn’t need a CMS with webhooks, build triggers, and API rate limits. It needs a Markdown file in a folder and a tool like Sitepins to edit it without leaving the browser. ### 4\. Your Budget Can’t Support API Pricing at Scale Free tiers on headless CMSes are narrow. Contentful’s free tier currently allows for 100,000 API calls per month and 25,000 content records, an increase from previous years though it remains restricted to a single starter space. Sanity’s free tier is more flexible but can be stricter on traffic, offering 1,000,000 API CDN requests and 250,000 direct API requests monthly with a 100GB bandwidth limit. For a high traffic site, those limits hit fast. A marketing site getting 100,000 monthly visitors with Incremental Static Regeneration (ISR) in Next.js can easily consume API credits across preview requests, build time fetches, and on demand revalidation. Once you exceed the free tier, costs can reach $300 to $500 per month for mid tier plans. For example, Contentful’s Basic plan starts at $300 per month for a single project. These costs mount before you have paid for hosting, monitoring, or anything else. If budget is fixed and traffic is meaningful, the API cost structure of a headless CMS deserves a serious look before you commit to it. ### 5\. Your Team Has No One to Manage the Integration An API-based CMS is not plug-and-play with Astro or Next.js. Someone has to write the data-fetching logic, handle API errors, configure environment variables, set up webhooks to trigger builds on content changes, and test the pipeline end to end. In a small team or solo project, that work lands entirely on the developer. And it’s ongoing: API versions change, tokens expire, webhook endpoints break when you migrate hosting. If no one on the team owns that integration, it will eventually fail silently - content won’t update, builds won’t trigger, and debugging it means digging through logs across three separate platforms. For projects without a dedicated developer to maintain the integration, a Git-based CMS like **Sitepins** is easier to keep running. Content stays in your repo, there’s no external API to break, and the editing interface works without any custom integration code. ### 6\. Your Content Is Highly Relational and Deeply Structured This one surprises people. Headless CMSes are good at delivering flat or lightly structured content. They get painful when your content has deep relationships: posts with multiple authors, each author linked to a bio, each bio linked to a department, each department linked to projects. Querying deeply relational content through a REST or GraphQL API means either making multiple round-trip requests (slow) or writing elaborate GraphQL queries that are fragile when schema changes. A traditional relational database with a server-rendered framework handles this more naturally. If your data model looks like a database schema with foreign keys, build it like one. ## Git-Based CMS vs. API-Based CMS: Which Fits Your Project Factor Git-Based (Sitepins, Decap) API-Based (Contentful, Sanity) Content editors Developers and content editor comfortable with Git Non-technical editors at scale Page count Under 200 pages Hundreds to thousands Update frequency Infrequent (weekly or less) Daily or continuous Multi-channel delivery Single site Multiple apps, sites, or platforms Budget Free or less than $20 month $50 - $500 month at scale Setup complexity Low Medium to high API dependency None Yes - external service required ## When an API-Based Headless CMS Is the Right Call To be direct: headless CMSes are genuinely good for specific situations. Use one when your content team is non-technical and needs a proper editing interface, when you’re delivering content to more than one frontend (a website, a mobile app, and a digital display, for example), or when your site publishes dozens of pieces of content per week and needs editorial workflows like drafts, approvals, and scheduled publishing. Next.js’s ISR and Astro’s on-demand rendering modes are built with this use case in mind. At that volume and complexity, the API overhead is worth it. The mistake is treating headless CMS as a default architectural choice for every Next.js or Astro project. It’s a tool for a specific job. When the job is simpler, use a simpler tool. ## Common Mistakes Teams Make When Choosing a Headless CMS - Picking a CMS before defining who will edit content and how often. If the answer is “a developer, occasionally,” you don’t need a CMS at all. - Assuming the free tier will last. Most projects outgrow free tiers within 6 to 12 months once traffic and content volume grow. - Building around the CMS’s data model instead of your content’s actual structure. Shoehorning relational data into a CMS’s field types creates technical debt that compounds over time. - Skipping the webhook pipeline in development and then discovering it doesn’t work on the first content update in production. - Choosing a CMS because it has good documentation for React, without checking whether it has a proper Astro integration. Several major CMS platforms still lack first-party Astro SDK support as of 2026. ## What to Use Instead: A Quick Decision Guide If your project fits any of the scenarios above where headless CMS doesn’t make sense, here’s what to reach for instead: - **Static site with developer-owned content:** Astro content collections with MDX files. No external dependency, zero cost, full type safety with Zod schemas. - **Small site needing a non-technical editing UI:** Sitepins (Git-based, works with Astro and Next.js out of the box), Tina CMS, or Decap CMS. - **Complex page-building requirements:** Storyblok (if staying headless) or Webflow/Framer (if the whole site can live there). - **Deep relational data:** A PostgreSQL database with Prisma and a server-rendered Next.js app, or a traditional CMS like WordPress used headlessly only if multi-channel delivery is actually needed. The framework doesn’t decide the CMS. The content workflow does. ## Frequently Asked Questions About Headless CMS with Astro and Next.js ### What is an API-based headless CMS? An API-based headless CMS stores your content in a cloud-hosted system and delivers it to your site through a REST or GraphQL API. Your frontend framework like Astro, Next.js, or anything else fetches that content at build time or request time and renders it. The CMS has no frontend of its own; it only manages and delivers data. ### Is a headless CMS necessary for Astro or Next.js projects? No. Both Astro and Next.js work fine with local Markdown or MDX files, Git-based CMSes, or no CMS at all. A headless CMS is the right choice when a non-technical team manages content at volume. For developer-owned projects or small sites, it adds complexity without a clear benefit. ### What is the difference between a Git-based CMS and an API-based CMS? A Git-based CMS (like Sitepins, Decap CMS) stores content as files in your Git repository and lets editors manage that content through a UI without touching Git directly. An API-based CMS (like Contentful or Sanity) stores content on external servers and delivers it through an API. Git-based options are simpler and free but less suited for large editorial teams. API-based options scale better for multi-user, multi-channel publishing but cost more and require active integration maintenance. ### What happens to my site if the headless CMS API goes down? If you’re using static generation (SSG) in Astro or Next.js, your published site stays up - it’s already built. But new builds will fail until the API comes back online, meaning content updates won’t go live. If you’re using server-side rendering (SSR) or on-demand revalidation, API downtime can directly affect live pages. This is a real availability risk that needs a caching strategy to manage. ### Can I switch from a headless CMS to MDX files later? Yes, but it takes real work. You’ll need to export your content from the CMS, reformat it as Markdown or MDX, restructure your data-fetching code, and rebuild your content pipelines. Most headless CMSes export to JSON, so migration is possible. Plan for a week or more of engineering time depending on content volume. Doing this migration on a 500-post blog is significantly more effort than on a 20-page marketing site. ### Which headless CMS works best with Astro? As of 2026, Storyblok, Sanity, and Hygraph remain the top recommendations for Astro due to their mature, dedicated integrations. Contentful has also streamlined its experience, now offering an official Contentful SDK for Astro that simplifies data fetching without needing manual logic or extra client side JavaScript. For Git-based workflows, **Sitepins** has become a popular Git-based choice for Astro projects. Sitepins connects directly to your GitHub repository and adds a clean, visual WYSIWYG editing layer over your Markdown or MDX files without requiring a separate database. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/when-not-to-use-headless-cms) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## 6 Signs It's Time to Leave WordPress (And What to Use Instead) URL: https://sitepins.com/blog/wordpress-alternatives Is WordPress slowing you down? Learn the clear signs it's time to switch and which alternatives like Astro, Hugo, Next.js, and more fit your situation. # 6 Signs It's Time to Leave WordPress (And What to Use Instead) - Farhad - July 12, 2026 ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![6 Signs It's Time to Leave WordPress (And What to Use Instead)](/_vercel/image?url=_astro%2Fwordpress-alternatives.BFPmRCaZ.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Quick Summary - WordPress powers **41.9%** of all websites as of 2026, but market share does not mean it is the right fit for every project. - The clearest signs you have outgrown it: pages that stay slow despite optimization, a plugin stack that breaks on updates, and a security maintenance cycle that never ends. - Only **38%** of WordPress sites pass all Core Web Vitals on mobile, compared to **58%** for Next.js sites. - Static site generators (Astro, Hugo, Next.js) and Headless CMSs are the most common exits for developer teams. - Migration takes **4-16** weeks depending on site complexity. This guide helps you decide if it is worth it now. ## What “Leaving WordPress” Actually Means Leaving WordPress means replacing it as your content management and publishing layer not necessarily rebuilding everything from scratch. For some teams, that means switching to a static site generator with a Git-based CMS. For others, it means going headless with a decoupled frontend. The path depends on your content workflow, your team’s technical comfort, and how much of the WordPress ecosystem you actually use. The decision is not about WordPress being bad. It powers 41.9% of the web for a reason [(W3Techs, 2026)](https://w3techs.com/technologies/details/cm-wordpress). It is about whether it is the right fit for where your site is now. ### Sign 1: Your Site Is Slow and Optimization Has Stopped Working A well-optimized WordPress site can pass Core Web Vitals. The problem is “well-optimized” typically means running a caching plugin, a CDN, an image optimization plugin, and a performance plugin simultaneously just to reach scores that static sites hit by default. **Only 38% of WordPress sites pass all Core Web Vitals on mobile.** Next.js sites pass at 58%. The gap comes down to architecture: WordPress renders PHP on every request and runs database queries, while static sites serve pre-built HTML directly from a CDN [(Digital Applied, 2026)](https://www.digitalapplied.com/blog/page-speed-statistics-2026-revenue-impact). WordPress sites on shared hosting average a TTFB of 900ms to 1,400ms at the 75th percentile. The same content on a static site served from Cloudflare Pages, Vercel or Netlify typically comes in under 200ms with no configuration [(CoreWebVitals.io, 2026)](https://www.corewebvitals.io/core-web-vitals/wordpress-guide). Speed is not just a UX issue. Google uses Core Web Vitals as a ranking signal, and a **one-second delay in page load costs approximately 7% in conversions** [(Colorlib, 2026)](https://colorlib.com/wp/site-speed-statistics/). ### Sign 2: Plugin Conflicts Are a Regular Part of Your Month WordPress has over 70,000 plugins in its official directory as of 2026 [(WPBeing, 2026)](https://wpbeing.com/wordpress-statistics/). That sounds like an advantage until you are debugging why your contact form stopped working after a WooCommerce update, or why your SEO plugin is conflicting with your page builder. Each plugin is a dependency. Each dependency can break when another updates. If you are spending more than a few hours a month on plugin-related debugging, that cost compounds over the year. Static and headless setups move this logic out of the CMS. Functionality like forms, search, and e-commerce goes to dedicated third-party services (Netlify Forms, Algolia, Stripe) that operate independently. There is no plugin ecosystem to manage, and there are no inter-plugin conflicts to diagnose. ### Sign 3: Security Patching Is a Job of Its Own WordPress faces an outsized security burden, not because its core is weak, but because its scale makes it the most targeted CMS on the internet. **In 2025 alone, 11,334 new vulnerabilities were identified in the WordPress ecosystem, a 42% increase year-on-year. Of those, 91% were in plugins, not WordPress core** [(Patchstack, 2026).](https://patchstack.com/whitepaper/state-of-wordpress-security-in-2026/)​ The exploitation window has also narrowed. The median time from vulnerability disclosure to active exploitation is now five hours for the most targeted flaws. Staying on top of updates is no longer enough on its own. 46% of disclosed vulnerabilities had no developer patch available at the time of disclosure [(Colorlib, 2026)](https://colorlib.com/wp/wordpress-hacking-statistics/). Static sites have no server-side execution layer to attack. There is no login page, no database, no PHP interpreter exposed to the web. The attack surface drops to near zero, and so does the maintenance burden. ### Sign 4: Your Hosting Bill Does Not Match Your Traffic WordPress needs a server capable of running PHP and MySQL. For anything beyond light traffic, you are typically looking at managed WordPress hosting at $30 - $100 per month, and that scales up as traffic grows. Static sites hosted on Netlify, Vercel, or Cloudflare Pages cost nothing for most traffic levels. Serving static files from a CDN is cheap at scale because there is no compute happening on each request - just file delivery. High-traffic static sites routinely stay within free or near-free hosting tiers. If your hosting cost is growing faster than your traffic or revenue, that is a sign the infrastructure does not fit the use case. ### Sign 5: Your Content Team Needs Features WordPress Cannot Model Well WordPress was built for blogs. It handles editorial content well in that context. But if your team needs structured content modeling, multi-language publishing, content previews across channels, or API-first access, WordPress starts to show its limits. The Classic Editor and Gutenberg are page editors, not content modeling tools. Building a well-structured content schema in WordPress requires Advanced Custom Fields or similar plugins and those add maintenance overhead and another layer of update risk. Dedicated headless CMSs are built around content modeling from the ground up. They expose content via API and work with any frontend. Git-based CMSs like [**Sitepins**](https://sitepins.com/) store content directly in your GitHub repository alongside code, removing the database entirely and making content changes part of your normal Git workflow. ### Sign 6: Your Developers Have Stopped Enjoying the Work Developer experience matters for retention and velocity. WordPress development in 2026 still means PHP, MySQL, and a local environment that can behave differently from production. Git-based workflows are possible but not native. CI/CD pipelines require manual configuration. Modern JavaScript frameworks ship with Git-native workflows, hot module reloading, component-based architecture, and deployment pipelines that connect directly to GitHub or GitLab. The development experience gap between WordPress and these tools has grown significantly. The State of JavaScript 2025 survey found that Astro leads meta-framework satisfaction by a 39-percentage-point margin over Next.js - signaling a broader shift toward content-focused, lighter-weight architectures [(State of JS, 2025)](https://2025.stateofjs.com/en-US/about). If recruiting or retaining developers is a concern, the tooling you run is part of the conversation. ## What to Use Instead: Matching Your Situation to the Right Tool The right alternative depends on your content workflow, team, and technical tolerance. Situation Recommended Direction Dev team comfortable with JS, content mostly editorial Astro + Git-based CMS ( e.g. Sitepins ) Large site with complex content modeling Next.js + Contentful or Sanity E-commerce with high traffic Shopify or Next.js + Headless Shopify Agency managing 20+ client sites Astro, Hugo or Next.Js SSG with a shared CMS layer Mostly static, occasional dynamic features Astro with API routes or Cloudflare Workers Enterprise full-stack app with auth and dynamic data Next.js ### Astro: For Developer Teams Building Content-Heavy Sites ​[Astro](https://astro.build/) ships zero JavaScript by default and outputs static HTML. It supports React, Vue, Svelte, and other frameworks within the same project via its islands architecture. In January 2026, Cloudflare acquired the Astro Technology Company the framework stays MIT-licensed and open source, but now has direct edge infrastructure backing. Astro’s LCP metrics run 40-70% better than Next.js for content-focused sites [(Agile Soft Labs, 2026).](https://www.agilesoftlabs.com/blog/2026/03/nextjs-vs-remix-vs-astro-best)​ **Astro is best for:** Marketing sites, documentation, developer blogs, content-heavy pages where performance is the priority. ### Hugo: For Speed and Scale With Minimal Build Time ​[Hugo](https://gohugo.io/) builds sites faster than any other static site generator, typically under one second for sites with thousands of pages. It is written in Go, has no Node.js dependency, and has a mature, stable theme ecosystem. **Hugo is best for:** Large sites, blogs, documentation, and teams that do not want a Node.js dependency in their build pipeline. ### Next.js: For Teams That Need Both Static and Dynamic ​[Next.js](https://nextjs.org/) supports static generation, server-side rendering, and incremental static regeneration in the same project. It holds 67% of new enterprise React projects and dominates in SaaS and B2B applications (Agile Soft Labs, 2026). **Nextjs is best for:** E-commerce, SaaS marketing sites, applications with authenticated content, teams already running React. ### Headless CMS Options Worth Knowing - **Contentful** - Enterprise-grade content modeling, strong API, pricing scales with usage - **Sanity** - Flexible schema, real-time collaboration, strong developer experience - **Sitepins** - Git-based, no database, built for Astro, Hugo, Next.js and more, editor-friendly interface. - **Decap (formerly Netlify CMS)** - Open source, Git-based, free to self-host ## How to Decide If the Switch Is Worth It Right Now Migration has a real cost. **A typical WordPress-to-static migration for a content site takes 4-12 weeks depending on content volume, custom functionality, and team familiarity with the target stack.** That is before factoring in URL redirect mapping and editor retraining. Ask these questions before committing: 1. Is the current pain costing more than 4-12 weeks of engineering time per year? 2. Does your team have a developer (or agency) experienced with the target stack? 3. Can content editors adapt to a new interface, or does that require dedicated retraining time? 4. Are there custom WordPress features (WooCommerce, membership plugins, forms) that need direct replacements before launch? If the answers are mostly yes, no, yes, no - the migration will likely pay back within the first year. ## Common Mistakes When Leaving WordPress - **Migrating content manually instead of using a script**: WordPress exports XML. Most static site tools have importers or migration scripts. Use them before touching anything manually. - **Ignoring redirect mapping**: Every URL change without a 301 redirect is a lost backlink and a broken user experience. Map all existing URLs before launch day. - **Picking the most complex stack instead of the right one**: A headless setup with three API services is overkill for a 20-page marketing site. Match architecture to actual need. - **Forgetting editor training**: Developers are comfortable with Git. Editors are not. Budget time for this before you go live, not after. - **Not testing forms, search, and dynamic features early**: These are the most common post-migration failure points and the hardest to fix under deadline pressure. ## Frequently Asked Questions About Leaving WordPress ### When should you leave WordPress? Leave WordPress when the maintenance cost like security patches, plugin conflicts, performance fixes regularly consumes developer time that could go toward features or content. If you spend more than a few hours a month managing WordPress itself rather than the site it runs, that is a clear signal worth acting on. ### Is WordPress still worth using in 2026? Yes, for the right use cases. WordPress remains a strong choice for non-technical teams who need a full CMS with a large plugin ecosystem. It becomes the wrong choice when performance, security maintenance, or modern development workflows are priorities. The platform still powers 43.4% of the web but developer-led new projects are increasingly choosing JavaScript frameworks instead. ### What is the best WordPress alternative for developer teams in 2026? Astro is the default recommendation for most new content sites in 2026. It ships zero JavaScript by default, supports every major frontend framework, and since Cloudflare’s acquisition in January 2026, has direct edge infrastructure backing. Hugo is the better choice for large sites or agencies where build speed is a constraint. ### What happens to SEO when you leave WordPress? SEO does not depend on WordPress. What matters is preserving your URL structure with 301 redirects, keeping content quality consistent, and maintaining or improving Core Web Vitals scores. Static sites almost always improve on the latter. Next.js sites pass Core Web Vitals at 58% versus 38% for WordPress on mobile. ### How long does a WordPress migration take? A simple blog with under 200 posts typically migrates in 2-4 weeks. A site with custom post types, e-commerce, or membership functionality takes 8-16 weeks. Timeline depends heavily on whether you have a developer familiar with the target stack. ### Can you keep WordPress just for content editing and use a different frontend? Yes. This is the headless WordPress approach. WordPress handles content via its admin, and a separate frontend (Next.js, Astro) pulls content through the WordPress REST API or WPGraphQL. You keep the editorial workflow and gain a faster, modern frontend. The tradeoff is higher setup and maintenance complexity compared to switching to a purpose-built headless CMS. ## Key Takeaways - The decision to leave WordPress is about fit. It makes sense when maintenance overhead, performance ceilings, or developer friction cost more than migration would. - Static site generators (Astro, Hugo, Next.js) eliminate the server-side attack surface, deliver faster Core Web Vitals scores, and cut hosting costs significantly. - Git-based CMSs like Sitepins give content teams a clean editing interface without a database or plugin stack to maintain. - Migration costs are real. Budget 4-16 weeks depending on site complexity, and map every URL redirect before launch. - Headless WordPress is a middle path worth considering if your team is invested in the WordPress editor but wants a modern, faster frontend. ##### Share this story : - [](https://facebook.com/sharer/sharer.php?u=https://sitepins.com/wordpress-alternatives) - []() - []() - []() ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Categories URL: https://sitepins.com/categories Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. All Categories # Categories ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) - [Headless 2](/categories/headless) - [Cms 9](/categories/cms) - [Seo 1](/categories/seo) - [Git based 2](/categories/git-based) - [Astro 2](/categories/astro) - [Comparison 1](/categories/comparison) - [Api first 1](/categories/api-first) - [Static site 1](/categories/static-site) - [Others 1](/categories/others) - [Announcement 1](/categories/announcement) - [I18n 1](/categories/i18n) - [Web development 1](/categories/web-development) --- ## Announcement URL: https://sitepins.com/categories/announcement Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Announcement ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Sitepins Now Speaks Your Language: Native i18n Support Is Here](/_vercel/image?url=_astro%2Fsitepins-i18n-support.BhlgOUOm.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/sitepins-i18n-launch) [Announcement,](/categories/announcement)[I18n](/categories/i18n) #### [Sitepins Now Speaks Your Language: Native i18n Support Is Here](/blog/sitepins-i18n-launch) - Farhad - June 03, 2026 --- ## Api first URL: https://sitepins.com/categories/api-first Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Api first ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Git-Based vs. API-First Headless CMS: The Ultimate Comparison ](/_vercel/image?url=_astro%2Fgit-based-cms-vs-api-first-cms.DupST9ld.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/git-based-vs-api-based) [CMS,](/categories/cms)[API First,](/categories/api-first)[Git Based](/categories/git-based) #### [Git-Based vs. API-First Headless CMS: The Ultimate Comparison](/blog/git-based-vs-api-based) - Redwan - February 23, 2026 --- ## Astro URL: https://sitepins.com/categories/astro Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Astro ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Astro Visual Editor: Give Non-Technical Users Edit Access](/_vercel/image?url=_astro%2Fvisual-editor-for-astro.Ct6sFj2h.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/visual-editor-for-astro-websites) [Astro,](/categories/astro)[CMS](/categories/cms) #### [Astro Visual Editor: Give Non-Technical Users Edit Access](/blog/visual-editor-for-astro-websites) - Farhad - August 24, 2026 [![EmDash vs Sitepins: Best Headless CMS for Astro](/_vercel/image?url=_astro%2Femdash-cms-vs-sitepins-cms.Djf6zKrT.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/emdash-vs-sitepins-headless-cms-for-astro) [Astro,](/categories/astro)[Comparison](/categories/comparison) #### [EmDash vs Sitepins: Best Headless CMS for Astro](/blog/emdash-vs-sitepins-headless-cms-for-astro) - Farhad - April 05, 2026 --- ## Cms URL: https://sitepins.com/categories/cms Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Cms ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Astro Visual Editor: Give Non-Technical Users Edit Access](/_vercel/image?url=_astro%2Fvisual-editor-for-astro.Ct6sFj2h.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/visual-editor-for-astro-websites) [Astro,](/categories/astro)[CMS](/categories/cms) #### [Astro Visual Editor: Give Non-Technical Users Edit Access](/blog/visual-editor-for-astro-websites) - Farhad - August 24, 2026 [![What is a Git-based Headless CMS? ](/_vercel/image?url=_astro%2Fgit-based-headless-cms.D5iAl43B.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/git-based-headless-cms) [CMS](/categories/cms) #### [What is a Git-based Headless CMS?](/blog/git-based-headless-cms) - Redwan - July 27, 2026 [![6 Signs It's Time to Leave WordPress (And What to Use Instead)](/_vercel/image?url=_astro%2Fwordpress-alternatives.BFPmRCaZ.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/wordpress-alternatives) [CMS,](/categories/cms)[Web Development](/categories/web-development) #### [6 Signs It's Time to Leave WordPress (And What to Use Instead)](/blog/wordpress-alternatives) - Farhad - July 12, 2026 [![6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/_vercel/image?url=_astro%2Fdecapcms-alternatives.CELW-JIt.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/decapcms-alternatives) [CMS,](/categories/cms)[Git based](/categories/git-based) #### [6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/blog/decapcms-alternatives) - Farhad - June 10, 2026 [![7 Benefits of Headless CMS for Modern Web Development in 2026](/_vercel/image?url=_astro%2Fbenefits-headless-cms.DQhKO-b6.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/benefits-headless-cms) [Headless,](/categories/headless)[CMS](/categories/cms) #### [7 Benefits of Headless CMS for Modern Web Development in 2026](/blog/benefits-headless-cms) - Redwan - May 19, 2026 [![When Not to Use an API-Based Headless CMS with Astro or Next.js](/_vercel/image?url=_astro%2Fwhen-not-to-use-api-based-headless-cms.CckSL2CJ.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/when-not-to-use-headless-cms) [Headless,](/categories/headless)[CMS](/categories/cms) #### [When Not to Use an API-Based Headless CMS with Astro or Next.js](/blog/when-not-to-use-headless-cms) - Farhad - May 11, 2026 [![Git-Based vs. API-First Headless CMS: The Ultimate Comparison ](/_vercel/image?url=_astro%2Fgit-based-cms-vs-api-first-cms.DupST9ld.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/git-based-vs-api-based) [CMS,](/categories/cms)[API First,](/categories/api-first)[Git Based](/categories/git-based) #### [Git-Based vs. API-First Headless CMS: The Ultimate Comparison](/blog/git-based-vs-api-based) - Redwan - February 23, 2026 [![Should you migrate from WordPress to a Static Site Generator in 2026?](/_vercel/image?url=_astro%2Fwordpress-static-migration.DZa0t0dv.webp&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/migrating-wordpress-static-site) [Static Site,](/categories/static-site)[CMS](/categories/cms) #### [Should you migrate from WordPress to a Static Site Generator in 2026?](/blog/migrating-wordpress-static-site) - Redwan - January 04, 2026 [![Choosing the Right CMS Tool for Your Static Site](/_vercel/image?url=_astro%2Fheadless-cms-git-based-api-first.CJB43JNU.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/headless-cms-tool-for-static-site) [CMS](/categories/cms) #### [Choosing the Right CMS Tool for Your Static Site](/blog/headless-cms-tool-for-static-site) - Redwan - November 18, 2025 --- ## Comparison URL: https://sitepins.com/categories/comparison Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Comparison ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![EmDash vs Sitepins: Best Headless CMS for Astro](/_vercel/image?url=_astro%2Femdash-cms-vs-sitepins-cms.Djf6zKrT.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/emdash-vs-sitepins-headless-cms-for-astro) [Astro,](/categories/astro)[Comparison](/categories/comparison) #### [EmDash vs Sitepins: Best Headless CMS for Astro](/blog/emdash-vs-sitepins-headless-cms-for-astro) - Farhad - April 05, 2026 --- ## Git based URL: https://sitepins.com/categories/git-based Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Git based ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/_vercel/image?url=_astro%2Fdecapcms-alternatives.CELW-JIt.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/decapcms-alternatives) [CMS,](/categories/cms)[Git based](/categories/git-based) #### [6 Best Decap CMS (formerly Netlify CMS) Alternatives in 2026](/blog/decapcms-alternatives) - Farhad - June 10, 2026 [![Git-Based vs. API-First Headless CMS: The Ultimate Comparison ](/_vercel/image?url=_astro%2Fgit-based-cms-vs-api-first-cms.DupST9ld.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/git-based-vs-api-based) [CMS,](/categories/cms)[API First,](/categories/api-first)[Git Based](/categories/git-based) #### [Git-Based vs. API-First Headless CMS: The Ultimate Comparison](/blog/git-based-vs-api-based) - Redwan - February 23, 2026 --- ## Headless URL: https://sitepins.com/categories/headless Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Headless ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![7 Benefits of Headless CMS for Modern Web Development in 2026](/_vercel/image?url=_astro%2Fbenefits-headless-cms.DQhKO-b6.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/benefits-headless-cms) [Headless,](/categories/headless)[CMS](/categories/cms) #### [7 Benefits of Headless CMS for Modern Web Development in 2026](/blog/benefits-headless-cms) - Redwan - May 19, 2026 [![When Not to Use an API-Based Headless CMS with Astro or Next.js](/_vercel/image?url=_astro%2Fwhen-not-to-use-api-based-headless-cms.CckSL2CJ.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/when-not-to-use-headless-cms) [Headless,](/categories/headless)[CMS](/categories/cms) #### [When Not to Use an API-Based Headless CMS with Astro or Next.js](/blog/when-not-to-use-headless-cms) - Farhad - May 11, 2026 --- ## I18n URL: https://sitepins.com/categories/i18n Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # I18n ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Sitepins Now Speaks Your Language: Native i18n Support Is Here](/_vercel/image?url=_astro%2Fsitepins-i18n-support.BhlgOUOm.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/sitepins-i18n-launch) [Announcement,](/categories/announcement)[I18n](/categories/i18n) #### [Sitepins Now Speaks Your Language: Native i18n Support Is Here](/blog/sitepins-i18n-launch) - Farhad - June 03, 2026 --- ## Others URL: https://sitepins.com/categories/others Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Others ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Sitepins CMS is now open source](/_vercel/image?url=_astro%2Fsitepins-open-source-git-based-cms.DJaziaAv.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/sitepins-cms-is-now-open-source) [Others](/categories/others) #### [Sitepins CMS is now open source](/blog/sitepins-cms-is-now-open-source) - Farhad - July 28, 2026 --- ## Seo URL: https://sitepins.com/categories/seo Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Seo ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![CMS for SEO in 2026: Architecture, Speed & What to Look For](/_vercel/image?url=_astro%2Fcms-for-seo.BBfOnhiy.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/best-cms-for-seo-in-2026) [SEO](/categories/seo) #### [CMS for SEO in 2026: Architecture, Speed & What to Look For](/blog/best-cms-for-seo-in-2026) - Redwan - March 16, 2026 --- ## Static site URL: https://sitepins.com/categories/static-site Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Static site ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![Should you migrate from WordPress to a Static Site Generator in 2026?](/_vercel/image?url=_astro%2Fwordpress-static-migration.DZa0t0dv.webp&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/migrating-wordpress-static-site) [Static Site,](/categories/static-site)[CMS](/categories/cms) #### [Should you migrate from WordPress to a Static Site Generator in 2026?](/blog/migrating-wordpress-static-site) - Redwan - January 04, 2026 --- ## Web development URL: https://sitepins.com/categories/web-development Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Category # Web development ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [![6 Signs It's Time to Leave WordPress (And What to Use Instead)](/_vercel/image?url=_astro%2Fwordpress-alternatives.BFPmRCaZ.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY)](/blog/wordpress-alternatives) [CMS,](/categories/cms)[Web Development](/categories/web-development) #### [6 Signs It's Time to Leave WordPress (And What to Use Instead)](/blog/wordpress-alternatives) - Farhad - July 12, 2026 --- ## Choose The Right CMS for Your Project URL: https://sitepins.com/compare Compare Sitepins vs other headless CMS platforms. Find the best headless CMS for your project. Compare Center # Choose The Right CMS for Your Project Compare Sitepins vs other headless CMS platforms and find the best headless CMS for your project. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) First ToolSitepins CloudCannon Decap CMS Keystatic TinaCMS Sveltia CMS Sanity (Coming Soon)Contentful (Coming Soon)Storyblok (Coming Soon)Strapi (Coming Soon) VS Second ToolSitepins CloudCannon Decap CMS Keystatic TinaCMS Sveltia CMS Sanity (Coming Soon)Contentful (Coming Soon)Storyblok (Coming Soon)Strapi (Coming Soon) Compare ### Headless CMS Comparison Explore in-depth comparisons of leading headless CMS platforms. Discover detailed analysis of features, performance, developer experience, and scalability to help you choose the perfect stack for your project. [ ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Decap CMS vs CloudCannon Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/decapcms-vs-cloudcannon)[ ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Decap CMS vs Keystatic Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/decapcms-vs-keystatic)[ ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Decap CMS vs TinaCMS Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/decapcms-vs-tinacms)[ ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Keystatic vs CloudCannon Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/keystatic-vs-cloudcannon)[ ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sitepins vs CloudCannon Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sitepins-vs-cloudcannon)[ ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sitepins vs Decap CMS Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sitepins-vs-decapcms)[ ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sitepins vs Keystatic Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sitepins-vs-keystatic)[ ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sitepins vs Sveltia CMS Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sitepins-vs-sveltiacms)[ ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sitepins vs TinaCMS Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sitepins-vs-tinacms)[ ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sveltia CMS vs CloudCannon Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sveltiacms-vs-cloudcannon)[ ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sveltia CMS vs Decap CMS Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sveltiacms-vs-decapcms)[ ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sveltia CMS vs Keystatic Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sveltiacms-vs-keystatic)[ ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### Sveltia CMS vs TinaCMS Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/sveltiacms-vs-tinacms)[ ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### TinaCMS vs CloudCannon Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/tinacms-vs-cloudcannon)[ ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) #### TinaCMS vs Keystatic Detailed side-by-side comparison of features, editors, performance setups, and user accessibility. View Comparison ](/compare/tinacms-vs-keystatic) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Decap CMS vs CloudCannon URL: https://sitepins.com/compare/decapcms-vs-cloudcannon Compare Decap CMS and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Decap CMS vs CloudCannon Compare Decap CMS and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Decap CMS Git-Based CMS Decap CMS (formerly Netlify CMS) is a free, open-source, Git-based CMS independently maintained in the EU. It acts as a React-based wrapper around the Git workflow, storing content directly in your repository alongside your code. Originally created by Netlify and rebranded in February 2023, Decap CMS is designed for developers and content editors working with static site generators. [Get Started with Decap CMS](https://decapcms.org) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## CloudCannon Git-Based CMS CloudCannon is a Git-based CMS platform built for agencies and development teams managing client websites at scale. It offers a great visual editing experience and deep SSG integration, but requires developer configuration before editors can get started. CloudCannon is best suited for teams with dedicated developers who need a robust, enterprise-grade content workflow. [Visit CloudCannon](https://cloudcannon.com) Feature ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Decap CMS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) CloudCannon ## Overview Feature Decap CMS CloudCannon **CMS type** Git-Based (open-source, MIT-licensed) Git-Based (commercial, agency-focused) **SSG support** Hugo, Next.js, Gatsby, Jekyll, 11ty, Astro, Remix, SvelteKit + any SSG that stores content in Git Jekyll, Hugo, Eleventy (11ty), Astro, Next.js, SvelteKit, Gatsby, MkDocs **Pricing entry point** Free forever (core CMS). Decap Turbo paid extension starts at $37/mo (Starter) or $112/mo (Team). $55/mo (monthly) or $49/mo (annual). No lifetime option. **Free plan** ✅ Yes — Core CMS is free forever, no user or project limits. ❌ No — No free plan. 21-day trial only. **Free trial (without credit card)** ✅ Not needed — the core CMS is permanently free. ⚠️ Yes but — 21 days, credit card required at the end of the trial. **Content security** ✅ Yes — Highly secured. No database; content stored as static files in your own Git repository. ✅ Yes — Highly secured. No database to hack since files are stored in your Git repo. **Native language support** ⚠️ Yes but — Admin UI defaults to English. Other locales must be manually registered via the decap-cms-locales package. No built-in switcher. ❌ No — No native support. Content translation is handled via third-party tools (e.g. Rosey). **Mobile friendly** ❌ No — Not natively optimized for mobile. A community CSS workaround exists. ❌ No — No dedicated mobile-optimized editing experience. ## Setup & Configuration Feature Decap CMS CloudCannon **Non-technical setup** ❌ No — A developer must add index.html and config.yml to the project and configure authentication before the CMS is usable. ❌ No — Developer-led setup required. Needs a cloudcannon.config.yml file to configure inputs and structures. **Starter templates** ⚠️ Yes but — Official starters exist for Hugo, Next.js, Gatsby, and Jekyll. No large curated template library. ❌ No — Only an Astro starter with prebuilt components. Fewer SSG-specific options overall. **Edit schema modifier** ❌ No — Schema is defined entirely in a YAML config.yml file, edited outside the CMS. No visual schema editor. ⚠️ Yes but — Via the cloudcannon.config file, editable in-app through Configuration Mode. No visual schema editor. ## Editing Experience Feature Decap CMS CloudCannon **Editor** Rich text (Plate-based, replaces deprecated markdown widget) + Markdown + Code. 16 built-in widgets and custom widgets. WYSIWYG Visual Editor — true on-page editing. **Live preview system** ⚠️ Yes but — Customizable React-based preview templates. Requires developer setup to match the site’s frontend. ✅ Yes — Real-time in-page preview rendered inside an iFrame. Changes are visible immediately without a full rebuild. **AI assistant integration** ❌ No — No built-in AI assistant or content generation tool in either the free CMS or Decap Turbo. ⚠️ Yes but — “AI-ready infrastructure” designed for external AI agents, not an in-editor writing assistant. **Collaborative editing** ❌ No — No simultaneous editing. Decap Turbo Team adds a presence indicator only, not concurrent editing. ⚠️ Yes but — Only one user edits a file at a time; others can view live in read-only mode. **iFrame embed preview** ❌ No — Not documented or available out of the box. ✅ Yes — iFrames are used natively in the Visual Editor for live page previews. **Shortcode support** ✅ Yes — Custom editor components and widgets serve as shortcodes, configured by developers. ✅ Yes — Shortcodes can be mapped to visual editing components via configuration. **SEO tools** ❌ No — Only slug and file path config. No built-in SEO analysis, SERP preview, or scoring tools. ⚠️ Yes but — Built-in SEO optimization tools. No SERP preview. **Dark mode** ❌ No — No native dark mode. A community-contributed CSS override exists but isn’t official. ✅ Yes — Light and dark mode available, follows browser default. ## Non-Technical User Experience Feature Decap CMS CloudCannon **Designed for non-technicals** ⚠️ Yes but — Editors can use it once set up, but setup, schema changes, and auth configuration always require a developer. ⚠️ Yes but — Requires a developer for initial setup and configuration before editors can use it. **Version rollback** ⚠️ Yes but — Full history via Git. No dedicated version rollback UI inside the CMS. ⚠️ Yes but — Requires technical knowledge or developer access to execute. **Initial setup by non-dev** ❌ No — A developer must configure config.yml and the authentication backend first. ❌ No — A developer must configure the CMS and instrument templates before editors can use it. ## Media Management Feature Decap CMS CloudCannon **Media management** ⚠️ Yes but — Built-in library supports upload, view, and delete via drag-and-drop. External providers (Cloudinary, Uploadcare) via plugins. No file renaming. ✅ Yes — Drag-and-drop media library. Integrates with DAMs (Amazon S3, Cloudinary, Google Cloud Storage) and Git LFS for large-scale asset management. **External image URL support** ⚠️ Yes but — Handled via Cloudinary and Uploadcare plugins. No direct inline external URL support. ⚠️ Yes but — Handled via DAM integrations. No direct inline external URL support. ## Collaboration & Teams Feature Decap CMS CloudCannon **User access** ⚠️ Yes but — Git Gateway (via Netlify Identity) allows non-Git login. On other hosts, a developer must configure external OAuth. ✅ Yes — Editors can be invited via email without needing a personal Git account. **Custom roles** ⚠️ Yes but — A Decap Turbo feature, available on the Team plan ($37/mo) and above. The free core CMS has no centralized role management. ✅ Yes — Default permissions on the Standard plan. Custom Permission Groups available on Team and Enterprise. **Organization management** ⚠️ Yes but — A Decap Turbo feature. The free CMS is per-site with no multi-project dashboard. ✅ Yes — Organization-level management supported on all plans. **Branch workflows** ⚠️ Yes but — Editorial Workflow (draft/review/publish via Git branches) is included in the free CMS. PRs are created and merged in the Git provider itself. ⚠️ Yes but — Advanced branching workflows are only available on the Team and Enterprise plans. ## Git & Deployment Feature Decap CMS CloudCannon **Git providers** GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, and Git Gateway (Netlify) — the broadest provider support of the two. GitHub, GitLab, Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source. ✅ No — All content stored as standard files (Markdown, JSON, YAML) in your own Git repository. **Deployment** Content commits trigger builds on any connected CI/CD platform — Netlify, Vercel, GitHub Pages, Cloudflare Pages, and more. Pushes to your Git repo, triggering builds on external hosts (Vercel, Netlify, Cloudflare Pages). Also offers built-in hosting on a global Cloudflare CDN. ## Accessibilities Feature Decap CMS CloudCannon **Global search** ⚠️ Yes but — Search by title, slug, and configured summary fields. Can exhaust API rate limits on large repositories; can be disabled. ❌ No — No dedicated global search across CMS content. **Edit configs as code** ✅ Yes — Configuration is done entirely via config.yml, edited outside the CMS. ✅ Yes — Configuration Mode allows editing the cloudcannon.config file directly within the app. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature. ❌ No — Not a supported feature. Worth Knowing ### There's a third option: Sitepins Decap CMS is free but developer-led from setup to schema changes, while CloudCannon gets you a polished visual editor at $55/mo but no free plan. Sitepins sits in between: connect your repo and start editing in minutes with zero config, get a visual editor, AI writing assistant, and real-time collaboration, and stay on a free forever plan or a $199 lifetime deal. Sitepins is open source too (AGPL-3.0, on GitHub), so you can self-host it or contribute. [See Sitepins vs Decap CMS →](/compare/sitepins-vs-decapcms)[See Sitepins vs CloudCannon →](/compare/sitepins-vs-cloudcannon) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Decap CMS if: - You want a truly free, self-hosted, open-source CMS with no required subscription - You need the widest Git provider support: GitHub, GitLab, Gitea, Bitbucket, or Azure DevOps - Your team is comfortable with YAML config and doesn't need a true WYSIWYG on-page editor - You want maximum extensibility through community plugins and custom widgets - Budget matters more than a polished, agency-grade workflow ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose CloudCannon if: - You need a true on-page WYSIWYG visual editor for marketing or client-facing sites - You're managing multiple client sites and need enterprise-grade permissions and org management out of the box - You want built-in DAM integrations (S3, Cloudinary, Google Cloud Storage) and Git LFS for large media libraries - Your team uses Bitbucket alongside GitHub or GitLab - You'd rather pay for a polished, supported product than assemble one from open-source parts Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Decap CMS vs Keystatic URL: https://sitepins.com/compare/decapcms-vs-keystatic Compare Decap CMS and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Decap CMS vs Keystatic Compare Decap CMS and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Decap CMS Git-Based CMS Decap CMS (formerly Netlify CMS) is a free, open-source, Git-based CMS independently maintained in the EU. It acts as a React-based wrapper around the Git workflow, storing content directly in your repository alongside your code. Originally created by Netlify and rebranded in February 2023, Decap CMS is designed for developers and content editors working with static site generators. [Get Started with Decap CMS](https://decapcms.org) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Keystatic Git-Based CMS Keystatic is a free, open-source, Git-based CMS built by Thinkmill. It stores content as Markdown, Markdoc, MDX, JSON, or YAML files directly in your Git repository. The admin UI is bundled inside your application and reads from and writes to those files with no separate CMS server or database. Keystatic is code-first and TypeScript-native. [Visit Keystatic](https://keystatic.com) Feature ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Decap CMS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Keystatic ## Overview Feature Decap CMS Keystatic **CMS type** Git-Based (open-source, MIT-licensed) Git-Based (open-source, MIT-licensed) **SSG support** Hugo, Next.js, Gatsby, Jekyll, 11ty, Astro, Remix, SvelteKit + any SSG that stores content in Git Astro, Next.js, Remix (first-party integrations). SvelteKit via community setup. Hugo, Jekyll, and 11ty not officially supported. **Pricing entry point** Free forever (core CMS). Decap Turbo paid extension starts at $37/mo (Starter) or $112/mo (Team). Free forever (core CMS). Keystatic Cloud Pro starts at $10/mo per team (3 users included, $5/mo per additional user). **Free plan** ✅ Yes — Core CMS is free forever, no user or project limits. ✅ Yes — Core CMS is free forever with no cap. Keystatic Cloud Free allows up to 3 users per team. **Free trial (without credit card)** ✅ Not needed — the core CMS is permanently free. ✅ Not needed — the core CMS is permanently free. Keystatic Cloud Free gives full access for up to 3 users. **Content security** ✅ Yes — Highly secured. No database; content stored as static files in your own Git repository. ✅ Yes — Highly secured. No database, no CMS server. Content stored as static files in your own Git repository. **Native language support** ⚠️ Yes but — Admin UI defaults to English. Other locales must be manually registered via the decap-cms-locales package. No built-in switcher. ❌ No — Admin UI is English only. No native language switcher, and i18n for content requires manual workarounds. **Mobile friendly** ❌ No — Not natively optimized for mobile. A community CSS workaround exists. ⚠️ Yes but — Mobile-first editing is listed as a feature, but multiple user reports note the interface isn’t fully optimized and can be complex on smaller screens. ## Setup & Configuration Feature Decap CMS Keystatic **Non-technical setup** ❌ No — A developer must add index.html and config.yml to the project and configure authentication before the CMS is usable. ❌ No — A developer must install the package, create a keystatic.config.ts file, and configure storage mode and authentication first. **Starter templates** ⚠️ Yes but — Official starters exist for Hugo, Next.js, Gatsby, and Jekyll. No large curated template library. ⚠️ Yes but — Official CLI starters exist for Astro and Next.js. A small number of community starters, no large library. **Edit schema modifier** ❌ No — Schema is defined entirely in a YAML config.yml file. No visual schema editor. ❌ No — Schema is defined entirely in code via keystatic.config.ts (TypeScript). No visual schema editor. ## Editing Experience Feature Decap CMS Keystatic **Editor** Rich text (Plate-based, replaces deprecated markdown widget) + Markdown + Code. 16 built-in widgets and custom widgets. Rich text (WYSIWYG) + Markdoc + MDX + JSON/YAML. Auto-generated from your TypeScript schema. **Live preview system** ⚠️ Yes but — Customizable React-based preview templates. Requires developer setup. ⚠️ Yes but — Real-time previews via Next.js Draft Mode integration. Requires developer setup and is tied to the Next.js integration. **AI assistant integration** ❌ No — No built-in AI assistant in either the free CMS or Decap Turbo. ❌ No — No built-in AI assistant or content generation tool in the core CMS or Keystatic Cloud. **Collaborative editing** ❌ No — No simultaneous editing. Decap Turbo Team adds a presence indicator only, not concurrent editing. ⚠️ Yes but — Multi-player editing is an experimental feature on Keystatic Cloud Pro. The core CMS has none, and simultaneous saves to the same file create unresolved Git merge conflicts. **iFrame embed preview** ❌ No — Not documented or available out of the box. ❌ No — Not a built-in or documented feature. **Shortcode support** ✅ Yes — Custom editor components and widgets serve as shortcodes, configured by developers. ✅ Yes — Content components (custom blocks) are supported within Markdoc and MDX fields. **SEO tools** ⚠️ Yes but — Slug and file path config only. No built-in SEO analysis, SERP preview, or content scoring. ⚠️ Yes but — Slug generation via the slug field type. No built-in SEO analysis, SERP preview, or scoring. **Dark mode** ❌ No — No native dark mode. A community-contributed CSS override exists but isn’t official. ❌ No — No dark mode documented for the Keystatic admin UI. ## Non-Technical User Experience Feature Decap CMS Keystatic **Designed for non-technicals** ⚠️ Yes but — Editors can use it once set up, but setup, schema changes, and auth configuration always require a developer. ⚠️ Yes but — Editors can use the visual admin UI once set up, but Keystatic is developer-first: all schema config and setup require a developer. **Version rollback** ⚠️ Yes but — Full history via Git. No dedicated version rollback UI inside the CMS. ⚠️ Yes but — Every save is a Git commit, giving full history. No dedicated non-technical rollback UI. **Initial setup by non-dev** ❌ No — A developer must configure config.yml and the authentication backend first. ❌ No — A developer must install the package, define the TypeScript schema, and configure storage and authentication first. ## Media Management Feature Decap CMS Keystatic **Media management** ⚠️ Yes but — Built-in library supports upload, view, and delete via drag-and-drop. External providers (Cloudinary, Uploadcare) via plugins. No file renaming. ⚠️ Yes but — Images upload and store in the Git repo via the image field. Keystatic Cloud Pro adds managed Cloud Images (storage, optimization, delivery). No folder organization or renaming in the CMS UI. **External image URL support** ⚠️ Yes but — Handled via Cloudinary and Uploadcare plugins. No direct inline external URL support. ⚠️ Yes but — External URLs can be referenced in content fields. Keystatic Cloud Images serves via Cloudflare CDN with transform params; no native S3/Cloudinary plugin outside Cloud Images. ## Collaboration & Teams Feature Decap CMS Keystatic **User access** ⚠️ Yes but — Git Gateway (via Netlify Identity) allows non-Git login. On other hosts, a developer must configure external OAuth. ⚠️ Yes but — Keystatic Cloud allows login without a GitHub account. Without Cloud, editors must authenticate directly via GitHub OAuth. **Custom roles** ⚠️ Yes but — A Decap Turbo feature, available on the Team plan ($37/mo) and above. The free core CMS has no centralized role management. ❌ No — No role-based access control at all, in the core CMS or Keystatic Cloud Free/Pro. All team members can access all projects in a team. **Organization management** ⚠️ Yes but — A Decap Turbo feature. The free CMS is per-site with no multi-project dashboard. ⚠️ Yes but — Keystatic Cloud organizes projects into teams, each connected to a repository. Requires the paid Cloud tier for anything beyond a single project. **Branch workflows** ⚠️ Yes but — Editorial Workflow (draft/review/publish via Git branches) is in the free CMS. PRs are created and merged in the Git provider itself. ⚠️ Yes but — Branch creation and switching happen inside the admin UI via GitHub mode. No built-in PR creation, review, or merge — that’s done directly in GitHub. ## Git & Deployment Feature Decap CMS Keystatic **Git providers** GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, and Git Gateway (Netlify) — the broadest provider support of the two. GitHub only via Keystatic Cloud. GitHub and local filesystem in self-hosted mode. No GitLab or Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source. ✅ No — No vendor lock-in. Content is stored as static files (Markdown, YAML, JSON) in your own GitHub repository. Keystatic Cloud is optional. **Deployment** Content commits trigger builds on any connected CI/CD platform — Netlify, Vercel, GitHub Pages, Cloudflare Pages, and more. Works with any Git-connected CI/CD platform. No built-in one-click deployment. ## Accessibilities Feature Decap CMS Keystatic **Global search** ⚠️ Yes but — Search by title, slug, and configured summary fields. Can exhaust API rate limits on large repositories; can be disabled. ❌ No — Only a per-collection filter by title or slug. No global cross-collection search or keyboard-shortcut search. **Edit configs as code** ✅ Yes — Configuration is done entirely via config.yml. ✅ Yes — All configuration is done in code via keystatic.config.ts. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature. ❌ No — Not a built-in or documented feature. Worth Knowing ### There's a third option: Sitepins Both Decap CMS and Keystatic are developer-first: someone has to write a config file and wire up authentication before an editor can log in, and neither has role-based access control worth relying on. Sitepins connects to your repo with zero config, ships a visual editor, AI writing assistant, real-time collaboration, and custom roles out of the box — all on a free forever plan. It is open source as well (AGPL-3.0, on GitHub), so self-hosting stays an option. [See Sitepins vs Decap CMS →](/compare/sitepins-vs-decapcms)[See Sitepins vs Keystatic →](/compare/sitepins-vs-keystatic) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Decap CMS if: - You need broad Git provider support beyond GitHub — GitLab, Bitbucket, Gitea, or Azure DevOps - You want role-based access control available as a paid add-on, even a basic one - Your team needs Hugo, Jekyll, or 11ty support without a community workaround - You want a built-in (if rate-limited) content search across the whole CMS - You prefer YAML-based configuration over writing TypeScript ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Keystatic if: - Your team is comfortable defining content schemas in TypeScript and wants type-safe content - You're building with Astro, Next.js, or Remix and want a first-party, deeply integrated CMS - You want a cheaper managed-cloud entry point ($10/mo for a 3-user team) if you outgrow self-hosting - You want images optimized and CDN-delivered without configuring a third-party DAM - Content should live entirely inside your codebase with zero separate CMS server Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Decap CMS vs TinaCMS URL: https://sitepins.com/compare/decapcms-vs-tinacms Compare Decap CMS and TinaCMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Decap CMS vs TinaCMS Compare Decap CMS and TinaCMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Decap CMS Git-Based CMS Decap CMS (formerly Netlify CMS) is a free, open-source, Git-based CMS independently maintained in the EU. It acts as a React-based wrapper around the Git workflow, storing content directly in your repository alongside your code. Originally created by Netlify and rebranded in February 2023, Decap CMS is designed for developers and content editors working with static site generators. [Get Started with Decap CMS](https://decapcms.org) VS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## TinaCMS Git-Based CMS TinaCMS is an open-source, Git-backed headless CMS originally developed by Forestry.io and acquired by SSW (Superior Software for Windows). It provides a visual editing interface on top of Markdown, MDX, and JSON files stored in Git, giving developers full control over the content model while abstracting Git complexity for content editors. [Visit TinaCMS](https://tina.io) Feature ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Decap CMS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) TinaCMS ## Overview Feature Decap CMS TinaCMS **CMS type** Git-Based (open-source, MIT-licensed) Git-Based (open-source, TinaCloud optional) **SSG support** Hugo, Next.js, Gatsby, Jekyll, 11ty, Astro, Remix, SvelteKit + any SSG that stores content in Git Astro, Next.js, Hugo, Jekyll, Gatsby, Remix, 11ty, SvelteKit + other frameworks **Pricing entry point** Free forever (core CMS). Decap Turbo paid extension starts at $37/mo (Starter) or $112/mo (Team). $24/mo (monthly) or $290/yr (annual) — Team plan. No lifetime option. **Free plan** ✅ Yes — Core CMS is free forever and fully open source. No user or project limits. ⚠️ Yes but — Free forever, limited to 2 users and 1 project. **Free trial (without credit card)** ✅ Not needed — the core CMS is permanently free. Decap Turbo early access includes a free trial on launch. ❌ No — No time-limited trial. The permanent free plan (2 users, 1 project) serves this role. **Content security** ✅ Yes — Highly secured. No database; all content is stored as static files in your own Git repository. ✅ Yes — Highly secured. No database; files stored in Git. SOC 2 framework alignment, AWS-hosted infrastructure, encryption at rest and in transit. **Native language support** ⚠️ Yes but — Admin UI defaults to English. Other locales must be manually registered by a developer using the decap-cms-locales package. No out-of-the-box switcher. ❌ No — English only for the CMS interface. **Mobile friendly** ❌ No — Not natively optimized for mobile. A community CSS workaround exists, but there’s no official mobile support. ✅ Yes — Mobile and tablet optimized as of TinaCMS v2.0 (iOS and Android supported). ## Setup & Configuration Feature Decap CMS TinaCMS **Non-technical setup** ❌ No — A developer must add index.html and config.yml to the project and configure authentication before the CMS is usable. ❌ No — A developer must configure the /tina folder and schema before editors can use the CMS. **Starter templates** ⚠️ Yes but — Official starters exist for Hugo, Next.js, Gatsby, and Jekyll. No large curated template library. ⚠️ Yes but — A small set of official CLI starters (Next.js, Astro). Some community starters exist, no large library. **Edit schema modifier** ❌ No — Schema is defined entirely in a YAML config.yml file. No visual schema editor inside the CMS. ❌ No — Schema is defined in code via TypeScript/JavaScript config files. No visual in-app schema editor. ## Editing Experience Feature Decap CMS TinaCMS **Editor** Rich text (Plate-based, replaces deprecated markdown widget) + Markdown + Code. 16 built-in widgets and custom widgets. Visual (contextual/inline) editor + Rich Text (Plate-based) + Markdown + Code. **Live preview system** ⚠️ Yes but — Customizable React-based preview templates. Requires developer setup to match the site’s frontend. ⚠️ Yes but — Contextual, on-page visual editing with real-time inline preview. Requires developer setup to wire to the frontend. **AI assistant integration** ❌ No — No built-in AI assistant or content generation tool in either the free CMS or Decap Turbo. ❌ No — Listed as “Coming Soon” on paid plans. TinaGPT is a support chatbot only, not an in-editor content generation tool. **Collaborative editing** ❌ No — No simultaneous multi-user editing. Decap Turbo Team adds a presence indicator (who’s active), not concurrent editing. ❌ No — TinaCMS is single-user per document. Simultaneous multi-user editing is not supported. **iFrame embed preview** ❌ No — Not documented or available out of the box. ⚠️ Yes but — Not native. iFrame/embed support depends on custom MDX component configuration by a developer. **Shortcode support** ✅ Yes — Custom editor components and widgets serve as shortcodes, configured by developers in the CMS setup. ✅ Yes — Custom Markdown shortcodes via the rich-text field’s custom MDX syntax configuration. **SEO tools** ⚠️ Yes but — Slug and file path config only. No built-in SEO analysis, SERP preview, or content scoring. ⚠️ Yes but — SEO fields are developer-configurable. No built-in SEO analysis, SERP preview, or content scoring. **Dark mode** ❌ No — No native dark mode. A community-contributed CSS override exists but isn’t an official feature. ❌ No — Not confirmed as a switchable CMS setting (dark mode exists in the separate TinaDocs product only). ## Non-Technical User Experience Feature Decap CMS TinaCMS **Designed for non-technicals** ⚠️ Yes but — Editors can use it once set up, but setup, schema changes, and auth configuration always require a developer. ⚠️ Yes but — Editors can use it once set up, but initial configuration and schema changes always require a developer. **Version rollback** ⚠️ Yes but — Full history via Git. No dedicated version rollback UI inside the CMS. ⚠️ Yes but — Content is Git-backed so rollback is possible. No dedicated non-technical rollback UI. **Initial setup by non-dev** ❌ No — A developer must configure config.yml and the authentication backend before the CMS is usable. ❌ No — A developer must install the package, configure the schema, and deploy the admin route first. ## Media Management Feature Decap CMS TinaCMS **Media management** ⚠️ Yes but — Built-in library supports upload, view, and delete via drag-and-drop. External providers (Cloudinary, Uploadcare) via plugins. No file renaming. ⚠️ Yes but — Upload, view, and delete via the Media Manager. External providers (Cloudinary, S3, Digital Ocean Spaces). No file renaming. **External image URL support** ⚠️ Yes but — Handled via Cloudinary and Uploadcare plugins. No direct inline external URL support. ⚠️ Yes but — Handled via external media provider plugins. No direct inline external URL support. ## Collaboration & Teams Feature Decap CMS TinaCMS **User access** ⚠️ Yes but — Git Gateway (via Netlify Identity) allows non-Git login. On non-Netlify hosts, a developer must configure an external OAuth client. ✅ Yes — Invite via TinaCloud. Editors need only a TinaCloud account, no GitHub account required. **Custom roles** ⚠️ Yes but — A Decap Turbo feature, available on the Team plan ($37/mo) and above. The free core CMS has no centralized role management. ⚠️ Yes but — Two roles (Admin, Editor) on Free, Team, and Team Plus. Three roles on Business (beta). Custom roles on Enterprise only. **Organization management** ⚠️ Yes but — A Decap Turbo feature. The free CMS is per-site with no centralized multi-project dashboard. ✅ Yes — Organizations are supported in TinaCloud to manage multiple projects. **Branch workflows** ⚠️ Yes but — Editorial Workflow (draft/review/publish via Git branches) is in the free CMS. PRs are created and merged in the Git provider itself, not inside Decap. ⚠️ Yes but — Branch creation, protected branches, PR review, and preview links — available on the Team Plus plan and above only. ## Git & Deployment Feature Decap CMS TinaCMS **Git providers** GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, and Git Gateway (Netlify) — the broadest provider support of the two. GitHub only via TinaCloud (including GitHub Enterprise on the Enterprise plan). GitLab not supported natively. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source. ✅ No — No vendor lock-in. Content stored as Markdown/MDX/JSON in your own GitHub repository. TinaCloud is optional; self-hosting is available. **Deployment** Content commits trigger builds on any connected CI/CD platform — Netlify, Vercel, GitHub Pages, Cloudflare Pages, and more. Pushes content changes to your Git repo, triggering builds on Vercel, Netlify, GitHub Pages, Cloudflare Pages, Cloudflare Workers, and Alibaba Cloud. ## Accessibilities Feature Decap CMS TinaCMS **Global search** ⚠️ Yes but — Search by title, slug, and configured summary fields. Can exhaust API rate limits on large repositories; can be disabled. ⚠️ Yes but — Built-in via TinaCloud with indexer token configuration. Not available in self-hosted mode. **Edit configs as code** ✅ Yes — Configuration is done entirely via config.yml. Editing config as code is the primary and only method. ✅ Yes — All configuration is done in code via /tina/config.ts. Direct editing of config files is the primary method. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature in Decap CMS. ✅ Yes — Mermaid diagram rendering is supported in the rich-text editor using the Mermaid npm package. Worth Knowing ### There's a third option: Sitepins Both Decap CMS and TinaCMS need a developer to install a package, write a config file, and wire up authentication before a single non-technical editor can log in. Sitepins skips all of that: connect your repository and start editing in minutes, with a visual editor, AI writing assistant, real-time multi-user collaboration, and one-click Vercel deploys included on a free forever plan. Sitepins is open source too (AGPL-3.0, on GitHub), so you can self-host it or contribute. [See Sitepins vs Decap CMS →](/compare/sitepins-vs-decapcms)[See Sitepins vs TinaCMS →](/compare/sitepins-vs-tinacms) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Decap CMS if: - You want a completely free, self-hosted CMS with zero recurring cost, forever - Your team needs the broadest Git provider support: GitHub, GitLab, Bitbucket, Gitea, or Azure DevOps - You want maximum extensibility through custom widgets, plugins, and open-source contributions - You're already in the Netlify ecosystem and want Git Gateway authentication for non-technical editors - You don't need a paid cloud tier and are fine managing collaboration and roles yourself ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose TinaCMS if: - You're building with Next.js or Astro and want deep, contextual on-page visual editing - You want editors to log in without a GitHub account, via TinaCloud - You need Mermaid diagram support directly in the content editor - You want a mobile-optimized editing experience out of the box - You're fine paying for a managed cloud (SOC 2-aligned, AWS-hosted) instead of self-hosting Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Keystatic vs CloudCannon URL: https://sitepins.com/compare/keystatic-vs-cloudcannon Compare Keystatic and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Keystatic vs CloudCannon Compare Keystatic and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Keystatic Git-Based CMS Keystatic is a free, open-source, Git-based CMS built by Thinkmill. It stores content as Markdown, Markdoc, MDX, JSON, or YAML files directly in your Git repository. The admin UI is bundled inside your application and reads from and writes to those files with no separate CMS server or database. Keystatic is code-first and TypeScript-native. [Get Started with Keystatic](https://keystatic.com) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## CloudCannon Git-Based CMS CloudCannon is a Git-based CMS platform built for agencies and development teams managing client websites at scale. It offers a great visual editing experience and deep SSG integration, but requires developer configuration before editors can get started. CloudCannon is best suited for teams with dedicated developers who need a robust, enterprise-grade content workflow. [Visit CloudCannon](https://cloudcannon.com) Feature ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Keystatic ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) CloudCannon ## Overview Feature Keystatic CloudCannon **CMS type** Git-Based (open-source, MIT-licensed) Git-Based (commercial, agency-focused) **SSG support** Astro, Next.js, Remix (first-party integrations). SvelteKit via community setup. Hugo, Jekyll, and 11ty not officially supported. Jekyll, Hugo, Eleventy (11ty), Astro, Next.js, SvelteKit, Gatsby, MkDocs **Pricing entry point** Free forever (core CMS). Keystatic Cloud Pro starts at $10/mo per team (3 users included, $5/mo per additional user). $55/mo (monthly) or $49/mo (annual). No lifetime option. **Free plan** ✅ Yes — Core CMS is free forever with no cap. Keystatic Cloud Free allows up to 3 users per team. ❌ No — No free plan. 21-day trial only. **Free trial (without credit card)** ✅ Not needed — the core CMS is permanently free. ⚠️ Yes but — 21 days, credit card required at the end of the trial. **Content security** ✅ Yes — Highly secured. No database, no CMS server. Content stored as static files in your own Git repository. ✅ Yes — Highly secured. No database to hack since files are stored in your Git repo. **Native language support** ❌ No — Admin UI is English only. No native language switcher, and i18n for content requires manual workarounds. ❌ No — No native support. Content translation is handled via third-party tools (e.g. Rosey). **Mobile friendly** ⚠️ Yes but — Mobile-first editing is listed as a feature, but multiple user reports note the interface isn’t fully optimized and can be complex on smaller screens. ❌ No — No dedicated mobile-optimized editing experience. ## Setup & Configuration Feature Keystatic CloudCannon **Non-technical setup** ❌ No — A developer must install the package, create a keystatic.config.ts file, and configure storage and authentication first. ❌ No — Developer-led setup required. Needs a cloudcannon.config.yml file to configure inputs and structures. **Starter templates** ⚠️ Yes but — Official CLI starters exist for Astro and Next.js. A small number of community starters, no large library. ❌ No — Only an Astro starter with prebuilt components. Fewer SSG-specific options overall. **Edit schema modifier** ❌ No — Schema is defined entirely in code via keystatic.config.ts (TypeScript), edited outside the CMS. ⚠️ Yes but — Via the cloudcannon.config file, editable in-app through Configuration Mode. No visual schema editor. ## Editing Experience Feature Keystatic CloudCannon **Editor** Rich text (WYSIWYG) + Markdoc + MDX + JSON/YAML. Auto-generated from your TypeScript schema. WYSIWYG Visual Editor — true on-page editing. **Live preview system** ⚠️ Yes but — Real-time previews via Next.js Draft Mode integration. Requires developer setup and is tied to that specific integration. ✅ Yes — Real-time in-page preview rendered inside an iFrame. Changes are visible immediately without a full rebuild. **AI assistant integration** ❌ No — No built-in AI assistant or content generation tool in the core CMS or Keystatic Cloud. ⚠️ Yes but — “AI-ready infrastructure” designed for external AI agents, not an in-editor writing assistant. **Collaborative editing** ⚠️ Yes but — Multi-player editing is an experimental feature on Keystatic Cloud Pro. The core CMS has none, and simultaneous saves create unresolved Git merge conflicts. ⚠️ Yes but — Only one user edits a file at a time; others can view live in read-only mode, with no merge-conflict risk. **iFrame embed preview** ❌ No — Not a built-in or documented feature. ✅ Yes — iFrames are used natively in the Visual Editor for live page previews. **Shortcode support** ✅ Yes — Content components (custom blocks) are supported within Markdoc and MDX fields. ✅ Yes — Shortcodes can be mapped to visual editing components via configuration. **SEO tools** ❌ No — Only slug generation via the slug field type. No built-in SEO analysis, SERP preview, or scoring. ⚠️ Yes but — Built-in SEO optimization tools. No SERP preview. **Dark mode** ❌ No — No dark mode documented for the Keystatic admin UI. ✅ Yes — Light and dark mode available, follows browser default. ## Non-Technical User Experience Feature Keystatic CloudCannon **Designed for non-technicals** ⚠️ Yes but — Editors can use the visual admin UI once set up, but Keystatic is developer-first: all schema config and setup require a developer. ⚠️ Yes but — Requires a developer for initial setup and configuration before editors can use it. **Version rollback** ⚠️ Yes but — Every save is a Git commit, giving full history. No dedicated non-technical rollback UI. ⚠️ Yes but — Requires technical knowledge or developer access to execute. **Initial setup by non-dev** ❌ No — A developer must install the package, define the TypeScript schema, and configure storage and authentication first. ❌ No — A developer must configure the CMS and instrument templates before editors can use it. ## Media Management Feature Keystatic CloudCannon **Media management** ⚠️ Yes but — Images upload and store in the Git repo via the image field. Keystatic Cloud Pro adds managed Cloud Images. No folder organization or renaming in the CMS UI. ✅ Yes — Drag-and-drop media library. Integrates with DAMs (Amazon S3, Cloudinary, Google Cloud Storage) and Git LFS for large-scale asset management. **External image URL support** ⚠️ Yes but — External URLs can be referenced in content fields. Keystatic Cloud Images serves via Cloudflare CDN with transform params; no native S3/Cloudinary plugin outside Cloud Images. ⚠️ Yes but — Handled via DAM integrations. No direct inline external URL support. ## Collaboration & Teams Feature Keystatic CloudCannon **User access** ⚠️ Yes but — Keystatic Cloud allows login without a GitHub account. Without Cloud, editors must authenticate directly via GitHub OAuth. ✅ Yes — Editors can be invited via email without needing a personal Git account, on any plan. **Custom roles** ❌ No — No role-based access control at all, in the core CMS or Keystatic Cloud Free/Pro. All team members can access all projects in a team. ✅ Yes — Default permissions on the Standard plan. Custom Permission Groups available on Team and Enterprise. **Organization management** ⚠️ Yes but — Keystatic Cloud organizes projects into teams. Requires the paid Cloud tier for anything beyond a single project. ✅ Yes — Organization-level management supported on all plans. **Branch workflows** ⚠️ Yes but — Branch creation and switching happen inside the admin UI via GitHub mode. No built-in PR creation, review, or merge — that’s done directly in GitHub. ⚠️ Yes but — Advanced branching workflows are only available on the Team and Enterprise plans. ## Git & Deployment Feature Keystatic CloudCannon **Git providers** GitHub only via Keystatic Cloud. GitHub and local filesystem in self-hosted mode. No GitLab or Bitbucket. GitHub, GitLab, Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content is stored as static files (Markdown, YAML, JSON) in your own GitHub repository. Keystatic Cloud is optional. ✅ No — All content stored as standard files (Markdown, JSON, YAML) in your own Git repository. **Deployment** Works with any Git-connected CI/CD platform. No built-in one-click deployment. Pushes to your Git repo, triggering builds on external hosts (Vercel, Netlify, Cloudflare Pages). Also offers built-in hosting on a global Cloudflare CDN. ## Accessibilities Feature Keystatic CloudCannon **Global search** ❌ No — Only a per-collection filter by title or slug. No global cross-collection search. ❌ No — No dedicated global search across CMS content. **Edit configs as code** ✅ Yes — All configuration is done in code via keystatic.config.ts. ✅ Yes — Configuration Mode allows editing the cloudcannon.config file directly within the app. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature. ❌ No — Not a supported feature. Worth Knowing ### There's a third option: Sitepins Keystatic has no role-based access control at all, and CloudCannon charges $55/mo with no free plan. Sitepins gives every team custom roles, a visual editor, an AI writing assistant, and real-time collaboration from day one — with zero config to get started, on a free forever plan or a $199 one-time lifetime deal. Like Keystatic, Sitepins is open source (AGPL-3.0, on GitHub) and can be self-hosted. [See Sitepins vs Keystatic →](/compare/sitepins-vs-keystatic)[See Sitepins vs CloudCannon →](/compare/sitepins-vs-cloudcannon) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Keystatic if: - You want a completely free, self-hosted CMS with no required subscription - Your team is comfortable defining schemas in TypeScript and wants a type-safe Reader API - You're building specifically with Astro, Next.js, or Remix and want first-party integration depth - Content should live entirely inside your codebase with zero separate CMS server - You want a cheap managed-cloud upgrade path ($10/mo for a 3-user team) instead of an agency-priced plan ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose CloudCannon if: - You need a true on-page WYSIWYG visual editor with real-time preview, no developer wiring required - You need role-based permissions and organization management from your very first paid plan - You want built-in DAM integrations (S3, Cloudinary, Google Cloud Storage) and Git LFS for large media libraries - Your team uses GitLab or Bitbucket, not just GitHub - You're managing multiple client sites and need agency-grade workflows and dedicated support Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins vs CloudCannon URL: https://sitepins.com/compare/sitepins-vs-cloudcannon Compare Sitepins and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sitepins vs CloudCannon Compare Sitepins and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sitepins Git-Based CMS Sitepins 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 Sitepins](https://app.sitepins.com) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## CloudCannon Git-Based CMS CloudCannon is a Git-based CMS platform built for agencies and development teams managing client websites at scale. It offers a great visual editing experience and deep SSG integration, but requires developer configuration before editors can get started. CloudCannon is best suited for teams with dedicated developers who need a robust, enterprise-grade content workflow. [Visit CloudCannon](https://cloudcannon.com) Feature ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) CloudCannon ## Overview Feature Sitepins CloudCannon **CMS type** Git-Based (open source, AGPL-3.0 licensed) Git-Based **SSG support** Astro, Next.js, Hugo, 11ty, Jekyll, SvelteKit, Nuxt + more Jekyll, Hugo, Eleventy (11ty), Astro, Next.js, SvelteKit, Gatsby, MkDocs **Pricing entry point** $12/mo (monthly) or $10/mo (annual); $199 one-time lifetime $55/mo (monthly) or $49/mo (annual). No lifetime option. **Free plan** ✅ Yes — Free forever, with limitations (Hobby plan) ❌ No — No free plan. 21-day trial only. **Free trial (without credit card)** ✅ Yes — 15 days (no card required) ⚠️ No — 21 days (credit card required at end of trial) **Content Security** ✅ Yes — Highly secured. No database to hack since files are stored in your Git repo. ✅ Yes — Highly secured. No database to hack since files are stored in your Git repo. **Native language support** ✅ Yes — 12 languages supported natively (en, zh, ja, de, fr, es, pt, ru, ko, id, vi, bn) ❌ No — Content translation supported via third-party tools (e.g. Rosey). **Mobile friendly** ✅ Yes — Fully mobile and tablet optimized ❌ No — No dedicated mobile-optimized editing experience. ## Setup & Configuration Feature Sitepins CloudCannon **Non-technical setup** ✅ Yes — Zero configuration. Register, connect your repo and get started without any code or config. ❌ No — Developer-led setup required. Requires a `cloudcannon.config.yml` file to configure inputs and structures. **Starter templates** ✅ Yes — 100+ Astro, Hugo, and Next.js ready-made project templates to launch faster ❌ No — Only Astro starter prebuilt components. Fewer SSG-specific options overall. **Edit schema modifier** ✅ Yes — Visual schema editor within the CMS. Adjust content field types and settings directly inside the CMS. ⚠️ Yes but — Via the `cloudcannon.config` file. No visual in-app schema editor. ## Editing Experience Feature Sitepins CloudCannon **Editor** Visual editor + Markdown + Code WYSIWYG Visual Editor **Live preview system** ✅ Yes — Sandbox live preview. See how your content looks on the site before publishing. ✅ Yes — Real-time in-page preview rendered inside an iFrame. Changes are visible immediately without a full rebuild. **AI assistant integration** ✅ Yes — Bring Your Own Key (BYOK): OpenAI, Gemini, Claude, and Grok to generate or rewrite content inside the editor. ✅ Yes — AI-ready infrastructure; designed for external AI agents. **Collaborative editing** ✅ Yes — Allows multiple users to edit content simultaneously. ⚠️ Yes but — Only one user edits at a time per file; others can view live in read-only mode. **iFrame embed preview** ✅ Yes — Render embedded content like videos or charts live inside the editor. ✅ Yes — iFrames are used natively in the Visual Editor for live page previews. **Shortcode support** ✅ Yes — Manage shortcodes and custom content blocks for powerful content structuring. ✅ Yes — Shortcodes can be mapped to visual editing components via configuration. **SEO tools** ✅ Yes — Built-in tools to optimize content for search engines, content analysis, slug editing, and SERP preview. ⚠️ Yes but — Built-in SEO optimization tools. No SERP preview. **Dark mode** ✅ Yes — Supports full platform dark mode. Default is set by the browser. Switchable. ✅ Yes — Light and dark mode available, follows browser default. ## Non-Technical User Experience Feature Sitepins CloudCannon **Designed for non-technicals** ✅ Yes — Core product mission. ⚠️ Yes but — Requires a developer for initial setup and configuration. **Version rollback** ✅ Yes — Undo changes and restore a previous version without touching Git, directly within the CMS. ⚠️ Yes but — Requires technical knowledge or developer access to execute. **Initial setup by non-dev** ✅ Yes — Zero configuration. Can be set up easily without developer involvement. ❌ No — Requires a developer to configure the CMS and instrument templates before editors can use it. ## Media Management Feature Sitepins CloudCannon **Media management** ✅ Yes — Upload, organize, drag and drop, rename files and folders, replace images and delete directly from the CMS. Drag-and-drop media library. Integrates with DAMs (Amazon S3, Cloudinary, Google Cloud Storage) and Git LFS for large-scale asset management. **External image URL support** ✅ Yes — Use images hosted on external CDNs or third-party services directly in the editor. ⚠️ Yes but — Handled via DAM integrations. No direct inline external URL support. ## Collaboration & Teams Feature Sitepins CloudCannon **User access** ✅ Yes — Editors can be invited via email without needing a personal Git account ✅ Yes — Editors can be invited via email without needing a personal Git account **Custom roles** ✅ Yes — Define specific permission levels for different types of users. E.g. Owner, Admin, Editor. ✅ Yes — Default permissions on Standard plan. Custom Permission Groups available on Team plan and Enterprise. **Organization management** ✅ Yes — Manage multiple teams and projects. ✅ Yes — Organization-level management supported on all plans. **Branch workflows** ✅ Yes — Manage branches, create PRs, and merge directly from Sitepins. ⚠️ Yes but — Advanced branching workflows available on Team and Enterprise plans only. ## Git & Deployment Feature Sitepins CloudCannon **Git providers** GitHub (all plans), GitLab (Team plan) GitHub, GitLab, Bitbucket **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 — All content stored as standard files (Markdown, JSON, YAML) in your own Git repository. **Deployment** ✅ Yes — One-click Vercel deployment built-in. Pushes content changes to your Git repo, triggering builds on external hosts (Vercel, Netlify, Cloudflare Pages). Also offers built-in hosting on a global Cloudflare CDN. ## Accessibilities Feature Sitepins CloudCannon **Global search** ✅ Yes — Cmd/Ctrl+K to search for files stored anywhere in the CMS. ❌ No — No dedicated global search across CMS content. **Edit configs as code** ✅ Yes — Direct access to configuration files. ✅ Yes — Configuration Mode allows editing the `cloudcannon.config` file directly within the app. **Mermaid diagram preview** ✅ Yes — Mermaid diagrams supported in the CMS. ❌ No — Not a supported feature. Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### 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 a free plan or a one-time lifetime deal with no recurring costs - You want your CMS interface in your team's native language ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose CloudCannon if: - You have a dedicated developer to handle initial setup and configuration - You need a true on-page WYSIWYG visual editor for marketing or client-facing sites - You require advanced content scheduling and enterprise-grade permission controls - Your team uses Bitbucket and needs full Git provider flexibility - You are managing large-scale agency projects with complex editorial workflows Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins vs Decap CMS URL: https://sitepins.com/compare/sitepins-vs-decapcms Compare Sitepins and Decap CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sitepins vs Decap CMS Compare Sitepins and Decap CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sitepins Git-Based CMS Sitepins 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 Sitepins](https://app.sitepins.com) VS ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Decap CMS Git-Based CMS Decap CMS (formerly Netlify CMS) is a free, open-source, Git-based CMS independently maintained in the EU. It acts as a React-based wrapper around the Git workflow, storing content directly in your repository alongside your code. Originally created by Netlify and rebranded in February 2023, Decap CMS is designed for developers and content editors working with static site generators. [Visit Decap CMS](https://decapcms.org) Feature ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Decap CMS ## Overview Feature Sitepins Decap CMS **CMS type** Git-Based (open source, AGPL-3.0 licensed) Git-Based (open-source, MIT-licensed) **SSG support** Astro, Next.js, Hugo, 11ty, Jekyll, SvelteKit, Nuxt + more Hugo, Next.js, Gatsby, Jekyll, 11ty, Astro, Remix, SvelteKit + any SSG that stores content in Git **Pricing entry point** $12/mo (monthly) or $10/mo (annual); $199 one-time lifetime Free forever (core CMS). Decap Turbo paid extension starts at $37/mo (Starter) or $112/mo (Team). **Free plan** ✅ Yes — Free forever, with limitations (Hobby plan) ✅ Yes — Core Decap CMS is free forever and fully open source. No user or project limits on the free tier. **Free trial (without credit card)** ✅ Yes — 15 days (no card required) ✅ Yes — No trial needed. The core CMS is permanently free. Decap Turbo early access includes a free trial on launch. **Content security** ✅ Yes — Highly secured. No database to hack; files are static and stored in Git ✅ Yes — Highly secured. No database to hack; all 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 but — The admin UI defaults to English. Other languages (de, fr, es, pt, and others) must be manually registered by a developer using the decap-cms-locales package. No out-of-the-box language switcher for editors. **Mobile friendly** ✅ Yes — Fully mobile and tablet optimized ❌ No — The CMS admin interface is not natively optimized for mobile. Partial header and dropdown responsiveness was added in recent releases, but full mobile support requires a community CSS workaround. ## Setup & Configuration Feature Sitepins Decap 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 (index.html and config.yml), configure the content model, and set up authentication before the CMS is usable. **Starter templates** ✅ Yes — 100+ Astro, Hugo, and Next.js ready-made project templates to launch faster ⚠️ Yes but — Official starter templates exist for Hugo, Next.js, Gatsby, and Jekyll via the Decap docs. No large curated library, and templates require developer configuration to activate. **Edit schema modifier** ✅ Yes — Visual schema editor within the CMS. Adjust content field types and settings directly inside the CMS. ❌ No — Schema (collections, fields, widgets) is defined entirely in a YAML config file. There is no visual schema editor inside the CMS. All changes require editing config.yml directly. ## Editing Experience Feature Sitepins Decap CMS **Editor** Visual editor + Markdown + Code Rich text (Plate-based, replaces deprecated markdown widget) + Markdown + Code. Supports 16 built-in widgets and custom widgets. **Live preview system** ✅ Yes — Sandbox live preview. See how your content looks on the site before publishing. ⚠️ Yes but — Real-time preview is supported and customizable using React-based preview templates. Requires developer setup to wire the preview to match the site’s frontend. **AI assistant integration** ✅ Yes — Bring Your Own Key (BYOK) supporting OpenAI, Gemini, Claude, and Grok to generate or rewrite content inside the editor. ❌ No — No built-in AI assistant or content generation tool in either the free CMS or Decap Turbo plans. **Collaborative editing** ✅ Yes — Allows multiple users to edit content simultaneously. ❌ No — No simultaneous multi-user editing. Decap Turbo Team plan adds real-time editing visibility (a presence indicator showing who is active), but does not support concurrent editing of the same entry. **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 — Supports custom editor components and custom widgets, which serve as shortcodes and reusable content blocks. Configured by developers in the CMS setup. **SEO tools** ✅ Yes — Built-in tools to optimize and preview content for search engines, content analysis, slug editing, and SERP preview. ⚠️ Yes but — Slug generation and custom file path configuration are supported. No built-in SEO analysis, SERP preview, or content scoring. SEO-related fields must be configured manually in the content schema. **Dark mode** ✅ Yes — Supports full platform dark mode, switchable between Dark and Light. ❌ No — No native dark mode in the CMS admin interface. A community-contributed dark mode CSS (shared via GitHub Discussions) exists as a manual override but is not an official or built-in feature. ## Non-Technical User Experience Feature Sitepins Decap CMS **Designed for non-technicals** ✅ Yes — Core product mission. ⚠️ Yes but — Once set up by a developer, non-technical editors can create and manage content through the web UI. However, initial setup, schema changes, and authentication configuration always require a developer. **Version rollback** ✅ Yes — Undo changes and restore a previous version without touching Git, directly within the CMS. ⚠️ Yes but — Full version history is available through Git. There is no dedicated version rollback UI inside the CMS. Reverting changes requires Git knowledge or developer involvement. **Initial setup by non-dev** ✅ Yes — Zero configuration. Can be set up easily without developer involvement. ❌ No — A developer must configure the config.yml and authentication backend before the CMS is usable by anyone. ## Media Management Feature Sitepins Decap CMS **Media management** ✅ Yes — Upload, organize, drag and drop, rename files and folders, replace images and delete directly from the CMS. ⚠️ Yes but — Built-in media library supports upload, view, and delete via drag-and-drop. External providers (Cloudinary, Uploadcare) available via plugins. File renaming is not supported natively in the media library. **External image URL support** ✅ Yes — Use images hosted on external CDNs or third-party services directly in the editor. ⚠️ Yes but — External media is supported via Cloudinary and Uploadcare plugins. Direct inline external URL input depends on field widget configuration by the developer. ## Collaboration & Teams Feature Sitepins Decap CMS **User access** ✅ Yes — Invite editors by email. Possible without requiring a Git account. ⚠️ Yes but — Git Gateway (via Netlify Identity) allows non-Git users to log in via email. On non-Netlify hosts, setting up external OAuth for editors requires a developer-configured OAuth client. **Custom roles** ✅ Yes — Define specific permission levels for different types of users. E.g. Owner, Admin, Editor. ⚠️ Yes but — Custom roles and permissions are a Decap Turbo feature, available on Team plan ($37/mo) and above. The free core CMS has no centralized role management. **Organization management** ✅ Yes — Manage multiple teams and projects under one account. ⚠️ Yes but — Multi-project management is a Decap Turbo feature. The free CMS is per-site and has no centralized multi-project dashboard. **Branch workflows** ✅ Yes — Manage branches, create PRs, and merge directly from Sitepins. ⚠️ Yes but — Editorial Workflow mode supports draft, review, and publish statuses using Git branches. Available in the free CMS. Creating and merging PRs is done via the Git provider, not inside Decap CMS itself. ## Git & Deployment Feature Sitepins Decap CMS **Git providers** GitHub (all plans), GitLab (Team plan) GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, and Git Gateway (Netlify). Broad multi-provider support out of the box. **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. **Deployment** ✅ Yes — One-click Vercel deployment built-in. Content commits trigger builds on any connected CI/CD platform. Works with Netlify, Vercel, GitHub Pages, Cloudflare Pages, and any Git-integrated host. ## Accessibilities Feature Sitepins Decap CMS **Global search** ✅ Yes — Cmd/Ctrl+K to search for files stored anywhere in the CMS. ⚠️ Yes but — Search across content entries (by title, slug, and configured summary fields) is supported. Search is enabled by default but can exhaust API rate limits on large repositories, and can be disabled in the config. **Edit configs as code** ✅ Yes — Direct access to configuration files. ✅ Yes — Configuration is done entirely via the config.yml file. Editing config as code is the primary and only method for schema and CMS settings. **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 Decap CMS. Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### 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 a free plan or a one-time lifetime deal with no recurring costs - You want your CMS interface in your team's native language ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Decap CMS if: - You want a completely free, open-source, self-hosted CMS with no subscription costs - Your team has a developer comfortable with YAML configuration and Git-based workflows - You need broad Git provider support out of the box (GitHub, GitLab, Bitbucket, Gitea, Azure) - You want maximum control and extensibility through custom widgets, plugins, and open-source contributions - You are already in the Netlify ecosystem and want seamless Git Gateway authentication Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins vs Keystatic URL: https://sitepins.com/compare/sitepins-vs-keystatic Compare Sitepins and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sitepins vs Keystatic Compare Sitepins and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sitepins Git-Based CMS Sitepins 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 Sitepins](https://app.sitepins.com) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Keystatic Git-Based CMS Keystatic is a free, open-source, Git-based CMS built by Thinkmill. It stores content as Markdown, Markdoc, MDX, JSON, or YAML files directly in your Git repository. The admin UI is bundled inside your application and reads from and writes to those files with no separate CMS server or database. Keystatic is code-first and TypeScript-native. [Visit Keystatic](https://keystatic.com) Feature ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Keystatic ## Overview Feature Sitepins Keystatic **CMS type** Git-Based (open source, AGPL-3.0 licensed) Git-Based (open-source, MIT-licensed) **SSG support** Astro, Next.js, Hugo, 11ty, Jekyll, SvelteKit, Nuxt + more Astro, Next.js, Remix (first-party integrations). SvelteKit supported via community setup. Hugo, Jekyll, and 11ty not officially supported. **Pricing entry point** $12/mo (monthly) or $10/mo (annual); $199 one-time lifetime Free forever (core CMS). Keystatic Cloud Pro starts at $10/mo per team (3 users included, $5/mo per additional user). **Free plan** ✅ Yes — Free forever, with limitations (Hobby plan) ✅ Yes — Core CMS is permanently free with no user or project cap. Keystatic Cloud Free allows up to 3 users per team. **Free trial (without credit card)** ✅ Yes — 15 days (no card required) ✅ Yes — No trial needed. The core CMS is permanently free. Keystatic Cloud Free provides full access for up to 3 users. **Content security** ✅ Yes — Highly secured. No database to hack; files are static and stored in Git ✅ Yes — Highly secured. No database, no CMS server. All 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 ❌ No — The CMS admin UI is English only. No native language switcher. i18n for content is not built in and requires manual workarounds or custom schema design. **Mobile friendly** ✅ Yes — Fully mobile and tablet optimized ⚠️ Yes but — Mobile-first editing is listed as a feature, but multiple user reports note the interface is not fully optimized for mobile and integration can be complex on smaller screens. ## Setup & Configuration Feature Sitepins Keystatic **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 install the package, create a keystatic.config.ts file defining the content schema, and configure storage mode and authentication before the CMS is usable. **Starter templates** ✅ Yes — 100+ Astro, Hugo, and Next.js ready-made project templates to launch faster ⚠️ Yes but — Official CLI starters exist for Astro and Next.js. A small number of community starters are available. No large curated template library. **Edit schema modifier** ✅ Yes — Visual schema editor within the CMS. Adjust content field types and settings directly inside the CMS. ❌ No — Schema is defined entirely in code via keystatic.config.ts (TypeScript). There is no visual schema editor. All schema changes require editing the config file directly. ## Editing Experience Feature Sitepins Keystatic **Editor** Visual editor + Markdown + Code Rich text (WYSIWYG) + Markdoc + MDX + JSON/YAML. Auto-generated from your TypeScript schema. **Live preview system** ✅ Yes — Sandbox live preview. See how your content looks on the site before publishing. ⚠️ Yes but — Real-time previews are supported via Next.js Draft Mode integration. Requires developer setup to wire the preview to the frontend. Not available out of the box. **AI assistant integration** ✅ Yes — Bring Your Own Key (BYOK) supporting OpenAI, Gemini, Claude, and Grok to generate or rewrite content inside the editor. ❌ No — No built-in AI assistant or content generation tool in either the core CMS or Keystatic Cloud. **Collaborative editing** ✅ Yes — Allows multiple users to edit content simultaneously. ⚠️ Yes but — Multi-player editing is an experimental feature on Keystatic Cloud Pro. The core CMS has no simultaneous editing. Saving the same file simultaneously creates Git merge conflicts with no built-in resolution UI. **iFrame embed preview** ✅ Yes — Render embedded content like videos or charts live inside the editor. ❌ No — Not a built-in or documented feature. iFrame or embed preview inside the editor is not available natively. **Shortcode support** ✅ Yes — Manage shortcodes and custom content blocks for powerful content structuring. ✅ Yes — Content components (custom blocks) are supported within Markdoc and MDX fields. Developers define reusable components that editors can insert as blocks inside the editor. **SEO tools** ✅ Yes — Built-in tools to optimize and preview content for search engines, content analysis, slug editing, and SERP preview. ⚠️ Yes but — Slug generation is supported via the slug field type. No built-in SEO analysis, SERP preview, or content scoring. SEO metadata fields must be added manually to the content schema. **Dark mode** ✅ Yes — Supports full platform dark mode, switchable between Dark and Light. ❌ No — No dark mode documented for the Keystatic admin UI. Not confirmed as a built-in or switchable feature. ## Non-Technical User Experience Feature Sitepins Keystatic **Designed for non-technicals** ✅ Yes — Core product mission. ⚠️ Yes but — Non-technical editors can use the visual admin UI once a developer has set it up. However, all schema configuration, setup, and schema changes require developer involvement. Keystatic is developer-first by design. **Version rollback** ✅ Yes — Undo changes and restore a previous version without touching Git, directly within the CMS. ⚠️ Yes but — Full version history is available through Git. Every save becomes a commit, giving complete rollback capability. There is no dedicated non-technical rollback UI inside the CMS admin. Reverting requires Git. **Initial setup by non-dev** ✅ Yes — Zero configuration. Can be set up easily without developer involvement. ❌ No — A developer must install the package, define the content schema in TypeScript, and configure storage and authentication before the CMS is usable. ## Media Management Feature Sitepins Keystatic **Media management** ✅ Yes — Upload, organize, drag and drop, rename files and folders, replace images and delete directly from the CMS. ⚠️ Yes but — Images can be uploaded and stored in the Git repository via the image field. Keystatic Cloud Pro adds Cloud Images (a managed image storage, optimization, and delivery service). No folder organization or file renaming in the CMS UI. **External image URL support** ✅ Yes — Use images hosted on external CDNs or third-party services directly in the editor. ⚠️ Yes but — External image URLs can be referenced in content fields. Keystatic Cloud Images serves images via Cloudflare CDN with URL-based transform parameters. No native plugin support for S3 or Cloudinary outside Cloud Images. ## Collaboration & Teams Feature Sitepins Keystatic **User access** ✅ Yes — Invite editors by email. Possible without requiring a Git account. ⚠️ Yes but — Keystatic Cloud allows editors to log in without a GitHub account. Without Keystatic Cloud, users must authenticate directly via GitHub OAuth, requiring a GitHub account. **Custom roles** ✅ Yes — Define specific permission levels for different types of users. E.g. Owner, Admin, Editor. ❌ No — No role-based access control in the core CMS or Keystatic Cloud Free or Pro. All users in a team have access to all projects within that team. Granular role permissions are not available. **Organization management** ✅ Yes — Manage multiple teams and projects under one account. ✅ Yes — Keystatic Cloud organizes projects into teams. Each team can have multiple projects, each connected to a specific GitHub repository. **Branch workflows** ✅ Yes — Manage branches, create PRs, and merge directly from Sitepins. ⚠️ Yes but — Keystatic supports branch-based workflows via GitHub mode. Editors can create and switch branches from within the admin UI. No built-in PR creation, review, or merge UI inside the CMS. These are done in GitHub directly. ## Git & Deployment Feature Sitepins Keystatic **Git providers** GitHub (all plans), GitLab (Team plan) GitHub only via Keystatic Cloud. GitHub and local filesystem in self-hosted mode. GitLab and Bitbucket are not natively supported by Keystatic Cloud. **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 is stored as static files (Markdown, YAML, JSON) in your own GitHub repository. Keystatic Cloud is optional. **Deployment** ✅ Yes — One-click Vercel deployment built-in. Works with any Git-connected CI/CD platform. Content commits trigger builds on Vercel, Netlify, Cloudflare Pages, and other hosts. No built-in one-click deployment. ## Accessibilities Feature Sitepins Keystatic **Global search** ✅ Yes — Cmd/Ctrl+K to search for files stored anywhere in the CMS. ⚠️ Yes but — Keystatic includes a search bar to filter entries within a collection by title or slug. There is no global cross-collection search or keyboard shortcut search across the entire CMS. **Edit configs as code** ✅ Yes — Direct access to configuration files. ✅ Yes — All configuration is done in code via keystatic.config.ts. Editing configs as code is the primary and only method. **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 Keystatic. Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### 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 a free plan or a one-time lifetime deal with no recurring costs - You want your CMS interface in your team's native language ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Keystatic if: - Your team is developer-led and comfortable defining content schemas in TypeScript - You are building with Astro or Next.js and want first-party, deeply integrated CMS support - You need a completely free, open-source CMS with no SaaS dependency for small teams (up to 3 users) - You want a TypeScript Reader API for type-safe content querying at build time - Content lives in your codebase and you want to keep it there with zero infrastructure overhead Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins vs Sveltia CMS URL: https://sitepins.com/compare/sitepins-vs-sveltiacms Compare Sitepins and Sveltia CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sitepins vs Sveltia CMS Compare Sitepins and Sveltia CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sitepins Git-Based CMS Sitepins 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 Sitepins](https://app.sitepins.com) VS ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sveltia CMS Git-Based CMS Sveltia 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 CMS](https://sveltiacms.app) Feature ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sveltia CMS ## Overview 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. Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### 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 ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### 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 Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sitepins vs TinaCMS URL: https://sitepins.com/compare/sitepins-vs-tinacms Compare Sitepins and TinaCMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sitepins vs TinaCMS Compare Sitepins and TinaCMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sitepins Git-Based CMS Sitepins 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 Sitepins](https://app.sitepins.com) VS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## TinaCMS Git-Based CMS TinaCMS is an open-source, Git-backed headless CMS originally developed by Forestry.io and acquired by SSW (Superior Software for Windows). It provides a visual editing interface on top of Markdown, MDX, and JSON files stored in Git, giving developers full control over the content model while abstracting Git complexity for content editors. [Visit TinaCMS](https://tina.io) Feature ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) TinaCMS ## Overview Feature Sitepins TinaCMS **CMS type** Git-Based (open source, AGPL-3.0 licensed) Git-Based (open-source) **SSG support** Astro, Next.js, Hugo, 11ty, Jekyll, SvelteKit, Nuxt + more Astro, Next.js, Hugo, Jekyll, Gatsby, Remix, 11ty, SvelteKit + other frameworks **Pricing entry point** $12/mo (monthly) or $10/mo (annual); $199 one-time lifetime $24/mo (monthly) or $290/yr (annual) — Team plan. No lifetime option. **Free plan** ✅ Yes — Free forever, with limitations (Hobby plan) ✅ Yes — Free forever, limited to 2 users and 1 project (Free plan) **Free trial (without credit card)** ✅ Yes — 15 days (no card required) ❌ No — No time-limited trial. The permanent free plan serves this role. **Content security** ✅ Yes — Highly secured. No database to hack; files are static and stored in Git ✅ Yes — Highly secured. No database to hack; files are stored in your Git repo. SOC 2 framework alignment, AWS-hosted infrastructure, encryption at rest and in transit. **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 ❌ No — English only for the CMS interface. **Mobile friendly** ✅ Yes — Fully mobile and tablet optimized ✅ Yes — Mobile and tablet optimized as of TinaCMS v2.0 (iOS and Android supported) ## Setup & Configuration Feature Sitepins TinaCMS **Non-technical setup** ✅ Yes — Zero configuration. Register, connect your repo and get started without any code or config. ❌ No — Developer-led setup required. A developer must install and configure the `/tina` folder and schema before editors can use the CMS. **Starter templates** ✅ Yes — 100+ Astro, Hugo, and Next.js ready-made project templates to launch faster ⚠️ Yes but — A small set of official CLI starters (Next.js, Astro). Additional community starters exist but no large curated template library. **Edit schema modifier** ✅ Yes — Visual schema editor within the CMS. Adjust content field types and settings directly inside the CMS. ❌ No — Schema is defined in code via TypeScript/JavaScript config files. No visual in-app schema editor. ## Editing Experience Feature Sitepins TinaCMS **Editor** Visual editor + Markdown + Code Visual (contextual/inline) editor + Rich Text (Plate-based) + Markdown + Code **Live preview system** ✅ Yes — Sandbox live preview. See how your content looks on the site before publishing. ⚠️ Yes but — Contextual visual editing with real-time inline preview. Requires developer setup to wire the preview to the frontend. **AI assistant integration** ✅ Yes — Bring Your Own Key (BYOK) supporting OpenAI, Gemini, Claude, and Grok to generate or rewrite content inside the editor. ❌ No — AI features listed as “Coming Soon” on paid plans. TinaGPT is a support chatbot only, not an in-editor content generation tool. **Collaborative editing** ✅ Yes — Allows multiple users to edit content simultaneously. ❌ No — TinaCMS is single-user per document. Simultaneous multi-user editing is not supported. **iFrame embed preview** ✅ Yes — Render embedded content like videos or charts live inside the editor. ⚠️ Yes but — Not a native out-of-the-box feature. iFrame/embed support depends on custom MDX component configuration by a developer. **Shortcode support** ✅ Yes — Manage shortcodes and custom content blocks for powerful content structuring. ✅ Yes — Supports custom Markdown shortcodes via the rich-text field’s custom MDX syntax configuration. **SEO tools** ✅ Yes — Built-in tools to optimize and preview content for search engines, content analysis, slug editing, and SERP preview. ⚠️ Yes but — SEO fields are configurable by developers. No built-in SEO analysis, SERP preview, or content scoring tool out of the box. **Dark mode** ✅ Yes — Supports full platform dark mode, switchable between Dark and Light. ❌ No — Not confirmed as a switchable CMS interface setting. Dark mode is available in TinaDocs (the docs template product) but not documented as a platform-level toggle for the CMS admin. ## Non-Technical User Experience Feature Sitepins TinaCMS **Designed for non-technicals** ✅ Yes — Core product mission. ⚠️ Yes but — Non-technical editors can use the CMS after developer setup, but initial configuration and schema changes require developer involvement. **Version rollback** ✅ Yes — Undo changes and restore a previous version without touching Git, directly within the CMS. ⚠️ Yes but — Content is Git-backed so rollback is possible through Git. No dedicated non-technical rollback UI within the CMS dashboard. **Initial setup by non-dev** ✅ Yes — Zero configuration. Can be set up easily without developer involvement. ❌ No — Requires a developer to install the package, configure the schema, and deploy the admin route before the CMS is usable. ## Media Management Feature Sitepins TinaCMS **Media management** ✅ Yes — Upload, organize, drag and drop, rename files and folders, replace images and delete directly from the CMS. ⚠️ Yes but — Upload, view, and delete media via the Media Manager. External providers (Cloudinary, S3, Digital Ocean Spaces) available. Note: files cannot be renamed through the Media Manager. **External image URL support** ✅ Yes — Use images hosted on external CDNs or third-party services directly in the editor. ⚠️ Yes but — Handled via external media provider plugins (Cloudinary, AWS S3, Digital Ocean Spaces). No direct inline external URL support. ## Collaboration & Teams Feature Sitepins TinaCMS **User access** ✅ Yes — Invite editors by email. Possible without requiring a Git account. ✅ Yes — Invite collaborators via TinaCloud. Users do not need a GitHub account to edit content, only a TinaCloud account. **Custom roles** ✅ Yes — Define specific permission levels for different types of users. E.g. Owner, Admin, Editor. ⚠️ Yes but — Two roles (Admin and Editor) on Free, Team, and Team Plus plans. Three roles available on Business plan (in beta). Custom roles on Enterprise only. **Organization management** ✅ Yes — Manage multiple teams and projects under one account. ✅ Yes — Organizations are supported in TinaCloud to manage multiple projects. **Branch workflows** ✅ Yes — Manage branches, create PRs, and merge directly from Sitepins. ⚠️ Yes but — Editorial Workflow supports branch creation, protected branches, PR-based review, and preview links. Available on Team Plus plan and above only. ## Git & Deployment Feature Sitepins TinaCMS **Git providers** GitHub (all plans), GitLab (Team plan) GitHub only via TinaCloud (including GitHub Enterprise on Enterprise plan). GitLab not supported natively; possible via self-hosting with a custom Git provider. **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 stored as Markdown/MDX/JSON in your own GitHub repository. TinaCloud is optional; self-hosting is available. **Deployment** ✅ Yes — One-click Vercel deployment built-in. Pushes content changes to your Git repo, triggering builds on external hosts. Supports Vercel, Netlify, GitHub Pages, Cloudflare Pages, Cloudflare Workers, and Alibaba Cloud. ## Accessibilities Feature Sitepins TinaCMS **Global search** ✅ Yes — Cmd/Ctrl+K to search for files stored anywhere in the CMS. ⚠️ Yes but — Built-in content search available via TinaCloud with indexer token configuration. Not available in self-hosted mode. **Edit configs as code** ✅ Yes — Direct access to configuration files. ✅ Yes — All configuration is done in code via the `/tina/config.ts` file. Direct editing of config files is the primary method. **Mermaid diagram preview** ✅ Yes — Render Mermaid diagrams live while writing without leaving the CMS. ✅ Yes — Mermaid diagram rendering is supported in the rich-text editor using the Mermaid npm package. Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sitepins](/_astro/sitepins.zjNt-vJb.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### 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 a free plan or a one-time lifetime deal with no recurring costs - You want your CMS interface in your team's native language ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose TinaCMS if: - Your team has a developer who can handle setup and schema configuration - You are building a Next.js or Astro project and want deep contextual visual editing - You need a fully open-source CMS with a self-hosting option for maximum control - You require GitHub Enterprise support for enterprise environments - You prefer a code-first content model with full TypeScript support Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sveltia CMS vs CloudCannon URL: https://sitepins.com/compare/sveltiacms-vs-cloudcannon Compare Sveltia CMS and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sveltia CMS vs CloudCannon Compare Sveltia CMS and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sveltia CMS Git-Based CMS Sveltia 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. [Get Started with Sveltia CMS](https://sveltiacms.app) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## CloudCannon Git-Based CMS CloudCannon is a Git-based CMS platform built for agencies and development teams managing client websites at scale. It offers a great visual editing experience and deep SSG integration, but requires developer configuration before editors can get started. CloudCannon is best suited for teams with dedicated developers who need a robust, enterprise-grade content workflow. [Visit CloudCannon](https://cloudcannon.com) Feature ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sveltia CMS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) CloudCannon ## Overview Feature Sveltia CMS CloudCannon **CMS type** Git-Based (open-source, MIT-licensed). Currently in beta; version 1.0 (GA) scheduled for late 2026. Git-Based (commercial, agency-focused) **SSG support** Astro, Eleventy, Hugo, Jekyll, Next.js, Nuxt, SvelteKit, VitePress, Docusaurus, Middleman, Zola + framework-agnostic support for vanilla JavaScript sites Jekyll, Hugo, Eleventy (11ty), Astro, Next.js, SvelteKit, Gatsby, MkDocs **Pricing entry point** Free forever. MIT-licensed and free for personal and commercial use. No paid tier. $55/mo (monthly) or $49/mo (annual). No lifetime option. **Free plan** ✅ Yes — The entire CMS is free and open source. No user, project, or feature limits. ❌ No — No free plan. 21-day trial only. **Free trial (without credit card)** ✅ Not needed — the CMS is permanently free. ⚠️ Yes but — 21 days, credit card required at the end of the trial. **Content security** ✅ 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. ✅ Yes — Highly secured. No database to hack since files are stored in your Git repo. **Native language support** ✅ 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. ❌ No — No native support. Content translation is handled via third-party tools (e.g. Rosey). **Mobile friendly** ✅ Yes — Fully responsive with dedicated mobile and tablet support, QR code login, and installable as a progressive web app (PWA). ❌ No — No dedicated mobile-optimized editing experience. ## Setup & Configuration Feature Sveltia CMS CloudCannon **Non-technical setup** ❌ No — 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. ❌ No — Developer-led setup required. Needs a cloudcannon.config.yml file to configure inputs and structures. **Starter templates** ⚠️ 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. ❌ No — Only an Astro starter with prebuilt components. Fewer SSG-specific options overall. **Edit schema modifier** ❌ No — Collections and fields are defined in the config file (YAML, TOML, or JSON). No visual schema editor, though JSON Schema validation and IDE auto-completion are provided. ⚠️ Yes but — Via the cloudcannon.config file, editable in-app through Configuration Mode. No visual schema editor. ## Editing Experience Feature Sveltia CMS CloudCannon **Editor** Rich text (Lexical-based WYSIWYG) + Markdown + Code. Content is written out as Markdown, YAML, JSON, or TOML. WYSIWYG Visual Editor — true on-page editing. **Live preview system** ⚠️ Yes but — A preview pane is included, and custom preview templates and styles can be registered through the JavaScript API. Matching the preview to your site’s frontend requires developer setup. ✅ Yes — Real-time in-page preview rendered inside an iFrame. Changes are visible immediately without a full rebuild. **AI assistant integration** ⚠️ Yes but — One-click AI translation via Anthropic, OpenAI, and Google Cloud Translation using your own API key. There is no general-purpose AI writing or rewriting assistant. ⚠️ Yes but — “AI-ready infrastructure” designed for external AI agents, not an in-editor writing assistant. **Collaborative editing** ❌ No — No simultaneous multi-user editing. Collaboration happens through Git commits, and multi-user support with edge-function-based user management is planned for v2.0. ⚠️ Yes but — Only one user edits a file at a time; others can view live in read-only mode, with no merge-conflict risk. **iFrame embed preview** ❌ No — Not documented or available out of the box. ✅ Yes — iFrames are used natively in the Visual Editor for live page previews. **Shortcode support** ✅ Yes — Custom editor components can be registered through the JavaScript API to create reusable block-level components, alongside the built-in code-block and image components. ✅ Yes — Shortcodes can be mapped to visual editing components via configuration. **SEO tools** ❌ No — No built-in SEO analysis, SERP preview, or content scoring. SEO fields must be modeled manually in the configuration. ⚠️ Yes but — Built-in SEO optimization tools. No SERP preview. **Dark mode** ✅ Yes — Built-in light and dark themes. Follows the system preference by default and can be switched in app settings. ✅ Yes — Light and dark mode available, follows browser default. ## Non-Technical User Experience Feature Sveltia CMS CloudCannon **Designed for non-technicals** ⚠️ Yes but — The UI is modern, accessible, and editor-friendly once configured, but setup, schema changes, and authentication require a developer, and every editor needs a Git account. ⚠️ Yes but — Requires a developer for initial setup and configuration before editors can use it. **Version rollback** ⚠️ Yes but — Entries are automatically backed up to browser storage while editing and can be restored as drafts. Full version history lives in Git, with no in-CMS Git rollback UI. ⚠️ Yes but — Requires technical knowledge or developer access to execute. **Initial setup by non-dev** ❌ No — A developer must create the admin files, write the config, and register an OAuth app first. ❌ No — A developer must configure the CMS and instrument templates before editors can use it. ## Media Management Feature Sveltia CMS CloudCannon **Media management** ✅ 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). ✅ Yes — Drag-and-drop media library. Integrates with DAMs (Amazon S3, Cloudinary, Google Cloud Storage) and Git LFS for large-scale asset management. **External image URL support** ✅ 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 photos from Pexels, Pixabay, and Unsplash. ⚠️ Yes but — Handled via DAM integrations. No direct inline external URL support. ## Collaboration & Teams Feature Sveltia CMS CloudCannon **User access** ❌ 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. ✅ Yes — Editors can be invited via email without needing a personal Git account, on any plan. **Custom roles** ❌ No — No role management inside the CMS. Permissions are inherited from the Git provider’s repository access. Roles are planned for v2.0. ✅ Yes — Default permissions on the Standard plan. Custom Permission Groups available on Team and Enterprise. **Organization management** ❌ No — Each site gets its own admin instance. There is no centralized multi-project or multi-team dashboard. ✅ Yes — Organization-level management supported on all plans. **Branch workflows** ⚠️ Yes but — A simple workflow (commit straight to a branch) and Open Authoring (external contributors submit pull requests) are supported. The Editorial Workflow is documented as “not yet supported in Sveltia CMS” and is planned before the 1.0 release. ⚠️ Yes but — Advanced branching workflows are only available on the Team and Enterprise plans. ## Git & Deployment Feature Sveltia CMS CloudCannon **Git providers** GitHub, GitLab, and Gitea/Forgejo, plus a test backend and a local repository workflow. Bitbucket, Azure DevOps, and Git Gateway are explicitly not supported. GitHub, GitLab, Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source under the MIT license. ✅ No — All content stored as standard files (Markdown, JSON, YAML) in your own Git repository. **Deployment** Content commits trigger builds on any connected CI/CD platform — Vercel, Netlify, Cloudflare Pages, GitHub Pages, and more. No built-in one-click deployment. Pushes to your Git repo, triggering builds on external hosts (Vercel, Netlify, Cloudflare Pages). Also offers built-in hosting on a global Cloudflare CDN. ## Accessibilities Feature Sveltia CMS CloudCannon **Global search** ✅ 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). ❌ No — No dedicated global search across CMS content. **Edit configs as code** ✅ 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. ✅ Yes — Configuration Mode allows editing the cloudcannon.config file directly within the app. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature in Sveltia CMS. ❌ No — Not a supported feature. Worth Knowing ### There's a third option: Sitepins Sveltia CMS is free but still in beta, with no roles and no way to onboard an editor who lacks a Git account, while CloudCannon starts at $55/mo with no free plan. Sitepins is open source too (AGPL-3.0, on GitHub) and adds zero-config setup, a visual editor, an AI writing assistant, real-time collaboration, custom roles, and email invites for editors — on a free forever plan or a $199 one-time lifetime deal. [See Sitepins vs Sveltia CMS →](/compare/sitepins-vs-sveltiacms)[See Sitepins vs CloudCannon →](/compare/sitepins-vs-cloudcannon) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Sveltia CMS if: - You want a completely free, MIT-licensed CMS instead of a $55/mo subscription - You want to self-host the CMS with no vendor account in the loop - You publish multilingual content and want first-class i18n with a localized admin UI - Your editors work from phones or tablets and need real mobile support and dark mode - You want instant full-text search across every collection, entry, and asset ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose CloudCannon if: - You need a true on-page WYSIWYG visual editor with real-time preview, no developer wiring required - You need role-based permissions and organization management from your first paid plan - Your editors must be able to join by email invite without a Git account - Your team uses Bitbucket, which Sveltia does not support - You're managing multiple client sites and need agency-grade workflows and dedicated support Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sveltia CMS vs Decap CMS URL: https://sitepins.com/compare/sveltiacms-vs-decapcms Compare Sveltia CMS and Decap CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sveltia CMS vs Decap CMS Compare Sveltia CMS and Decap CMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sveltia CMS Git-Based CMS Sveltia 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. [Get Started with Sveltia CMS](https://sveltiacms.app) VS ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Decap CMS Git-Based CMS Decap CMS (formerly Netlify CMS) is a free, open-source, Git-based CMS independently maintained in the EU. It acts as a React-based wrapper around the Git workflow, storing content directly in your repository alongside your code. Originally created by Netlify and rebranded in February 2023, Decap CMS is designed for developers and content editors working with static site generators. [Visit Decap CMS](https://decapcms.org) Feature ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sveltia CMS ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Decap CMS ## Overview Feature Sveltia CMS Decap CMS **CMS type** Git-Based (open-source, MIT-licensed). Currently in beta; version 1.0 (GA) scheduled for late 2026. Git-Based (open-source, MIT-licensed) **SSG support** Astro, Eleventy, Hugo, Jekyll, Next.js, Nuxt, SvelteKit, VitePress, Docusaurus, Middleman, Zola + framework-agnostic support for vanilla JavaScript sites Hugo, Next.js, Gatsby, Jekyll, 11ty, Astro, Remix, SvelteKit + any SSG that stores content in Git **Pricing entry point** Free forever. MIT-licensed and free for personal and commercial use. No paid tier. Free forever (core CMS). Decap Turbo paid extension starts at $37/mo (Starter) or $112/mo (Team). **Free plan** ✅ Yes — The entire CMS is free and open source. No user, project, or feature limits. ✅ Yes — Core CMS is free forever and fully open source. No user or project limits. **Free trial (without credit card)** ✅ Not needed — the CMS is permanently free. ✅ Not needed — the core CMS is permanently free. Decap Turbo early access includes a free trial on launch. **Content security** ✅ 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. ✅ Yes — Highly secured. No database; all content is stored as static files in your own Git repository. **Native language support** ✅ 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. ⚠️ Yes but — Admin UI defaults to English. Other locales must be manually registered by a developer using the decap-cms-locales package. No out-of-the-box switcher. **Mobile friendly** ✅ Yes — Fully responsive with dedicated mobile and tablet support, QR code login, and installable as a progressive web app (PWA). ❌ No — Not natively optimized for mobile. A community CSS workaround exists, but there’s no official mobile support. ## Setup & Configuration Feature Sveltia CMS Decap CMS **Non-technical setup** ❌ No — 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. ❌ No — A developer must add index.html and config.yml to the project and configure authentication before the CMS is usable. **Starter templates** ⚠️ 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. ⚠️ Yes but — Official starters exist for Hugo, Next.js, Gatsby, and Jekyll. No large curated template library. **Edit schema modifier** ❌ No — Collections and fields are defined in the config file (YAML, TOML, or JSON). No visual schema editor, though JSON Schema validation and IDE auto-completion are provided. ❌ No — Schema is defined entirely in a YAML config.yml file. No visual schema editor inside the CMS. ## Editing Experience Feature Sveltia CMS Decap CMS **Editor** Rich text (Lexical-based WYSIWYG) + Markdown + Code. Content is written out as Markdown, YAML, JSON, or TOML. Rich text (Plate-based, replaces deprecated markdown widget) + Markdown + Code. 16 built-in widgets and custom widgets. **Live preview system** ⚠️ Yes but — A preview pane is included, and custom preview templates and styles can be registered through the JavaScript API. Matching the preview to your site’s frontend requires developer setup. ⚠️ Yes but — Customizable React-based preview templates. Requires developer setup to match the site’s frontend. **AI assistant integration** ⚠️ Yes but — One-click AI translation via Anthropic, OpenAI, and Google Cloud Translation using your own API key. There is no general-purpose AI writing or rewriting assistant. ❌ No — No built-in AI assistant or content generation tool in either the free CMS or Decap Turbo. **Collaborative editing** ❌ No — No simultaneous multi-user editing. Collaboration happens through Git commits, and multi-user support with edge-function-based user management is planned for v2.0. ❌ No — No simultaneous multi-user editing. Decap Turbo Team adds a presence indicator (who’s active), not concurrent editing. **iFrame embed preview** ❌ No — Not documented or available out of the box. ❌ No — Not documented or available out of the box. **Shortcode support** ✅ Yes — Custom editor components can be registered through the JavaScript API to create reusable block-level components, alongside the built-in code-block and image components. ✅ Yes — Custom editor components and widgets serve as shortcodes, configured by developers in the CMS setup. **SEO tools** ❌ No — No built-in SEO analysis, SERP preview, or content scoring. SEO fields must be modeled manually in the configuration. ⚠️ Yes but — Slug and file path config only. No built-in SEO analysis, SERP preview, or content scoring. **Dark mode** ✅ Yes — Built-in light and dark themes. Follows the system preference by default and can be switched in app settings. ❌ No — No native dark mode. A community-contributed CSS override exists but isn’t an official feature. ## Non-Technical User Experience Feature Sveltia CMS Decap CMS **Designed for non-technicals** ⚠️ Yes but — The UI is modern, accessible, and editor-friendly once configured, but setup, schema changes, and authentication require a developer, and every editor needs a Git account. ⚠️ Yes but — Editors can use it once set up, but setup, schema changes, and auth configuration always require a developer. **Version rollback** ⚠️ Yes but — Entries are automatically backed up to browser storage while editing and can be restored as drafts. Full version history lives in Git, with no in-CMS Git rollback UI. ⚠️ Yes but — Full history via Git. No dedicated version rollback UI inside the CMS. **Initial setup by non-dev** ❌ No — A developer must create the admin files, write the config, and register an OAuth app first. ❌ No — A developer must configure config.yml and the authentication backend before the CMS is usable. ## Media Management Feature Sveltia CMS Decap CMS **Media management** ✅ 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). ⚠️ Yes but — Built-in library supports upload, view, and delete via drag-and-drop. External providers (Cloudinary, Uploadcare) via plugins. No file renaming. **External image URL support** ✅ 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 photos from Pexels, Pixabay, and Unsplash. ⚠️ Yes but — Handled via Cloudinary and Uploadcare plugins. No direct inline external URL support. ## Collaboration & Teams Feature Sveltia CMS Decap CMS **User access** ❌ 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. ⚠️ Yes but — Git Gateway (via Netlify Identity) allows non-Git login. On non-Netlify hosts, a developer must configure an external OAuth client. **Custom roles** ❌ No — No role management inside the CMS. Permissions are inherited from the Git provider’s repository access. Roles are planned for v2.0. ⚠️ Yes but — A Decap Turbo feature, available on the Team plan ($37/mo) and above. The free core CMS has no centralized role management. **Organization management** ❌ No — Each site gets its own admin instance. There is no centralized multi-project or multi-team dashboard. ⚠️ Yes but — A Decap Turbo feature. The free CMS is per-site with no centralized multi-project dashboard. **Branch workflows** ⚠️ Yes but — A simple workflow (commit straight to a branch) and Open Authoring (external contributors submit pull requests) are supported. The Editorial Workflow is documented as “not yet supported in Sveltia CMS” and is planned before the 1.0 release. ⚠️ Yes but — Editorial Workflow (draft/review/publish via Git branches) is in the free CMS. PRs are created and merged in the Git provider itself, not inside Decap. ## Git & Deployment Feature Sveltia CMS Decap CMS **Git providers** GitHub, GitLab, and Gitea/Forgejo, plus a test backend and a local repository workflow. Bitbucket, Azure DevOps, and Git Gateway are explicitly not supported. GitHub, GitLab, Gitea, Bitbucket, Azure DevOps, and Git Gateway (Netlify) — the broadest provider support of the two. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source under the MIT license. ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source. **Deployment** Content commits trigger builds on any connected CI/CD platform — Vercel, Netlify, Cloudflare Pages, GitHub Pages, and more. No built-in one-click deployment. Content commits trigger builds on any connected CI/CD platform — Netlify, Vercel, GitHub Pages, Cloudflare Pages, and more. ## Accessibilities Feature Sveltia CMS Decap CMS **Global search** ✅ 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). ⚠️ Yes but — Search by title, slug, and configured summary fields. Can exhaust API rate limits on large repositories; can be disabled. **Edit configs as code** ✅ 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. ✅ Yes — Configuration is done entirely via config.yml. Editing config as code is the primary and only method. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature in Sveltia CMS. ❌ No — Not a built-in or documented feature in Decap CMS. Worth Knowing ### There's a third option: Sitepins Sveltia CMS and Decap CMS both need a developer to create admin files, write a config, and register an OAuth app before an editor can log in — and both leave your editors dependent on a Git account. Sitepins skips all of that: connect your repository and start editing in minutes, with a visual editor, an AI writing assistant, real-time multi-user collaboration, custom roles, and email invites for editors, on a free forever plan. Sitepins is open source too (AGPL-3.0, on GitHub), so you can self-host it or contribute. [See Sitepins vs Sveltia CMS →](/compare/sitepins-vs-sveltiacms)[See Sitepins vs Decap CMS →](/compare/sitepins-vs-decapcms) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Sveltia CMS if: - You want a modern, much faster rewrite of Netlify/Decap CMS with a far better editing UI - Your editors need dark mode, real mobile support, and a localized admin interface out of the box - You publish multilingual content and want first-class i18n with one-click AI translation - You manage a large media library and want built-in image optimization plus S3, Cloudinary, or Uploadcare storage - You want instant full-text search across every collection, entry, and asset ![Decap CMS](/_astro/decap.DapbTytN.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Decap CMS if: - You need Bitbucket, Azure DevOps, or Git Gateway support, none of which Sveltia offers - You need the Editorial Workflow with draft, review, and publish statuses available today - You want a CMS that has already reached a stable release rather than one still in beta - You want a paid tier that adds roles and multi-project management (Decap Turbo) - You rely on the larger existing ecosystem of Decap widgets, plugins, and community answers Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sveltia CMS vs Keystatic URL: https://sitepins.com/compare/sveltiacms-vs-keystatic Compare Sveltia CMS and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sveltia CMS vs Keystatic Compare Sveltia CMS and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sveltia CMS Git-Based CMS Sveltia 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. [Get Started with Sveltia CMS](https://sveltiacms.app) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Keystatic Git-Based CMS Keystatic is a free, open-source, Git-based CMS built by Thinkmill. It stores content as Markdown, Markdoc, MDX, JSON, or YAML files directly in your Git repository. The admin UI is bundled inside your application and reads from and writes to those files with no separate CMS server or database. Keystatic is code-first and TypeScript-native. [Visit Keystatic](https://keystatic.com) Feature ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sveltia CMS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Keystatic ## Overview Feature Sveltia CMS Keystatic **CMS type** Git-Based (open-source, MIT-licensed). Currently in beta; version 1.0 (GA) scheduled for late 2026. Git-Based (open-source, MIT-licensed) **SSG support** Astro, Eleventy, Hugo, Jekyll, Next.js, Nuxt, SvelteKit, VitePress, Docusaurus, Middleman, Zola + framework-agnostic support for vanilla JavaScript sites Astro, Next.js, Remix (first-party integrations). SvelteKit via community setup. Hugo, Jekyll, and 11ty not officially supported. **Pricing entry point** Free forever. MIT-licensed and free for personal and commercial use. No paid tier. Free forever (core CMS). Keystatic Cloud Pro starts at $10/mo per team (3 users included, $5/mo per additional user). **Free plan** ✅ Yes — The entire CMS is free and open source. No user, project, or feature limits. ✅ Yes — Core CMS is free forever with no cap. Keystatic Cloud Free allows up to 3 users per team. **Free trial (without credit card)** ✅ Not needed — the CMS is permanently free. ✅ Not needed — the core CMS is permanently free. **Content security** ✅ 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. ✅ Yes — Highly secured. No database, no CMS server. Content stored as static files in your own Git repository. **Native language support** ✅ 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. ❌ No — Admin UI is English only. No native language switcher, and i18n for content requires manual workarounds. **Mobile friendly** ✅ Yes — Fully responsive with dedicated mobile and tablet support, QR code login, and installable as a progressive web app (PWA). ⚠️ Yes but — Mobile-first editing is listed as a feature, but multiple user reports note the interface isn’t fully optimized and can be complex on smaller screens. ## Setup & Configuration Feature Sveltia CMS Keystatic **Non-technical setup** ❌ No — 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. ❌ No — A developer must install the package, create a keystatic.config.ts file, and configure storage and authentication first. **Starter templates** ⚠️ 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. ⚠️ Yes but — Official CLI starters exist for Astro and Next.js. A small number of community starters, no large library. **Edit schema modifier** ❌ No — Collections and fields are defined in the config file (YAML, TOML, or JSON). No visual schema editor, though JSON Schema validation and IDE auto-completion are provided. ❌ No — Schema is defined entirely in code via keystatic.config.ts (TypeScript), edited outside the CMS. ## Editing Experience Feature Sveltia CMS Keystatic **Editor** Rich text (Lexical-based WYSIWYG) + Markdown + Code. Content is written out as Markdown, YAML, JSON, or TOML. Rich text (WYSIWYG) + Markdoc + MDX + JSON/YAML. Auto-generated from your TypeScript schema. **Live preview system** ⚠️ Yes but — A preview pane is included, and custom preview templates and styles can be registered through the JavaScript API. Matching the preview to your site’s frontend requires developer setup. ⚠️ Yes but — Real-time previews via Next.js Draft Mode integration. Requires developer setup and is tied to that specific integration. **AI assistant integration** ⚠️ Yes but — One-click AI translation via Anthropic, OpenAI, and Google Cloud Translation using your own API key. There is no general-purpose AI writing or rewriting assistant. ❌ No — No built-in AI assistant or content generation tool in the core CMS or Keystatic Cloud. **Collaborative editing** ❌ No — No simultaneous multi-user editing. Collaboration happens through Git commits, and multi-user support with edge-function-based user management is planned for v2.0. ⚠️ Yes but — Multi-player editing is an experimental feature on Keystatic Cloud Pro. The core CMS has none, and simultaneous saves create unresolved Git merge conflicts. **iFrame embed preview** ❌ No — Not documented or available out of the box. ❌ No — Not a built-in or documented feature. **Shortcode support** ✅ Yes — Custom editor components can be registered through the JavaScript API to create reusable block-level components, alongside the built-in code-block and image components. ✅ Yes — Content components (custom blocks) are supported within Markdoc and MDX fields. **SEO tools** ❌ No — No built-in SEO analysis, SERP preview, or content scoring. SEO fields must be modeled manually in the configuration. ❌ No — Only slug generation via the slug field type. No built-in SEO analysis, SERP preview, or scoring. **Dark mode** ✅ Yes — Built-in light and dark themes. Follows the system preference by default and can be switched in app settings. ❌ No — No dark mode documented for the Keystatic admin UI. ## Non-Technical User Experience Feature Sveltia CMS Keystatic **Designed for non-technicals** ⚠️ Yes but — The UI is modern, accessible, and editor-friendly once configured, but setup, schema changes, and authentication require a developer, and every editor needs a Git account. ⚠️ Yes but — Editors can use the visual admin UI once set up, but Keystatic is developer-first: all schema config and setup require a developer. **Version rollback** ⚠️ Yes but — Entries are automatically backed up to browser storage while editing and can be restored as drafts. Full version history lives in Git, with no in-CMS Git rollback UI. ⚠️ Yes but — Every save is a Git commit, giving full history. No dedicated non-technical rollback UI. **Initial setup by non-dev** ❌ No — A developer must create the admin files, write the config, and register an OAuth app first. ❌ No — A developer must install the package, define the TypeScript schema, and configure storage and authentication first. ## Media Management Feature Sveltia CMS Keystatic **Media management** ✅ 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). ⚠️ Yes but — Images upload and store in the Git repo via the image field. Keystatic Cloud Pro adds managed Cloud Images. No folder organization or renaming in the CMS UI. **External image URL support** ✅ 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 photos from Pexels, Pixabay, and Unsplash. ⚠️ Yes but — External URLs can be referenced in content fields. Keystatic Cloud Images serves via Cloudflare CDN with transform params; no native S3/Cloudinary plugin outside Cloud Images. ## Collaboration & Teams Feature Sveltia CMS Keystatic **User access** ❌ 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. ⚠️ Yes but — Keystatic Cloud allows login without a GitHub account. Without Cloud, editors must authenticate directly via GitHub OAuth. **Custom roles** ❌ No — No role management inside the CMS. Permissions are inherited from the Git provider’s repository access. Roles are planned for v2.0. ❌ No — No role-based access control at all, in the core CMS or Keystatic Cloud Free/Pro. All team members can access all projects in a team. **Organization management** ❌ No — Each site gets its own admin instance. There is no centralized multi-project or multi-team dashboard. ⚠️ Yes but — Keystatic Cloud organizes projects into teams. Requires the paid Cloud tier for anything beyond a single project. **Branch workflows** ⚠️ Yes but — A simple workflow (commit straight to a branch) and Open Authoring (external contributors submit pull requests) are supported. The Editorial Workflow is documented as “not yet supported in Sveltia CMS” and is planned before the 1.0 release. ⚠️ Yes but — Branch creation and switching happen inside the admin UI via GitHub mode. No built-in PR creation, review, or merge — that’s done directly in GitHub. ## Git & Deployment Feature Sveltia CMS Keystatic **Git providers** GitHub, GitLab, and Gitea/Forgejo, plus a test backend and a local repository workflow. Bitbucket, Azure DevOps, and Git Gateway are explicitly not supported. GitHub only via Keystatic Cloud. GitHub and local filesystem in self-hosted mode. No GitLab or Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source under the MIT license. ✅ No — No vendor lock-in. Content is stored as static files (Markdown, YAML, JSON) in your own GitHub repository. Keystatic Cloud is optional. **Deployment** Content commits trigger builds on any connected CI/CD platform — Vercel, Netlify, Cloudflare Pages, GitHub Pages, and more. No built-in one-click deployment. Works with any Git-connected CI/CD platform. No built-in one-click deployment. ## Accessibilities Feature Sveltia CMS Keystatic **Global search** ✅ 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). ❌ No — Only a per-collection filter by title or slug. No global cross-collection search. **Edit configs as code** ✅ 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. ✅ Yes — All configuration is done in code via keystatic.config.ts. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature in Sveltia CMS. ❌ No — Not a built-in or documented feature. Worth Knowing ### There's a third option: Sitepins Sveltia CMS and Keystatic are both free and open source, but both are developer-first: one needs a config file plus an OAuth app, the other a TypeScript schema, and neither gives you roles or a rollback UI. Sitepins is open source too (AGPL-3.0, on GitHub), and adds zero-config setup, a visual editor, an AI writing assistant, real-time collaboration, custom roles, and email invites for editors on a free forever plan. [See Sitepins vs Sveltia CMS →](/compare/sitepins-vs-sveltiacms)[See Sitepins vs Keystatic →](/compare/sitepins-vs-keystatic) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Sveltia CMS if: - You want a config-file setup (YAML, TOML, or JSON) instead of writing TypeScript schemas - You need GitLab or Gitea/Forgejo support, not GitHub only - Your editors need dark mode, a localized admin UI, and real mobile support out of the box - You publish multilingual content and want first-class i18n with one-click AI translation - You want instant full-text search across every collection, entry, and asset ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Keystatic if: - Your team is comfortable defining content schemas in TypeScript and wants type-safe content - You're building with Astro, Next.js, or Remix and want first-party integration depth - You want a stable, released CMS rather than one still in beta - You want the admin UI bundled inside your own app rather than served as a separate SPA - You want a cheap managed-cloud upgrade path ($10/mo for a 3-user team) with hosted images Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Sveltia CMS vs TinaCMS URL: https://sitepins.com/compare/sveltiacms-vs-tinacms Compare Sveltia CMS and TinaCMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # Sveltia CMS vs TinaCMS Compare Sveltia CMS and TinaCMS side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Sveltia CMS Git-Based CMS Sveltia 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. [Get Started with Sveltia CMS](https://sveltiacms.app) VS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## TinaCMS Git-Based CMS TinaCMS is an open-source, Git-backed headless CMS originally developed by Forestry.io and acquired by SSW (Superior Software for Windows). It provides a visual editing interface on top of Markdown, MDX, and JSON files stored in Git, giving developers full control over the content model while abstracting Git complexity for content editors. [Visit TinaCMS](https://tina.io) Feature ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sveltia CMS ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) TinaCMS ## Overview Feature Sveltia CMS TinaCMS **CMS type** Git-Based (open-source, MIT-licensed). Currently in beta; version 1.0 (GA) scheduled for late 2026. Git-Based (open-source, TinaCloud optional) **SSG support** Astro, Eleventy, Hugo, Jekyll, Next.js, Nuxt, SvelteKit, VitePress, Docusaurus, Middleman, Zola + framework-agnostic support for vanilla JavaScript sites Astro, Next.js, Hugo, Jekyll, Gatsby, Remix, 11ty, SvelteKit + other frameworks **Pricing entry point** Free forever. MIT-licensed and free for personal and commercial use. No paid tier. $24/mo (monthly) or $290/yr (annual) — Team plan. No lifetime option. **Free plan** ✅ Yes — The entire CMS is free and open source. No user, project, or feature limits. ⚠️ Yes but — Free forever, limited to 2 users and 1 project. **Free trial (without credit card)** ✅ Not needed — the CMS is permanently free. ❌ No — No time-limited trial. The permanent free plan (2 users, 1 project) serves this role. **Content security** ✅ 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. ✅ Yes — Highly secured. No database; files stored in Git. SOC 2 framework alignment, AWS-hosted infrastructure, encryption at rest and in transit. **Native language support** ✅ 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. ❌ No — English only for the CMS interface. **Mobile friendly** ✅ Yes — Fully responsive with dedicated mobile and tablet support, QR code login, and installable as a progressive web app (PWA). ✅ Yes — Mobile and tablet optimized as of TinaCMS v2.0 (iOS and Android supported). ## Setup & Configuration Feature Sveltia CMS TinaCMS **Non-technical setup** ❌ No — 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. ❌ No — A developer must configure the /tina folder and schema before editors can use the CMS. **Starter templates** ⚠️ 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. ⚠️ Yes but — A small set of official CLI starters (Next.js, Astro). Some community starters exist, no large library. **Edit schema modifier** ❌ No — Collections and fields are defined in the config file (YAML, TOML, or JSON). No visual schema editor, though JSON Schema validation and IDE auto-completion are provided. ❌ No — Schema is defined in code via TypeScript/JavaScript config files. No visual in-app schema editor. ## Editing Experience Feature Sveltia CMS TinaCMS **Editor** Rich text (Lexical-based WYSIWYG) + Markdown + Code. Content is written out as Markdown, YAML, JSON, or TOML. Visual (contextual/inline) editor + Rich Text (Plate-based) + Markdown + Code. **Live preview system** ⚠️ Yes but — A preview pane is included, and custom preview templates and styles can be registered through the JavaScript API. Matching the preview to your site’s frontend requires developer setup. ⚠️ Yes but — Contextual, on-page visual editing with real-time inline preview. Requires developer setup to wire to the frontend. **AI assistant integration** ⚠️ Yes but — One-click AI translation via Anthropic, OpenAI, and Google Cloud Translation using your own API key. There is no general-purpose AI writing or rewriting assistant. ❌ No — Listed as “Coming Soon” on paid plans. TinaGPT is a support chatbot only, not an in-editor content generation tool. **Collaborative editing** ❌ No — No simultaneous multi-user editing. Collaboration happens through Git commits, and multi-user support with edge-function-based user management is planned for v2.0. ❌ No — TinaCMS is single-user per document. Simultaneous multi-user editing is not supported. **iFrame embed preview** ❌ No — Not documented or available out of the box. ⚠️ Yes but — Not native. iFrame/embed support depends on custom MDX component configuration by a developer. **Shortcode support** ✅ Yes — Custom editor components can be registered through the JavaScript API to create reusable block-level components, alongside the built-in code-block and image components. ✅ Yes — Custom Markdown shortcodes via the rich-text field’s custom MDX syntax configuration. **SEO tools** ❌ No — No built-in SEO analysis, SERP preview, or content scoring. SEO fields must be modeled manually in the configuration. ⚠️ Yes but — SEO fields are developer-configurable. No built-in SEO analysis, SERP preview, or content scoring. **Dark mode** ✅ Yes — Built-in light and dark themes. Follows the system preference by default and can be switched in app settings. ❌ No — Not confirmed as a switchable CMS setting (dark mode exists in the separate TinaDocs product only). ## Non-Technical User Experience Feature Sveltia CMS TinaCMS **Designed for non-technicals** ⚠️ Yes but — The UI is modern, accessible, and editor-friendly once configured, but setup, schema changes, and authentication require a developer, and every editor needs a Git account. ⚠️ Yes but — Editors can use it once set up, but initial configuration and schema changes always require a developer. **Version rollback** ⚠️ Yes but — Entries are automatically backed up to browser storage while editing and can be restored as drafts. Full version history lives in Git, with no in-CMS Git rollback UI. ⚠️ Yes but — Content is Git-backed so rollback is possible. No dedicated non-technical rollback UI. **Initial setup by non-dev** ❌ No — A developer must create the admin files, write the config, and register an OAuth app first. ❌ No — A developer must install the package, configure the schema, and deploy the admin route first. ## Media Management Feature Sveltia CMS TinaCMS **Media management** ✅ 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). ⚠️ Yes but — Upload, view, and delete via the Media Manager. External providers (Cloudinary, S3, Digital Ocean Spaces). No file renaming. **External image URL support** ✅ 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 photos from Pexels, Pixabay, and Unsplash. ⚠️ Yes but — Handled via external media provider plugins. No direct inline external URL support. ## Collaboration & Teams Feature Sveltia CMS TinaCMS **User access** ❌ 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. ✅ Yes — Invite via TinaCloud. Editors need only a TinaCloud account, no GitHub account required. **Custom roles** ❌ No — No role management inside the CMS. Permissions are inherited from the Git provider’s repository access. Roles are planned for v2.0. ⚠️ Yes but — Two roles (Admin, Editor) on Free, Team, and Team Plus. Three roles on Business (beta). Custom roles on Enterprise only. **Organization management** ❌ No — Each site gets its own admin instance. There is no centralized multi-project or multi-team dashboard. ✅ Yes — Organizations are supported in TinaCloud to manage multiple projects. **Branch workflows** ⚠️ Yes but — A simple workflow (commit straight to a branch) and Open Authoring (external contributors submit pull requests) are supported. The Editorial Workflow is documented as “not yet supported in Sveltia CMS” and is planned before the 1.0 release. ⚠️ Yes but — Branch creation, protected branches, PR review, and preview links — available on the Team Plus plan and above only. ## Git & Deployment Feature Sveltia CMS TinaCMS **Git providers** GitHub, GitLab, and Gitea/Forgejo, plus a test backend and a local repository workflow. Bitbucket, Azure DevOps, and Git Gateway are explicitly not supported. GitHub only via TinaCloud (including GitHub Enterprise on the Enterprise plan). GitLab not supported natively. **Vendor lock-in** ✅ No — No vendor lock-in. Content lives in your own Git repository. Self-hosted and fully open source under the MIT license. ✅ No — No vendor lock-in. Content stored as Markdown/MDX/JSON in your own GitHub repository. TinaCloud is optional; self-hosting is available. **Deployment** Content commits trigger builds on any connected CI/CD platform — Vercel, Netlify, Cloudflare Pages, GitHub Pages, and more. No built-in one-click deployment. Pushes content changes to your Git repo, triggering builds on Vercel, Netlify, GitHub Pages, Cloudflare Pages, Cloudflare Workers, and Alibaba Cloud. ## Accessibilities Feature Sveltia CMS TinaCMS **Global search** ✅ 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). ⚠️ Yes but — Built-in via TinaCloud with indexer token configuration. Not available in self-hosted mode. **Edit configs as code** ✅ 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. ✅ Yes — All configuration is done in code via /tina/config.ts. Direct editing of config files is the primary method. **Mermaid diagram preview** ❌ No — Not a built-in or documented feature in Sveltia CMS. ✅ Yes — Mermaid diagram rendering is supported in the rich-text editor using the Mermaid npm package. Worth Knowing ### There's a third option: Sitepins Sveltia CMS is free but still in beta and requires every editor to hold a Git account, while TinaCMS charges $24/mo once you pass 2 users and 1 project. Sitepins gives you a visual editor, an AI writing assistant, real-time collaboration, custom roles, and email invites for editors with zero config to get started — on a free forever plan or a $199 one-time lifetime deal. Like Sveltia, Sitepins is open source (AGPL-3.0, on GitHub) and can be self-hosted. [See Sitepins vs Sveltia CMS →](/compare/sitepins-vs-sveltiacms)[See Sitepins vs TinaCMS →](/compare/sitepins-vs-tinacms) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![Sveltia CMS](/_astro/sveltia.Clb6rTC1.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Sveltia CMS if: - You want a completely free, MIT-licensed CMS with no paid cloud tier and no user or project caps - You need GitLab or Gitea/Forgejo, which TinaCloud does not support - You publish multilingual content and want first-class i18n with a localized admin UI - You want built-in image optimization and external storage (S3, Cloudinary, Uploadcare) without extra plugins - You want instant full-text search across every collection, entry, and asset ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose TinaCMS if: - You're building with Next.js or Astro and want deep, contextual on-page visual editing - You want editors to log in without a Git account, via TinaCloud - You need Mermaid diagram support directly in the content editor - You need role-based access and organization management for multiple projects - You're fine paying for a managed cloud (SOC 2-aligned, AWS-hosted) instead of self-hosting Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## TinaCMS vs CloudCannon URL: https://sitepins.com/compare/tinacms-vs-cloudcannon Compare TinaCMS and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # TinaCMS vs CloudCannon Compare TinaCMS and CloudCannon side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## TinaCMS Git-Based CMS TinaCMS is an open-source, Git-backed headless CMS originally developed by Forestry.io and acquired by SSW (Superior Software for Windows). It provides a visual editing interface on top of Markdown, MDX, and JSON files stored in Git, giving developers full control over the content model while abstracting Git complexity for content editors. [Get Started with TinaCMS](https://tina.io) VS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## CloudCannon Git-Based CMS CloudCannon is a Git-based CMS platform built for agencies and development teams managing client websites at scale. It offers a great visual editing experience and deep SSG integration, but requires developer configuration before editors can get started. CloudCannon is best suited for teams with dedicated developers who need a robust, enterprise-grade content workflow. [Visit CloudCannon](https://cloudcannon.com) Feature ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) TinaCMS ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) CloudCannon ## Overview Feature TinaCMS CloudCannon **CMS type** Git-Based (open-source, TinaCloud optional) Git-Based (commercial, agency-focused) **SSG support** Astro, Next.js, Hugo, Jekyll, Gatsby, Remix, 11ty, SvelteKit + other frameworks Jekyll, Hugo, Eleventy (11ty), Astro, Next.js, SvelteKit, Gatsby, MkDocs **Pricing entry point** $24/mo (monthly) or $290/yr (annual) — Team plan. No lifetime option. $55/mo (monthly) or $49/mo (annual). No lifetime option. **Free plan** ⚠️ Yes but — Free forever, limited to 2 users and 1 project. ❌ No — No free plan. 21-day trial only. **Free trial (without credit card)** ❌ No — No time-limited trial. The permanent free plan (2 users, 1 project) serves this role. ⚠️ Yes but — 21 days, credit card required at the end of the trial. **Content security** ✅ Yes — Highly secured. No database; files in Git. SOC 2 framework alignment, AWS-hosted infrastructure, encryption at rest and in transit. ✅ Yes — Highly secured. No database to hack since files are stored in your Git repo. **Native language support** ❌ No — English only for the CMS interface. ❌ No — No native support. Content translation is handled via third-party tools (e.g. Rosey). **Mobile friendly** ✅ Yes — Mobile and tablet optimized as of TinaCMS v2.0 (iOS and Android supported). ❌ No — No dedicated mobile-optimized editing experience. ## Setup & Configuration Feature TinaCMS CloudCannon **Non-technical setup** ❌ No — A developer must configure the /tina folder and schema before editors can use the CMS. ❌ No — Developer-led setup required. Needs a cloudcannon.config.yml file to configure inputs and structures. **Starter templates** ⚠️ Yes but — A small set of official CLI starters (Next.js, Astro). Some community starters, no large library. ❌ No — Only an Astro starter with prebuilt components. Fewer SSG-specific options overall. **Edit schema modifier** ❌ No — Schema is defined in code via TypeScript/JavaScript config files, edited outside the CMS. No visual schema editor. ⚠️ Yes but — Via the cloudcannon.config file, editable in-app through Configuration Mode. No visual schema editor. ## Editing Experience Feature TinaCMS CloudCannon **Editor** Visual (contextual/inline) editor + Rich Text (Plate-based) + Markdown + Code. WYSIWYG Visual Editor — true on-page editing. **Live preview system** ⚠️ Yes but — Contextual, on-page visual editing with real-time inline preview. Requires developer setup to wire to the frontend. ✅ Yes — Real-time in-page preview rendered inside an iFrame. Changes are visible immediately without a full rebuild. **AI assistant integration** ❌ No — Listed as “Coming Soon” on paid plans. TinaGPT is a support chatbot only. ⚠️ Yes but — “AI-ready infrastructure” designed for external AI agents, not an in-editor writing assistant. **Collaborative editing** ❌ No — TinaCMS is single-user per document. Simultaneous multi-user editing is not supported. ⚠️ Yes but — Only one user edits a file at a time; others can view live in read-only mode. **iFrame embed preview** ⚠️ Yes but — Not native. iFrame/embed support depends on custom MDX component configuration by a developer. ✅ Yes — iFrames are used natively in the Visual Editor for live page previews. **Shortcode support** ✅ Yes — Custom Markdown shortcodes via the rich-text field’s custom MDX syntax configuration. ✅ Yes — Shortcodes can be mapped to visual editing components via configuration. **SEO tools** ❌ No — SEO fields are developer-configurable, but there’s no built-in SEO analysis, SERP preview, or content scoring. ⚠️ Yes but — Built-in SEO optimization tools. No SERP preview. **Dark mode** ❌ No — Not confirmed as a switchable CMS setting (dark mode exists in the separate TinaDocs product only). ✅ Yes — Light and dark mode available, follows browser default. ## Non-Technical User Experience Feature TinaCMS CloudCannon **Designed for non-technicals** ⚠️ Yes but — Editors can use it once set up, but initial configuration and schema changes always require a developer. ⚠️ Yes but — Requires a developer for initial setup and configuration before editors can use it. **Version rollback** ⚠️ Yes but — Content is Git-backed so rollback is possible. No dedicated non-technical rollback UI. ⚠️ Yes but — Requires technical knowledge or developer access to execute. **Initial setup by non-dev** ❌ No — A developer must install the package, configure the schema, and deploy the admin route first. ❌ No — A developer must configure the CMS and instrument templates before editors can use it. ## Media Management Feature TinaCMS CloudCannon **Media management** ⚠️ Yes but — Upload, view, and delete via the Media Manager. External providers (Cloudinary, S3, Digital Ocean Spaces). No file renaming. ✅ Yes — Drag-and-drop media library. Integrates with DAMs (Amazon S3, Cloudinary, Google Cloud Storage) and Git LFS for large-scale asset management. **External image URL support** ⚠️ Yes but — Handled via external media provider plugins. No direct inline external URL support. ⚠️ Yes but — Handled via DAM integrations. No direct inline external URL support. ## Collaboration & Teams Feature TinaCMS CloudCannon **User access** ✅ Yes — Invite via TinaCloud. Editors need only a TinaCloud account, no GitHub account required. ✅ Yes — Editors can be invited via email without needing a personal Git account. **Custom roles** ⚠️ Yes but — Two roles (Admin, Editor) on Free, Team, and Team Plus. Three roles on Business (beta). Custom roles on Enterprise only. ✅ Yes — Default permissions on the Standard plan. Custom Permission Groups available on Team and Enterprise. **Organization management** ✅ Yes — Organizations are supported in TinaCloud to manage multiple projects. ✅ Yes — Organization-level management supported on all plans. **Branch workflows** ⚠️ Yes but — Branch creation, protected branches, PR review, and preview links — available on the Team Plus plan and above only. ⚠️ Yes but — Advanced branching workflows are only available on the Team and Enterprise plans. ## Git & Deployment Feature TinaCMS CloudCannon **Git providers** GitHub only via TinaCloud, including GitHub Enterprise on the Enterprise plan. GitLab not supported natively. GitHub, GitLab, Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content stored as Markdown/MDX/JSON in your own GitHub repository. TinaCloud is optional; self-hosting is available. ✅ No — All content stored as standard files (Markdown, JSON, YAML) in your own Git repository. **Deployment** Pushes content changes to your Git repo, triggering builds on Vercel, Netlify, GitHub Pages, Cloudflare Pages, Cloudflare Workers, and Alibaba Cloud. Pushes to your Git repo, triggering builds on external hosts (Vercel, Netlify, Cloudflare Pages). Also offers built-in hosting on a global Cloudflare CDN. ## Accessibilities Feature TinaCMS CloudCannon **Global search** ⚠️ Yes but — Built-in via TinaCloud with indexer token configuration. Not available in self-hosted mode. ❌ No — No dedicated global search across CMS content. **Edit configs as code** ✅ Yes — All configuration is done in code via /tina/config.ts. ✅ Yes — Configuration Mode allows editing the cloudcannon.config file directly within the app. **Mermaid diagram preview** ✅ Yes — Mermaid diagram rendering is supported in the rich-text editor using the Mermaid npm package. ❌ No — Not a supported feature. Worth Knowing ### There's a third option: Sitepins TinaCMS caps its free plan at 2 users and 1 project, and CloudCannon skips a free plan entirely at $55/mo. Sitepins gives you a visual editor, AI writing assistant, real-time collaboration, and one-click Vercel deploys with zero setup required — free forever, or a $199 one-time lifetime deal instead of a recurring subscription. Sitepins is open source too (AGPL-3.0, on GitHub), so you can self-host it or contribute. [See Sitepins vs TinaCMS →](/compare/sitepins-vs-tinacms)[See Sitepins vs CloudCannon →](/compare/sitepins-vs-cloudcannon) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose TinaCMS if: - You want a genuine free tier to start on, even if capped at 2 users and 1 project - You need Mermaid diagrams and a mobile-optimized editor without paying agency-tier pricing - You want GitHub Enterprise support available on a growth plan - You're building on a wide range of SSGs, including Hugo, Jekyll, and Gatsby - You'd rather self-host and avoid an agency-priced subscription ![CloudCannon](/_astro/cloudcannon.DYHGnsm9.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose CloudCannon if: - You need a true on-page WYSIWYG visual editor with real-time preview, no developer wiring required - You want built-in DAM integrations (S3, Cloudinary, Google Cloud Storage) and Git LFS for large media libraries - Your team needs GitLab or Bitbucket support, not just GitHub - You want default role-based permissions from your first paid plan, not gated behind an enterprise tier - You're managing multiple client sites and need agency-grade workflows and support Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## TinaCMS vs Keystatic URL: https://sitepins.com/compare/tinacms-vs-keystatic Compare TinaCMS and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. CMS Comparison # TinaCMS vs Keystatic Compare TinaCMS and Keystatic side-by-side. Explore setup, editing experience, non-technical usability, collaboration, Git workflow, and pricing. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) [Compare Center](/compare) ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## TinaCMS Git-Based CMS TinaCMS is an open-source, Git-backed headless CMS originally developed by Forestry.io and acquired by SSW (Superior Software for Windows). It provides a visual editing interface on top of Markdown, MDX, and JSON files stored in Git, giving developers full control over the content model while abstracting Git complexity for content editors. [Get Started with TinaCMS](https://tina.io) VS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ## Keystatic Git-Based CMS Keystatic is a free, open-source, Git-based CMS built by Thinkmill. It stores content as Markdown, Markdoc, MDX, JSON, or YAML files directly in your Git repository. The admin UI is bundled inside your application and reads from and writes to those files with no separate CMS server or database. Keystatic is code-first and TypeScript-native. [Visit Keystatic](https://keystatic.com) Feature ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) TinaCMS ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Keystatic ## Overview Feature TinaCMS Keystatic **CMS type** Git-Based (open-source, TinaCloud optional) Git-Based (open-source, MIT-licensed) **SSG support** Astro, Next.js, Hugo, Jekyll, Gatsby, Remix, 11ty, SvelteKit + other frameworks Astro, Next.js, Remix (first-party integrations). SvelteKit via community setup. Hugo, Jekyll, and 11ty not officially supported. **Pricing entry point** $24/mo (monthly) or $290/yr (annual) — Team plan. No lifetime option. Free forever (core CMS). Keystatic Cloud Pro starts at $10/mo per team (3 users included, $5/mo per additional user). **Free plan** ⚠️ Yes but — Free forever, limited to 2 users and 1 project. ✅ Yes — Core CMS is free forever with no cap. Keystatic Cloud Free allows up to 3 users per team. **Free trial (without credit card)** ❌ No — No time-limited trial. The permanent free plan (2 users, 1 project) serves this role. ✅ Not needed — the core CMS is permanently free. **Content security** ✅ Yes — Highly secured. No database; files in Git. SOC 2 framework alignment, AWS-hosted infrastructure, encryption at rest and in transit. ✅ Yes — Highly secured. No database, no CMS server. Content stored as static files in your own Git repository. **Native language support** ❌ No — English only for the CMS interface. ❌ No — Admin UI is English only. No native language switcher, and i18n for content requires manual workarounds. **Mobile friendly** ✅ Yes — Mobile and tablet optimized as of TinaCMS v2.0 (iOS and Android supported). ⚠️ Yes but — Mobile-first editing is listed as a feature, but multiple user reports note the interface isn’t fully optimized and can be complex on smaller screens. ## Setup & Configuration Feature TinaCMS Keystatic **Non-technical setup** ❌ No — A developer must configure the /tina folder and schema before editors can use the CMS. ❌ No — A developer must install the package, create a keystatic.config.ts file, and configure storage and authentication first. **Starter templates** ⚠️ Yes but — A small set of official CLI starters (Next.js, Astro). Some community starters, no large library. ⚠️ Yes but — Official CLI starters exist for Astro and Next.js. A small number of community starters, no large library. **Edit schema modifier** ❌ No — Schema is defined in code via TypeScript/JavaScript config files. No visual schema editor. ❌ No — Schema is defined entirely in code via keystatic.config.ts (TypeScript). No visual schema editor. ## Editing Experience Feature TinaCMS Keystatic **Editor** Visual (contextual/inline) editor + Rich Text (Plate-based) + Markdown + Code. Rich text (WYSIWYG) + Markdoc + MDX + JSON/YAML. Auto-generated from your TypeScript schema. **Live preview system** ⚠️ Yes but — Contextual, on-page visual editing with real-time inline preview. Requires developer setup to wire to the frontend. ⚠️ Yes but — Real-time previews via Next.js Draft Mode integration. Requires developer setup and is tied to that specific integration. **AI assistant integration** ❌ No — Listed as “Coming Soon” on paid plans. TinaGPT is a support chatbot only. ❌ No — No built-in AI assistant or content generation tool in the core CMS or Keystatic Cloud. **Collaborative editing** ❌ No — TinaCMS is single-user per document. Simultaneous multi-user editing is not supported. ⚠️ Yes but — Multi-player editing is an experimental feature on Keystatic Cloud Pro. The core CMS has none, and simultaneous saves create unresolved Git merge conflicts. **iFrame embed preview** ⚠️ Yes but — Not native. iFrame/embed support depends on custom MDX component configuration by a developer. ❌ No — Not a built-in or documented feature. **Shortcode support** ✅ Yes — Custom Markdown shortcodes via the rich-text field’s custom MDX syntax configuration. ✅ Yes — Content components (custom blocks) are supported within Markdoc and MDX fields. **SEO tools** ⚠️ Yes but — SEO fields are developer-configurable. No built-in SEO analysis, SERP preview, or content scoring. ⚠️ Yes but — Slug generation via the slug field type. No built-in SEO analysis, SERP preview, or scoring. **Dark mode** ❌ No — Not confirmed as a switchable CMS setting (dark mode exists in the separate TinaDocs product only). ❌ No — No dark mode documented for the Keystatic admin UI. ## Non-Technical User Experience Feature TinaCMS Keystatic **Designed for non-technicals** ⚠️ Yes but — Editors can use it once set up, but initial configuration and schema changes always require a developer. ⚠️ Yes but — Editors can use the visual admin UI once set up, but Keystatic is developer-first: all schema config and setup require a developer. **Version rollback** ⚠️ Yes but — Content is Git-backed so rollback is possible. No dedicated non-technical rollback UI. ⚠️ Yes but — Every save is a Git commit, giving full history. No dedicated non-technical rollback UI. **Initial setup by non-dev** ❌ No — A developer must install the package, configure the schema, and deploy the admin route first. ❌ No — A developer must install the package, define the TypeScript schema, and configure storage and authentication first. ## Media Management Feature TinaCMS Keystatic **Media management** ⚠️ Yes but — Upload, view, and delete via the Media Manager. External providers (Cloudinary, S3, Digital Ocean Spaces). No file renaming. ⚠️ Yes but — Images upload and store in the Git repo via the image field. Keystatic Cloud Pro adds managed Cloud Images. No folder organization or renaming in the CMS UI. **External image URL support** ⚠️ Yes but — Handled via external media provider plugins. No direct inline external URL support. ⚠️ Yes but — External URLs can be referenced in content fields. Keystatic Cloud Images serves via Cloudflare CDN with transform params. ## Collaboration & Teams Feature TinaCMS Keystatic **User access** ✅ Yes — Invite via TinaCloud. Editors need only a TinaCloud account, no GitHub account required. ⚠️ Yes but — Keystatic Cloud allows login without a GitHub account. Without Cloud, editors must authenticate directly via GitHub OAuth. **Custom roles** ⚠️ Yes but — Two roles (Admin, Editor) on Free, Team, and Team Plus. Three roles on Business (beta). Custom roles on Enterprise only. ❌ No — No role-based access control at all, in the core CMS or Keystatic Cloud Free/Pro. All team members can access all projects in a team. **Organization management** ✅ Yes — Organizations are supported in TinaCloud to manage multiple projects. ⚠️ Yes but — Keystatic Cloud organizes projects into teams. Requires the paid Cloud tier for anything beyond a single project. **Branch workflows** ⚠️ Yes but — Branch creation, protected branches, PR review, and preview links — available on the Team Plus plan and above only. ⚠️ Yes but — Branch creation and switching happen inside the admin UI via GitHub mode. No built-in PR creation, review, or merge — that’s done directly in GitHub. ## Git & Deployment Feature TinaCMS Keystatic **Git providers** GitHub only via TinaCloud, including GitHub Enterprise on the Enterprise plan. GitLab not supported natively. GitHub only via Keystatic Cloud. GitHub and local filesystem in self-hosted mode. No GitLab or Bitbucket. **Vendor lock-in** ✅ No — No vendor lock-in. Content stored as Markdown/MDX/JSON in your own GitHub repository. TinaCloud is optional; self-hosting is available. ✅ No — No vendor lock-in. Content is stored as static files (Markdown, YAML, JSON) in your own GitHub repository. Keystatic Cloud is optional. **Deployment** Pushes content changes to your Git repo, triggering builds on Vercel, Netlify, GitHub Pages, Cloudflare Pages, Cloudflare Workers, and Alibaba Cloud. Works with any Git-connected CI/CD platform. No built-in one-click deployment. ## Accessibilities Feature TinaCMS Keystatic **Global search** ⚠️ Yes but — Built-in via TinaCloud with indexer token configuration. Not available in self-hosted mode. ❌ No — Only a per-collection filter by title or slug. No global cross-collection search. **Edit configs as code** ✅ Yes — All configuration is done in code via /tina/config.ts. ✅ Yes — All configuration is done in code via keystatic.config.ts. **Mermaid diagram preview** ✅ Yes — Mermaid diagram rendering is supported in the rich-text editor using the Mermaid npm package. ❌ No — Not a built-in or documented feature. Worth Knowing ### There's a third option: Sitepins Both TinaCMS and Keystatic need a developer to write a config file and set up a schema before editors can log in, and neither one gives you real-time collaborative editing on the same document. Sitepins connects to your repo with zero config and includes a visual editor, AI writing assistant, true multi-user collaboration, and custom roles — free forever, or a $199 one-time lifetime deal. It is open source as well (AGPL-3.0, on GitHub), so self-hosting stays an option. [See Sitepins vs TinaCMS →](/compare/sitepins-vs-tinacms)[See Sitepins vs Keystatic →](/compare/sitepins-vs-keystatic) Note: If you found any wrong information here, please [contact us](/contact) and we will fix it. ## Which one is right for you? A quick summary to help you choose the right Git-based CMS. ![TinaCMS](/_astro/tina.B0gx8_E3.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose TinaCMS if: - You want editors to log in without a GitHub account, via a managed TinaCloud account - You need Mermaid diagram rendering directly in the content editor - You want a mobile-optimized editing experience for your team - You're building across a wider range of SSGs (Hugo, Jekyll, Gatsby included) with one CMS - You want built-in content search without waiting on a self-hosted workaround ![Keystatic](/_astro/keystatic.uuMWD-Xp.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Choose Keystatic if: - You want a completely free, self-hosted CMS with no required subscription for small teams - Your team wants a code-first, TypeScript-native schema with a Reader API for type-safe content queries - You're building specifically with Astro, Next.js, or Remix and want a first-party integration - Content should live entirely inside your codebase with zero separate CMS server or database - You want a cheaper managed-cloud upgrade path ($10/mo for a 3-user team) if you outgrow self-hosting Migration Support ### 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 Free Migration Help](/contact) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Get in Touch URL: https://sitepins.com/contact Sitepins is an open source, Git-based headless CMS for Astro, Next.js, Hugo and more. Give your team a visual editor, keep full version control, and self-host it free or use Sitepins Cloud. Contact Us # Get in Touch ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ## Let’s Talk We're here to help you with any questions, feedback, or inquiries ![](/_astro/email.CQ16tDB_.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) Email [hi@sitepins.com](mailto:hi@sitepins.com) ![](/_astro/pinpoint.CVFS4btZ.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) Address 5/2, Road No. 1, Shyamoli, Dhaka-1207 Your Name \* Email \* Subject \* Write Message \* Send Message ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Git-based Headless CMS for Hugo URL: https://sitepins.com/hugo-cms Sitepins gives your non technical clients and teammates a visual editor to manage content on Hugo Hugo CMS # Git-based Headless CMS for Hugo Sitepins gives your non technical clients and teammates a visual editor to manage content on Hugo. [Sign up for FREE ](https://sitepins.com/pricing) No credit card required. Free tier forever. ![sitepins cms nextjs](/_vercel/image?url=_astro%2Fcode-editor.CPXDpsp8.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![sitepins cms nextjs](/_vercel/image?url=_astro%2Fsitepins-landing.DmBPf6R4.png&w=1920&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![](/_vercel/image?url=_astro%2Four_story_bg.4SkuIFY4.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) How it Works ## Connect. Configure. Start Editing. Everything within minutes ![Connect Repo](/_astro/project-setup.0okJdjMy.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Connect Repo Connect your Git repository once. Sitepins automatically detects your Hugo content structure. ![Configure](/_astro/project-configure.Cq3OqEdc.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Configure Sitepins automatically reads your Content files (Markdown, TOML, YAML, JSON) and presents them as structured forms. ![Start Editing](/_astro/project-edit.BD4QGJqy.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Start Editing Your team can start editing immediately. Every save is a traceable Git commit, ready for your Hugo build. FOR EDITORS ## Content Management Streamlined. A user friendly visual interface to manage your content, while ensuring your Hugo site's speed and integrity. ### Empower your content team - Edit content using a visual editor. No coding or technical knowledge required. - Easily update metadata, tags, dates, and SEO configurations. Content updates commit instantly to Git, allowing publishing without developer help. - Manage media assets easily with a focused library using the drag-and-drop feature. ![sitepins cms hugo visual editor](/_vercel/image?url=_astro%2Fcms-editor.ogjQw1_r.png&w=828&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) FOR DEVELOPERS ## Preserves Hugo’s code, Speed and Integrity. Hand off site to clients with ease. Editors use simple visual tools to refresh content, keeping your Hugo code untouched and uninterrupted. ### Streamline your Dev workflow - Hand off sites with ease, moving content updates out of the code for your non-technical clients. - Content is written as static files, preserving Hugo's architecture and guaranteeing its famous lightning-fast build times. - Every change made by an editor is a standard Git commit, ensuring a full audit trail and easy rollback capability. ![sitepins cms hugo visual editor](/_vercel/image?url=_astro%2Fhugo-cms.BqKK918x.png&w=828&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Key Features ## Features That Make Content Editing Effortless Everything your teammates or clients need to update content without touching code. ### Easy Setup No complicated setup. register, connect your repo, and you’re ready to go — even if you’ve never used a CMS before. ![Quick and Easy Setup](/_vercel/image?url=_astro%2Feasy-setup.DESJijM5.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Stay in control with Git Every edit is versioned, trackable, and reversible. You’ll always know who changed what. ![Git Integration in Sitepins](/_vercel/image?url=_astro%2Fgit-workflow.IAwiiopi.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Edit visually Update text, images, and content directly in the editor. No more back-and-forth with developers for small changes. ![Visual Markdown Editor](/_vercel/image?url=_astro%2Fwysiwyg-editor.CFWYt7f-.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Live Preview See your changes instantly in a sandbox preview without rebuilding the site. Your edits update in real time so you can verify content before publishing. ![Live Preview Sandbox](/_vercel/image?url=_astro%2Flivepreview.CClywa_3.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Keep media organized effortlessly Drag, drop, and reuse images right inside the CMS. ![Manage Media Files Easily](/_vercel/image?url=_astro%2Fmedia-management.D6KlzgEG.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Works with your favorite stack Sitepins supports Astro, Next.js, Hugo, and other leading static site generators. ![All Static Site Generators Support](/_vercel/image?url=_astro%2Fssg-support.CTABSsRp.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Support Shortcodes Easily manage shortcodes and custom content blocks for powerful content structuring. Save time and stay consistent. ![Shortcode Editing in CMS](/_vercel/image?url=_astro%2Fshortcode.dkOCMW9K.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Collaborate with your team safely Manage roles, permissions, and access for multiple users. Live presence indicators show exactly who is working and where ![User Roles and Permission Management](/_vercel/image?url=_astro%2Fpermission.B9HaNGsC.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Keep Complex Content Organized Maintain a clean content hierarchy, even for large sites — everything stays easy to find, edit, and manage visually. ![Nested Content Collections](/_vercel/image?url=_astro%2Fnested-collection.CU4iK8uC.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Compatible with all popular file formats Sitepins works with Markdown, JSON, YAML, and TOML — whatever your static site uses. ![Multi-format Content Support](/_vercel/image?url=_astro%2Ffiles-support.DPZJCI79.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Native Language Support Sitepins supports 12 (en, zh, ja, de, fr, es, pt, ru, ko, id, vi, bn) languages natively for a seamless, consistent, and localized experience. ![Native Translation Support](/_vercel/image?url=_astro%2Fmultilingual.D2aDITfI.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### AI Assistant Plug in your own API key (OpenAI, Gemini, Claude, Grok) to generate or rewrite contents inside the editor. ![AI Content Assistant](/_vercel/image?url=_astro%2Fai-assistant.BTrX11pe.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Free Templates ## Start With a Free Template Launch your Hugo project faster with our pre-configured starters. ![Hugoplate](https://assets.teamosis.com/thumbs/hugoplate.png) ### Hugoplate hugoblog [Get Start For Free](https://app.sitepins.com/new/clone?name=Hugoplate&repository=https://github.com/zeon-studio/hugoplate) ![Geeky Hugo](https://assets.teamosis.com/thumbs/geeky.png) ### Geeky Hugo hugoblog [Get Start For Free]() ![Hydrogen Hugo](https://assets.teamosis.com/thumbs/hydrogen.png) ### Hydrogen Hugo hugoblog [Get Start For Free]() ![Minilog Hugo](https://assets.teamosis.com/thumbs/minilog.png) ### Minilog Hugo hugoblog [Get Start For Free]() ![Iwriter Hugo](https://assets.teamosis.com/thumbs/iwriter.png) ### Iwriter Hugo hugoblog [Get Start For Free]() ![Bookworm Light Hugo](https://assets.teamosis.com/thumbs/bookworm-light.png) ### Bookworm Light Hugo hugoblog [Get Start For Free]() [View All Templates ](https://app.sitepins.com/templates) > I've worked with almost every headless CMS out there. Sitepins is by far the best. Handing projects off to non-technical clients has never been smoother. All my Astro themes now come pre-configured with Sitepins and it's the default CMS for my clients' projects too. ### Christos Founder & Lead Designer, Oxygenna > I wanted to give our marketing team the ability to edit content without them poking me every time. So far, it’s going well. I can finally focus on more complex tasks rather than just changing a heading or triggering a rebuild. ### Somrat Developer Team Lead > I absolutely love the UI and the experience of working with it. The configuration and set-up was simple, smooth and easy. ### Emmanuel Chief Technical Officer > Sitepins looks pretty sweet. Great job. It’s just what I’ve been looking for. ### Jim Mitchell Developer and Tech Blogger > Sitepins looks really nice, it's just what I hoped to find. ### Joakim Freelance Developer ![Christos](/_vercel/image?url=_astro%2Fchirstos.DV2Y3f2T.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Somrat](/_vercel/image?url=_astro%2FSomrat.BwganZp8.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Emmanuel ](/_vercel/image?url=_astro%2FEmmanuel.Bsrg7jKY.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Jim Mitchell](/_vercel/image?url=_astro%2FJim-Mitchell.Dg26QtN6.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Joakim](/_vercel/image?url=_astro%2FJoakim.XmZu6oLf.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Join the teams simplifying content editing with Sitepins. ![Themefisher](/_astro/themefisher.DdObPKXZ.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![GetHugoThemes](/_astro/gethugothemes.D4jOwvUz.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Statichunt](/_astro/statichunt.ogDzivN2.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Uihut](/_astro/uihut.DNlBUx8T.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Zeon Studio](/_astro/zeon-studio.Bn2Zoq8x.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Supernova](/_astro/supernova.DXiL8Uo6.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) FAQs ## Frequent Questions Got questions? We’ve got clear answers to help you get started. Why add Sitepins CMS to Hugo? How do I turn on the AI Assistant? Do I need to install anything to use Sitepins? Can use Sitepins for free? Have more question? [Contact Us](contact) to inquire more! ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Connect to useful tools URL: https://sitepins.com/integration Sign back into your account to retrieve all your information. Integrations # Connect to useful tools Sign back into your account to retrieve all your information. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Astro](/_astro/astro.B0kbbGDX.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Astro Astro powers the world's fastest marketing sites, blogs, e-commerce websites, and more. ![Next.js](/_astro/nextjs.r9RVkKBW.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Nextjs Next.js by Vercel is the full-stack React framework designed for building modern web applications. ![hugo](/_astro/hugo.sguaXCtV.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Hugo Hugo is one of the most popular open-source static site generators. with its amazing speed & flexibility. ### Nuxt.js Nuxt is an open source framework that makes web development intuitive and powerful. ![svelte](/_astro/svelte.cTaBEOoE.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Svelte Svelte is a UI framework that uses a compiler to let you write concise components that do minimal work. ![11ty](/_astro/11ty.U9TRdOsx.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### 11ty Eleventy, also known as 11ty, is a static site generator. It was written in Javascript.  ![jkyll](/_astro/jkyll.DXe2lFgk.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Jekyll Jekyll is a simple, blog-aware, static site generator that transforms your plain text into websites and blogs. ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Git-based Headless CMS for Next.js URL: https://sitepins.com/nextjs-cms Sitepins gives your non technical clients and teammates a visual editor to manage content on Nextjs Nextjs CMS # Git-based Headless CMS for Next.js Sitepins gives your non technical clients and teammates a visual editor to manage content on Nextjs. [Sign up for FREE ](https://sitepins.com/pricing) No credit card required. Free tier forever. ![sitepins cms nextjs](/_vercel/image?url=_astro%2Fcode-editor.CPXDpsp8.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![sitepins cms nextjs](/_vercel/image?url=_astro%2Fsitepins-landing.DmBPf6R4.png&w=1920&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![](/_vercel/image?url=_astro%2Four_story_bg.4SkuIFY4.png&w=1200&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) How it Works ## Connect. Configure. Start Editing. Everything within minutes ![Connect Repo](/_astro/project-setup.0okJdjMy.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Connect Repo Connect your Git repository once. Sitepins automatically detects your Next.js content structure. ![Configure](/_astro/project-configure.Cq3OqEdc.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Configure Sitepins automatically reads your content files (Markdown, MDX, JSON) and presents them as structured editing forms ![Start Editing](/_astro/project-edit.BD4QGJqy.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Start Editing Your team can start editing immediately. Every save is a traceable Git commit, ready for your Next.js build. FOR EDITORS ## Simple Visual Editor Manage and update your Next.js site contents through a visual editor—no coding or technical knowledge required. ### Empower your Content Team - Edit content using a visual editor. No coding or technical knowledge required. - Easily update metadata, tags, dates, and SEO configurations and publish without developer help. - Manage media assets easily with a focused library using the drag-and-drop feature. ![sitepins cms nextjs visual editor](/_vercel/image?url=_astro%2Fcms-editor.ogjQw1_r.png&w=828&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) FOR DEVELOPERS ## Preserves Next.js code, Speed and Integrity. Hand off your site to clients with ease. Editors use a simple visual tool, keeping your Next.js code clean and uninterrupted. ### Streamline Your Dev Workflow - Hand off sites with ease, moving content updates out of the code for your non-technical clients. - Supports editing JSON and YAML files, allowing editors to update the data and props that power your React components. - Your content remains committed to your repo, ensuring full ownership, version control, and zero dependency on a proprietary database. ![sitepins cms nextjs visual editor](/_vercel/image?url=_astro%2Fnextjs-cms.C4XlgVYo.png&w=828&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Key Features ## Features That Make Content Editing Effortless Everything your teammates or clients need to update content without touching code. ### Easy Setup No complicated setup. register, connect your repo, and you’re ready to go — even if you’ve never used a CMS before. ![Quick and Easy Setup](/_vercel/image?url=_astro%2Feasy-setup.DESJijM5.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Stay in control with Git Every edit is versioned, trackable, and reversible. You’ll always know who changed what. ![Git Integration in Sitepins](/_vercel/image?url=_astro%2Fgit-workflow.IAwiiopi.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Edit visually Update text, images, and content directly in the editor. No more back-and-forth with developers for small changes. ![Visual Markdown Editor](/_vercel/image?url=_astro%2Fwysiwyg-editor.CFWYt7f-.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Live Preview See your changes instantly in a sandbox preview without rebuilding the site. Your edits update in real time so you can verify content before publishing. ![Live Preview Sandbox](/_vercel/image?url=_astro%2Flivepreview.CClywa_3.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Keep media organized effortlessly Drag, drop, and reuse images right inside the CMS. ![Manage Media Files Easily](/_vercel/image?url=_astro%2Fmedia-management.D6KlzgEG.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Works with your favorite stack Sitepins supports Astro, Next.js, Hugo, and other leading static site generators. ![All Static Site Generators Support](/_vercel/image?url=_astro%2Fssg-support.CTABSsRp.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Support Shortcodes Easily manage shortcodes and custom content blocks for powerful content structuring. Save time and stay consistent. ![Shortcode Editing in CMS](/_vercel/image?url=_astro%2Fshortcode.dkOCMW9K.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Collaborate with your team safely Manage roles, permissions, and access for multiple users. Live presence indicators show exactly who is working and where ![User Roles and Permission Management](/_vercel/image?url=_astro%2Fpermission.B9HaNGsC.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Keep Complex Content Organized Maintain a clean content hierarchy, even for large sites — everything stays easy to find, edit, and manage visually. ![Nested Content Collections](/_vercel/image?url=_astro%2Fnested-collection.CU4iK8uC.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Compatible with all popular file formats Sitepins works with Markdown, JSON, YAML, and TOML — whatever your static site uses. ![Multi-format Content Support](/_vercel/image?url=_astro%2Ffiles-support.DPZJCI79.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### Native Language Support Sitepins supports 12 (en, zh, ja, de, fr, es, pt, ru, ko, id, vi, bn) languages natively for a seamless, consistent, and localized experience. ![Native Translation Support](/_vercel/image?url=_astro%2Fmultilingual.D2aDITfI.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ### AI Assistant Plug in your own API key (OpenAI, Gemini, Claude, Grok) to generate or rewrite contents inside the editor. ![AI Content Assistant](/_vercel/image?url=_astro%2Fai-assistant.BTrX11pe.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Free Templates ## Start With a Template Launch your Next.js project faster with our pre-configured starters. ![Nextplate](https://assets.teamosis.com/thumbs/nextplate.png) ### Nextplate nextjsblog [Get Start For Free](https://app.sitepins.com/new/clone?name=Nextplate&repository=https://github.com/zeon-studio/nextplate) ![Geeky Nextjs](https://assets.teamosis.com/thumbs/geeky.png) ### Geeky Nextjs nextjsblog [Get Start For Free]() ![Hydrogen Nextjs](https://assets.teamosis.com/thumbs/hydrogen.png) ### Hydrogen Nextjs nextjsblog [Get Start For Free]() ![Techfeed Nextjs](https://assets.teamosis.com/thumbs/techfeed.png) ### Techfeed Nextjs nextjsblog [Get Start For Free]() ![Andromeda Light Nextjs](https://assets.teamosis.com/thumbs/andromeda-light.png) ### Andromeda Light Nextjs nextjssaas [Get Start For Free]() ![Bigspring Light Nextjs](https://assets.teamosis.com/thumbs/bigspring-light.png) ### Bigspring Light Nextjs nextjssaas [Get Start For Free]() [View All Templates ](https://app.sitepins.com/templates) > I've worked with almost every headless CMS out there. Sitepins is by far the best. Handing projects off to non-technical clients has never been smoother. All my Astro themes now come pre-configured with Sitepins and it's the default CMS for my clients' projects too. ### Christos Founder & Lead Designer, Oxygenna > I wanted to give our marketing team the ability to edit content without them poking me every time. So far, it’s going well. I can finally focus on more complex tasks rather than just changing a heading or triggering a rebuild. ### Somrat Developer Team Lead > I absolutely love the UI and the experience of working with it. The configuration and set-up was simple, smooth and easy. ### Emmanuel Chief Technical Officer > Sitepins looks pretty sweet. Great job. It’s just what I’ve been looking for. ### Jim Mitchell Developer and Tech Blogger > Sitepins looks really nice, it's just what I hoped to find. ### Joakim Freelance Developer ![Christos](/_vercel/image?url=_astro%2Fchirstos.DV2Y3f2T.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Somrat](/_vercel/image?url=_astro%2FSomrat.BwganZp8.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Emmanuel ](/_vercel/image?url=_astro%2FEmmanuel.Bsrg7jKY.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Jim Mitchell](/_vercel/image?url=_astro%2FJim-Mitchell.Dg26QtN6.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Joakim](/_vercel/image?url=_astro%2FJoakim.XmZu6oLf.png&w=640&q=80&dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Join the teams simplifying content editing with Sitepins. ![Themefisher](/_astro/themefisher.DdObPKXZ.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![GetHugoThemes](/_astro/gethugothemes.D4jOwvUz.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Statichunt](/_astro/statichunt.ogDzivN2.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Uihut](/_astro/uihut.DNlBUx8T.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Zeon Studio](/_astro/zeon-studio.Bn2Zoq8x.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) ![Supernova](/_astro/supernova.DXiL8Uo6.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) FAQs ## Frequent Questions Got questions? We’ve got clear answers to help you get started. Why use Sitepins with Next.js? How do I turn on the AI Assistant? Do I need to install anything to use Sitepins? Can use Sitepins for free? Have more question? [Contact Us](contact) to inquire more! ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Frequent Questions URL: https://sitepins.com/pricing Choose a plan that fits your needs. Change or upgrade anytime. Hobby For Hobby & Personal Projects Free/forever [Use for Free](https://app.sitepins.com/register) No credit card required • 15 days Pro trial Show all features - 3 sites (1 private repo) - 1 Organization - Media Management - 1 User (1 Role) - No-code Setup - Activity Log - Rich Text Editor - Raw Markdown Editor - Configurations Management - Github Repositories - Dark Mode - Community Support MonthlyYearlyUp to 18% OffLifetimeEarly Bird Deal Pro ### $12 /month For Individuals [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dpro%26billing%3Dmonthly) ### Everything in Hobby, plus - 6 sites (Public + Private Repo) - 2 Organizations - 3 Users per organization - 3 Roles - SEO Suggestions - Multiple Branch Management - AI Assistant - Preview Sandbox - Raw Code Edit - Sidebar Arrangement - Code Snippet Support - Custom Commit Messages - Deployment Status - Rollback Previous Version - Premium Support ![featured icon](/_astro/gradient_star.Cc7UPRnR.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)Team ### $29 /month For Teams [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dteam%26billing%3Dmonthly) ### Everything in Pro, plus - 15 sites (Public + Private Repo) - 5 Organizations - 5 Users per organization - Support Github + GitLab Repositories - Advanced SEO Suggestions - Premium Support Agency ### $49 /month For Agencies [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dagency%26billing%3Dmonthly) ### Everything in Team, plus - 30 sites (Public + Private Repo) - 10 Organizations - 5 Users per organization - Dedicated Support Need more? Unlimited sites, organizations, and users. [Contact us for Enterprise](/contact) Pro ### $10 /month (billed yearly) For Individuals [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dpro%26billing%3Dannually) ### Everything in Hobby, plus - 6 sites (Public + Private Repo) - 2 Organizations - 3 Users per organization - 3 Roles - SEO Suggestions - Multiple Branch Management - AI Assistant - Preview Sandbox - Raw Code Edit - Sidebar Arrangement - Code Snippet Support - Custom Commit Messages - Deployment Status - Rollback Previous Version - Premium Support ![featured icon](/_astro/gradient_star.Cc7UPRnR.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)Team ### $24 /month (billed yearly) For Teams [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dteam%26billing%3Dannually) ### Everything in Pro, plus - 15 sites (Public + Private Repo) - 5 Organizations - 5 Users per organization - Support Github + GitLab Repositories - Advanced SEO Suggestions - Premium Support Agency ### $40 /month (billed yearly) For Agencies [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dagency%26billing%3Dannually) ### Everything in Team, plus - 30 sites (Public + Private Repo) - 10 Organizations - 5 Users per organization - Dedicated Support Need more? Unlimited sites, organizations, and users. [Contact us for Enterprise](/contact) Pro ### $249 /lifetime access One-time payment. Lifetime access. No recurring fees. [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dpro%26billing%3Dlifetime) ### Everything in Hobby, plus - 6 sites (Public + Private Repo) - 2 Organizations - 3 Users per organization - 3 Roles - SEO Suggestions - Multiple Branch Management - AI Assistant - Preview Sandbox - Raw Code Edit - Sidebar Arrangement - Code Snippet Support - Custom Commit Messages - Deployment Status - Rollback Previous Version - Premium Support ![featured icon](/_astro/gradient_star.Cc7UPRnR.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg)Team ### $519 /lifetime access One-time payment. Lifetime access. No recurring fees. [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dteam%26billing%3Dlifetime) ### Everything in Pro, plus - 15 sites (Public + Private Repo) - 5 Organizations - 5 Users per organization - Support Github + GitLab Repositories - Advanced SEO Suggestions - Premium Support Agency ### $729 /lifetime access One-time payment. Lifetime access. No recurring fees. [Upgrade Now](https://app.sitepins.com/register?from=%2Fcheckout%3Fplan%3Dagency%26billing%3Dlifetime) ### Everything in Team, plus - 30 sites (Public + Private Repo) - 10 Organizations - 5 Users per organization - Dedicated Support Need more? Unlimited sites, organizations, and users. [Contact us for Enterprise](/contact) FAQs ## Frequent Questions Got questions? We’ve got clear answers to help you get started. What is Sitepins? What is a Git-based CMS? Do I need to install anything to use Sitepins? Have more question? [Contact Us](contact) to inquire more! ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Privacy Policies URL: https://sitepins.com/privacy-policy Sitepins privacy policy # Privacy Policies Sitepins privacy policy ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) Sitepins (“we”, “our”, or “us”) values your privacy. This Privacy Policy explains how we collect, use, and share your information when you use our website and services. ### 1\. Who We Are - **Legal Name:** Sitepins - **Address:** 5/2, Road No. 1, Shyamoli, Dhaka-1207, Bangladesh - **Email:** [hi@sitepins.com](mailto:hi@sitepins.com) ### 2\. Information We Collect We collect personal and non-personal data including: - Name and email address (e.g., for account creation or waitlists) - Billing information via our payment processor (Paddle) - Usage data through cookies and analytics tools ### 3\. How We Use Your Information We use your data to: - Provide and improve our services - Process payments - Communicate with you (e.g. marketing emails,through newsletters, special offers or announcements.) - Monitor usage and fix issues - Comply with legal obligations ### 4\. Cookies and Tracking We use cookies and similar technologies to: - Understand how users interact with our website - Improve user experience - Run analytics (e.g., Google Analytics) You can control cookie usage through your browser settings. ### 5\. Data Sharing We may share data with: - Payment processors (e.g., Paddle) - Email service providers - Analytics services - Legal authorities, if required by law We do not sell your personal data. ### 6\. Data Retention and Deletion You may request account or data deletion at any time by contacting us at [hi@sitepins.com](mailto:hi@sitepins.com). ### 7\. Your Rights Depending on your jurisdiction, you may have rights such as: - Access to your personal data - Correction of inaccurate data - Deletion of your data - Withdrawal of consent We are working towards full GDPR compliance. If you have a request, email us. ### 8\. Security We take reasonable measures to protect your information, but no system is 100% secure. ### 9\. Children’s Privacy Our service is not intended for users under the age of 13. If you believe we’ve collected data from a minor, contact us to have it removed. ### 10\. Changes to This Policy We may update this Privacy Policy from time to time. Continued use of Sitepins means acceptance of changes. **Effective Date:** June 23, 2025 --- ## Sites that use Sitepins CMS. URL: https://sitepins.com/showcase A selection of real websites managed with Sitepins CMS. Showcase # Sites that use Sitepins CMS. A selection of real websites managed with Sitepins CMS. ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Themefisher [](https://themefisher.com) Themefisher is a global marketplace providing high-quality, free, and premium website templates and themes designed for modern web technologies. Built With: - ![nextjs](/images/icons/technologies/nextjs.svg) ![Themefisher](/_vercel/image?url=_astro%2Fthemefisher.Cc6rB6o-.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Gethugothemes [](https://gethugothemes.com) Gethugothemes is a specialized platform that provides high-quality, pre-built Hugo templates and modules designed for building fast, SEO-friendly static websites. Built With: - ![nextjs](/images/icons/technologies/nextjs.svg) ![Gethugothemes](/_vercel/image?url=_astro%2Fgethugothemes.D7kEqMRg.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Statichunt [](https://statichunt.com) Statichunt is an open-source directory featuring over 7,800 themes, starters, and tools for modern web development frameworks like Astro, Next.js, and Hugo Built With: - ![nextjs](/images/icons/technologies/nextjs.svg) ![Statichunt](/_vercel/image?url=_astro%2Fstatichunt.Cpvhjasv.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Zeon Studio [](https://zeon.studio) Zeon Studio is a modern web design and development agency. They build fast, structured websites using Astro, Next.js, and Hugo, paired with headless CMS. Built With: - ![nextjs](/images/icons/technologies/nextjs.svg) ![Zeon Studio](/_vercel/image?url=_astro%2Fzeon-studio.BgmKmwAc.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### 1Supernova [](https://1supernova.com) Supernova is an investment and advisory network featuring over 250 exited founders who provide capital and operational support to startups, focusing on accelerating growth. Built With: - ![nextjs](/images/icons/technologies/nextjs.svg) ![1Supernova](/_vercel/image?url=_astro%2F1supernova.CnIpwAAY.webp&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ### Eliza.swiss [](https://eliza.swiss) ELIZA is a Swiss-based cloud software solution designed for digital quality management, process management, and HR administration. Built With: - ![hugo](/images/icons/technologies/hugo.svg) ![Eliza.swiss](/_vercel/image?url=_astro%2Feliza.NnhJLTwS.webp&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) > I've worked with almost every headless CMS out there. Sitepins is by far the best. Handing projects off to non-technical clients has never been smoother. All my Astro themes now come pre-configured with Sitepins and it's the default CMS for my clients' projects too. ### Christos Founder & Lead Designer, Oxygenna > I wanted to give our marketing team the ability to edit content without them poking me every time. So far, it’s going well. I can finally focus on more complex tasks rather than just changing a heading or triggering a rebuild. ### Somrat Developer Team Lead > I absolutely love the UI and the experience of working with it. The configuration and set-up was simple, smooth and easy. ### Emmanuel Chief Technical Officer > Sitepins looks pretty sweet. Great job. It’s just what I’ve been looking for. ### Jim Mitchell Developer and Tech Blogger > Sitepins looks really nice, it's just what I hoped to find. ### Joakim Freelance Developer ![Christos](/_vercel/image?url=_astro%2Fchirstos.DV2Y3f2T.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Somrat](/_vercel/image?url=_astro%2FSomrat.BwganZp8.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Emmanuel ](/_vercel/image?url=_astro%2FEmmanuel.Bsrg7jKY.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Jim Mitchell](/_vercel/image?url=_astro%2FJim-Mitchell.Dg26QtN6.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ![Joakim](/_vercel/image?url=_astro%2FJoakim.XmZu6oLf.png&w=640&q=80&dpl=dpl_HfKSEJC6FcgWhpQa6s247RLF8UEg) ## Get Started with Sitepins Get started for free today and discover easy, flexible, and full control over your content. [Try for Free ](/pricing?ref=cta) --- ## Terms and Conditions URL: https://sitepins.com/terms Sitepins terms and conditions # Terms and Conditions Sitepins terms and conditions ![](/_astro/ph_grids.DwgUyOzm.svg?dpl=dpl_5kXkVqDmdNKvB74xswdPoarBVPaY) By using Sitepins, you agree to these Terms of Service (“Terms”). If you do not agree, please do not use our services. ### 1\. Overview Sitepins is a cloud-hosted git-based headless CMS designed to help developers and teams manage content efficiently. ### 2\. Account Terms - You must be at least 13 years old to use Sitepins. - You are responsible for maintaining the security of your account. - You must provide accurate and complete information. ### 3\. Acceptable Use You agree not to: - Use Sitepins for any unlawful purpose - Interfere with or disrupt our systems - Try to gain unauthorized access to other users’ accounts We reserve the right to suspend or terminate accounts that violate these rules. ### 4\. Payment & Refunds - Payments are processed via **Paddle**. - You agree to pay all applicable fees associated with your plan. - We offer refunds under reasonable circumstances. Please contact us at [hi@sitepins.com](mailto:hi@sitepins.com). ### 5\. Intellectual Property All content, trademarks, logos, and software related to Sitepins are our property or used with permission. You may not reproduce or redistribute them without our consent. ### 6\. Limitation of Liability We provide Sitepins “as is.” While we strive for high uptime and quality, we’re not liable for: - Data loss - Downtime - Errors or bugs - Indirect or consequential damages Use at your own risk. ### 7\. Termination You may stop using Sitepins at any time. We reserve the right to suspend or terminate your access for violations of these Terms. ### 8\. Governing Law These Terms are governed by the laws of the State of Texas, USA. ### 9\. Contact For any questions, reach out to us at [hi@sitepins.com](mailto:hi@sitepins.com). ### 10\. Changes to This Terms We may update this terms from time to time. Continued use of Sitepins means acceptance of changes. **Effective Date:** June 23, 2025