No database anywhere in the stack: Grav, the leading flat-file CMS, builds every page from a folder of Markdown and YAML on PHP, Symfony components, Twig templating, and Doctrine caching. That architecture is the whole argument: content is Git-versionable, rsync-able, and lock-in-free; pages render in well under 100ms without database round-trips; and backup means copying a directory. Content authors write Markdown (or plain HTML), configure with readable YAML, and define custom page structures via blueprint files that generate editing forms automatically. The optional Admin panel adds a polished editing layer: dashboard with site activity, page management with a syntax-highlighted editor and live preview, drag-and-drop media uploads, one-click plugin/theme updates, and normal/expert modes for form-based or raw YAML editing. The ecosystem runs deep - hundreds of open-source plugins and themes installed through the GPM package manager, with an event-hook architecture that gives plugins full control over the request lifecycle, and downloadable skeletons providing entire pre-built sites. Grav 2.0 modernizes the stack (PHP 8.3+, Symfony 7, Twig 3) and adds a first-party REST API, an MCP server for AI agents, and a SvelteKit single-page admin with real-time collaborative editing. Ideal for docs, blogs, and marketing sites. MIT-licensed.

Documentation deserves better than a database nobody wants to maintain. Typemill is an open-source flat-file CMS for informational websites, manuals, knowledge bases, and handbooks: content lives as Markdown files in folders, so a site can be copied, versioned, backed up, and moved with ordinary file tools and no database server anywhere in the stack. Authors get a visual block editor for nontechnical writing and a raw Markdown editor when precision matters, with a navigation tree, drag-and-drop structure, media library, page metadata, and publish states in one workspace. The same source then publishes three ways: as a themed website, as a printable PDF manual, or as an EPUB eBook through the eBook studio, making single-source publishing real for teams tired of maintaining docs, PDFs, and handbooks as three diverging copies. Themes are built from HTML and Twig; plugins add search, analytics, diagrams, math, and integrations; and an optional AI assistant interface connects writing help to the editor. User management, restricted pages, redirects, and a REST API cover the operational side, and the whole application is small enough to run comfortably on modest shared-style hosting or a tiny server while still feeling instant. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Bludit is a flat-file content management system that runs your website or blog from plain JSON files, giving you a complete admin panel and publishing workflow with no database anywhere in the stack. Writing feels familiar whichever way you work: draft posts and pages in the Markdown editor, switch to the WYSIWYG editor when you want to see the page as you build it, or drop into HTML for exact control. Cover images, galleries, and uploads live in the media manager, and categories and tags keep a growing archive browsable. Built-in SEO tools handle titles, meta descriptions, and friendly URLs, so pages come out ready for search engines and social previews without another plugin hunt. When the look needs to change, the official theme directory restyles the whole site from the admin area, and the plugin directory adds galleries, contact forms, and analytics the same way. Moving day is a copy command: the entire site, content and settings included, is a folder of files you can duplicate, back up, or carry to another server. Because every page renders from files with no database round trips, modest hardware serves pages quickly. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Write your knowledge as plain Markdown files, and WikiDocs turns the folder into a searchable, versioned wiki with no database to set up or back up. Pages carry YAML front matter, so the whole wiki can be copied, archived, or opened in any text editor. An editor with a formatting toolbar handles headings, lists, task lists, links, and images, and pictures can be pasted straight from the clipboard. Math is typeset with KaTeX, Mermaid renders diagrams such as ER models and mind maps, and code blocks get syntax highlighting. Every save keeps a revision, a versions dialog lists them, and deleted pages wait in a trash where they can be restored or erased. Attachments upload and download from any page, namespaces build a page tree in the sidebar with pinned pages on top, and full-text search highlights every match. Public mode publishes a read-only knowledge base, private mode requires sign-in, and administrator and user accounts are managed in the app. Settings cover the wiki title, owner notice, privacy banner, language, timezone, light or dark template, and accent color, and every page has a print button. A desktop app keeps files on your computer and syncs with your self-hosted instance, while a REST API with Swagger documentation lets other tools read and write pages. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Every page in a DokuWiki knowledge base is just a plain text file on disk, so a team wiki can run for years on modest hardware with no database to feed, ever. Writers edit pages in a clean, readable syntax, fix just one section of a long document at a time, and lean on the toolbar, breadcrumbs, automatic tables of contents, and conflict locking to keep collaboration painless. Every change is kept as a revision with colored side-by-side diffs, recent-changes feeds go out over RSS, and an index-based full-text search finds content across thousands of pages in milliseconds. Namespaces organize content into a browsable tree, while built-in access control lists decide per page or per branch who may read, edit, upload, or administer, with logins checked against LDAP and other backends. Media uploads embed straight into pages, configuration happens in the browser, and the whole installation backs up by copying a folder, which makes migrations and disaster recovery almost boringly simple. When the basics stop being enough, more than twelve hundred community plugins and a hundred templates add galleries, multilingual structures, diagrams, and data tables without changing how the wiki itself works. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-2.0 licensed.

Team and product documentation on a fast Vue frontend with PostgreSQL storage: Wiki.js is a Node.js wiki engine. Its distinguishing trait is per-page editor choice: authors pick Markdown with live preview, a WYSIWYG visual builder for non-technical writers, or raw HTML, page by page. Native Git synchronization commits every page change to GitHub, GitLab, Bitbucket, Azure DevOps, or any Git remote - bi-directionally, so edits made in the repository flow back into the wiki - giving documentation version-controlled backup for free. Authentication coverage is among the broadest of any self-hosted wiki: local accounts with self-registration, social login via Google, GitHub, Discord, and Slack, and enterprise SSO through LDAP/Active Directory, SAML, CAS, Auth0, Okta, Azure AD, Keycloak, and generic OAuth2/OIDC, with optional MFA. Built-in full-text search runs on PostgreSQL with zero setup, and external engines like Algolia or Solr can substitute. Page history with visual version comparison, granular group-based permissions per path, nested navigation menus, 50+ integration modules, and full localization round it out. AGPLv3-licensed with a 28k-star community.

Knowledge scattered across chat threads, tickets, and shared drives gets one permanent, searchable home in JSPWiki, a wiki engine that any team member can edit from the browser. Pages can be written in classic JSPWiki markup or in Markdown, and new syntaxes plug in alongside. Every page carries its own history through the versioning file provider, so edits can be compared and rolled back, and page locking keeps two editors from colliding. Files attach directly to pages, templates restyle the whole wiki, and three interchangeable search providers, including full-text indexing, make old decisions findable again. Access stays precise: authentication and per-page access control lists decide who can view or edit each page, which suits mixed audiences of staff, partners, and the public. Plugins and page filters extend rendering with dynamic content, and one installation can host multiple separate wikis for different teams. Readers get custom preferences and internationalized interfaces. Run it as a WAR on Tomcat or pull the Docker image and open port 8080. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. Apache License 2.0 licensed.

The entire wiki - content, code, and interface - is built from "tiddlers," small addressable units of information that link, transclude, tag, and filter into each other: TiddlyWiki is a non-linear personal notebook with a design philosophy unlike anything else in this catalog. Instead of pages in a hierarchy, you compose views by pulling tiddlers together on demand, which is why researchers, zettelkasten practitioners, and GTD devotees have sworn by it for two decades. The whole application is JavaScript, and the UI itself is written in hackable WikiText - customization goes as deep as rewriting the interface from inside the wiki. Self-hosting runs the Node.js version, which upgrades the classic single-HTML-file architecture in the ways that matter for a server: every tiddler is stored as an individual text file (Git-friendly, organizable), edits save through the HTTP API from any modern browser including phones, and one installation can serve multiple wikis blending shared and unique content. The plugin ecosystem covers graph visualizations, themes, languages, and hundreds of community extensions, declared per-wiki in a simple tiddlywiki.info file; the newer MultiWikiServer plugin adds multi-user accounts and tiddler sharing. Your notes stay usable for decades, independent of any corporation - the project's founding promise. BSD-licensed.

Get ready to transform your audience into a thriving empire with Ghost, the ultimate toolkit for the modern creator on a mission to monetize their mojo. Picture this: a sleek website that screams 'you', bursting with content that captivates, newsletters that fly straight into inboxes, and a subscription service that turns followers into financiers. Wave goodbye to bland and hello to a smorgasbord of stunning, free themes that you can finesse to fit your unique flair. But wait, there's more! Ghost's editor is like the Swiss Army knife for content connoisseurs—slick, sophisticated, and oh-so-simple to use. Unleash your creativity with multimedia storytelling that includes everything but the kitchen sink—galleries, chucklesome gifs, videos, podcasts, you name it. And when it's time to hit 'send', those built-in newsletters make sure your words woo your audience without breaking a sweat. Want to play the mysterious type? Ghost's got you covered with native signup forms that turn casual lurkers into committed members. And because we all love a good sneak peek, Ghost dishes out the deets with analytics that spill the tea on who's loving your work the most. Plus, with tantalizing offers and promotions, you'll have new subscribers flocking like seagulls at a beach picnic. All this, hosted on RepoCloud, where the cost is as tiny as your chances of being bored. So, what are you waiting for? Let's Ghost!

Roughly 43% of all websites and over 60% of the CMS market run on WordPress - the GPL-licensed platform that scales from a personal blog to publishing operations and WooCommerce stores. The Gutenberg block editor composes pages from reusable blocks, and full site editing extends block control to headers, footers, and templates; tens of thousands of plugins and themes cover essentially every capability a site might need, from SEO and caching to membership and e-commerce. WordPress 7.0 "Armstrong" marks the platform's biggest structural update since Gutenberg itself: a React-based DataViews admin replaces the legacy list tables with instant filtering, a provider-agnostic AI Client API ships with connectors for OpenAI, Anthropic, and Google, media processing moves into the browser via WebAssembly, and a universal Font Library manages typography across block, hybrid, and classic themes with local hosting for GDPR compliance. New Breadcrumbs, Icons, and lightbox Gallery blocks reduce plugin dependence, and server-side PHP block registration simplifies development. The REST API and WP-CLI make it automatable end to end. Self-hosting is what WordPress was designed for: your content, database, plugin choices, and upgrade schedule stay entirely under your control, free of wordpress.com plan limits.

ApostropheCMS lets editors change text, images, and layouts directly on the finished web page, exactly as visitors will see them. Developers keep full control of the codebase underneath. Click a headline on the live page and type; drop content widgets into editable areas to build sections from rich text, images, galleries, and video; then flip between draft and published modes to preview changes before anyone else sees them. The admin menu handles the structured side of the site: pages in a tree, plus pieces for repeatable content like articles, events, and products, each defined by developers with a field schema API so editors only ever see the fields that belong there. Role-based permissions decide who can draft, who can publish, and which sections of the site each team can touch, and localization keeps language and regional variations of every page organized side by side. When a project outgrows server-rendered pages, the built-in REST APIs serve the same content to Astro, React, Vue, or any other frontend, so a visual-editing CMS quietly becomes the headless backend without a migration. Extensions from the module ecosystem bolt on forms, SEO tools, and integrations without forking the core. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Halo is a modern CMS that handles blogs, knowledge bases, corporate sites, and full e-commerce storefronts from a single installation, distinguished by a polyglot plugin architecture that runs both Java and JavaScript extensions on a GraalVM runtime. Built on Spring Boot 3 with a Vue.js admin console, the platform delivers a clean content management experience with Markdown and rich-text editing, live preview, scheduled publishing, draft management, media uploads, and granular multi-user role-based access controls. Plugins can be enabled or disabled at runtime without restarting the server, and the official marketplace offers over 100 free themes plus a growing library of extensions covering SEO optimization, search integration, paid content access, AI writing assistance, and Q&A chatbots. Storage backends are configurable through plugins, supporting local disk, S3-compatible object storage, and other providers. The fully documented RESTful API enables headless CMS usage for decoupled frontend architectures. Database support includes embedded H2 for quick starts, with production deployments on PostgreSQL or MySQL. Nearly 40,000 GitHub stars and over 2.5 million Docker pulls reflect the project's maturity and active development pace. A single Docker command gets a functional instance running on port 8090. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

Papyra gives you a calm, private home for notes that stays as easy as sticky notes while quietly linking everything together like a wiki. Cards pin, colour, and drag into place on your desk, and opening one drops you into an editor where slash commands insert headings, checklists, tables, or maps without leaving the keyboard. Type two brackets to link another note, and backlinks gather the other direction automatically, following the note even if you rename it. Notes save themselves, and every earlier version is kept, so you can scrub back through history and restore the draft you actually wanted. Sharing a note lets several people type in it together with visible cursors, comments in threads, and mentions that bring the right person in. Private notes lock behind a PIN or your fingerprint and sit encrypted on disk, while a daily journal page collects the day with a mood and a calendar to browse the year. Search covers notes, to-dos, and attachments with highlighted matches, and image text and audio transcripts can join the index. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. GPL-3.0 licensed.

A notes app that is deliberately not a second brain: notesd keeps your grocery lists, journals, and work notes on a server you run, and syncs them to your phone for fully offline use. The web app and the native Android and iPhone apps each keep a complete local copy, so you can write on a subway and watch everything merge when a connection returns; conflicting edits are combined, or preserved as a linked conflicted copy instead of silently overwriting. Notes are stored as Markdown, so exporting your data or mirroring it to a folder of .md files is always one command away. Tags typed anywhere in a note, including nested ones like #home/garden, collect automatically in the sidebar, and Spaces keep work, personal, journal, and recipes in separate contexts. Full-text search runs across titles and bodies, indexed and ranked both on the server and on your phone. Individual notes can be locked with AES-256-GCM encryption performed on your device, unlocked by password, passkey, or biometrics, while the server only ever stores ciphertext. A few accounts per server, each with its own database, make it easy to host notes for family or friends. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Most wikis die of flat page-and-tag sprawl; BookStack's defining decision is enforced structure - an MIT-licensed PHP/Laravel platform (over MySQL) where content lives in a hierarchy of shelves, books, chapters, and pages, the way a physical library works. A shelf maps to a department, a book to "Engineering Runbooks," a chapter to "Database Procedures," a page to the actual document. That opinionation removes the "where does this go?" friction and keeps knowledge bases tidy as they grow. Editing works both ways: a clean WYSIWYG editor for most users, a Markdown editor with live preview for those who prefer it - switchable per page. Full-text search spans all books or scopes to one, with direct links to individual paragraphs, and include tags let you embed one page's content inside another so shared blocks update everywhere at once. Every edit creates a diffable, revertible revision. Page templates standardize recurring formats, tags add cross-cutting categorization, and built-in diagrams.net integration draws architecture diagrams in place. Authentication covers email/password plus OIDC, SAML2, LDAP, and social login; a full role and permission system locks content down per shelf, book, or page. Pages and books export to PDF, HTML, plain text, and Markdown, a REST API automates content, and the whole thing runs happily on the cheapest VPS you can find.

Frappe Wiki is an open-source wiki that turns product guides, help centers, and company handbooks into clean, searchable documentation your whole team enjoys writing. Each space is its own wiki with a separate URL, logo, and access rules, public or limited to chosen roles. The rich text editor handles headings, tables, task lists, code blocks, callouts, images with dark-mode variants, Mermaid diagrams, PDFs, and videos, and stores everything as Markdown. Edits collect in a change request that works like a branch: a reviewer reads a side-by-side diff, then approves, asks for changes, or rejects it, and readers can propose changes too. Every merge adds a version to the page history. Published pages show a page tree, a table of contents, search, PDF download, per-page feedback, and light or dark mode. Analytics report page views, new visitors, top pages, and referrers for the whole wiki, one space, or one page. GitHub Sync keeps a space in step with a folder of Markdown files in a repository. Each page gets meta tags and a generated social card, and the site serves a sitemap, a Markdown copy of every page, and an llms.txt index for AI tools. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Editors can update a static website without learning Git, because Pages CMS puts a visual editor on top of the repository itself. A single .pages.yml file defines what is editable: collections of Markdown files that share a schema, standalone files such as site settings, and nested groups that organize the sidebar. Fields cover strings, rich text, code, dates, numbers, booleans, selects, images, files, references, objects, and repeatable blocks, with front matter stored as YAML, JSON, or TOML. Plain text files like robots.txt open in a raw editor, redirect files in a code editor, and CSV files as an editable datagrid. Collection lists can be searched, sorted, and shown flat or as a folder tree. The media manager supports drag-and-drop uploads, multi-file selection, allowed extensions, and safe or random renaming. People without GitHub accounts join through email invitations and edit content and media, with their saves committed through the GitHub App. Custom action buttons dispatch GitHub Actions workflows after a confirmation dialog or input form, so one click can rebuild a preview or deploy the site. Commit message templates and a choice of app or user commit identity shape how each save appears in Git history. The responsive interface works on mobile screens, and suits Jekyll, Hugo, Astro, Next.js, Eleventy, VuePress, and similar site generators. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

Freelancers keep rebuilding the same handoff: developer builds the site, client breaks the layout trying to change a headline. Primo is an open-source CMS built for that handoff, where developers define reusable blocks and page types, and clients edit text, images, and links directly on the rendered page without touching the structure underneath. Multiple client sites live in one dashboard, organized into groups with a domain each, and publishing generates fast static HTML you can serve from Primo itself or export to another host. The whole site also exists as structured local files, so you or an AI coding agent can pull a site down, edit its blocks and fields in your normal tools, push changes back with revision checks that protect client edits, and publish when ready. Editors can add child pages and reorder the blocks a page type allows, while developers keep control of block code, field schemas, layouts, and roles. A marketplace of starters gives new projects a running start across restaurants, portfolios, practices, and shops. One small server binary with embedded storage runs the CMS and serves the published sites, which suits an agency hosting a dozen client sites on one machine. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.