Ycode

What is Ycode?

Ycode is an open source website builder and CMS that lets you design, host, and update custom website content using a visual interface. Its core purpose is to give you a workflow similar to modern website builders while keeping control through open source and support for self-hosting.

You can use Ycode in a managed form via Ycode Cloud or run it on your own infrastructure by deploying the open source code and connecting your backend services.

Key Features

• Visual website builder and CMS in a single platform, so you can build pages and manage content from one workflow.
• Open source code access for self-hosting, including the ability to “fork the repo” and deploy it to your own environment.
• Self-hosting path that includes deploying to Vercel and connecting Supabase to start building.
• Cloud option (Ycode Cloud) described as fully managed, with automatic updates and maintenance.
• Domains and form/page/content capabilities shown in pricing tiers, including unlimited (self-host) or capped (cloud) items like CMS items and form entries.
• Release updates that add CMS capabilities such as collection filtering with pagination and dynamic sorting, plus rich-text editor improvements.

How to Use Ycode

1. Choose your setup: start with Ycode Cloud for a managed option or self-host the open source project.
2. If you self-host, fork the Ycode repository on GitHub and deploy it to Vercel.
3. Connect Supabase to your deployed project to enable building and content workflows.
4. In either setup, use the visual builder to create your website and update CMS-driven content.

Use Cases

• Migrating from another CMS or builder by rebuilding the website and then switching content management with minimal involvement from an IT department (as described by a user review).
• Building a small-to-medium custom site where you want a visual editor plus CMS features (pages, unlimited pages/forms/items in self-host) without being locked into a closed platform.
• Managing dynamic content lists using CMS features such as collection filtering with pagination and dynamic sorting (introduced in a recent release).
• Setting up a team workflow where designers and builders collaborate on website content using the community and release updates.
• Running a production website with either managed hosting (Ycode Cloud) or full control through self-hosting on your own infrastructure.

FAQ

• Is Ycode open source? Yes. The site describes Ycode as an open source website builder and CMS and provides an “Open in Github” link.
• Can I use Ycode without self-hosting? Yes. Ycode Cloud is presented as a fully managed option, described as providing automatic updates and maintenance.
• What do I need to self-host Ycode? The provided setup flow mentions forking the repository, deploying to Vercel, and connecting Supabase.
• What kind of CMS functionality does Ycode support? The release notes mention collection filtering with pagination, dynamic sorting, and rich-text editor improvements.
• What hosting and content limits apply? The page shows different limits in the pricing section for self-hosting versus Ycode Cloud (for example, “Unlimited” items on self-host and capped CMS items on cloud), but the exact values are only partially shown for cloud in the provided text.

Alternatives

• Closed-source visual website builders: These are typically easier to start with but often keep your content and infrastructure within the vendor’s ecosystem, which Ycode positions against by emphasizing open source control.
• Headless or hosted CMS platforms with a separate frontend: If you want strong CMS features but prefer a custom frontend workflow, a CMS-first approach can separate content management from the visual page builder.
• General no-code site builders: These tools focus on visual design and publishing, though they may differ in how much code access and self-hosting flexibility they offer.
• Self-hostable CMS-driven website stacks: A self-hosted CMS plus a frontend framework approach can provide control similar to Ycode’s self-host option, but with more setup compared to a unified visual builder + CMS workflow.