Drupal

Stewarded by the nonprofit Drupal Association; core and contrib code written by a volunteer/vendor community, not a single company.

Drupal 1.0.0 released January 15, 2001.

Core Drupal is self-hosted; Drupal CMS (2025 distribution) is the same self-hosted software with a guided installer and curated defaults, not a hosted SaaS product.

Drupal core and all Drupal.org-hosted contributed modules/themes are open source.

GNU General Public License, version 2 or later; all Drupal.org-hosted code must be GPLv2+ compatible.

Positioning reflects Drupal's traditional strength (structured content, access control, scale) plus Drupal CMS's 2025 push into marketer-friendly site building.

Drupal software itself is free; this page (and its 404 at time of check) reflects that there is no vendor pricing page for the software; costs come from hosting/support vendors.

The software is free open-source; "free plan" isn't a vendor tier since there is no vendor selling Drupal itself.

Unlike SaaS builders, Drupal has no artificial free-tier caps; you pay for hosting, a domain, and (usually) developer time.

Trial concept applies to hosting vendors, not to Drupal itself.

Market-typical figure, not a vendor price: budget shared/VPS hosting capable of running Drupal (e.g., Hostinger, DreamHost Drupal-compatible plans) starts around $10/mo. Software itself is free.

Market-typical figure: Pantheon's entry-level managed Drupal hosting plan (Basic) starts at $41/mo, a common reference point for small-business managed Drupal hosting.

Drupal Commerce is free and has no vendor pricing tiers; a realistic ecommerce-capable hosting cost would need a dedicated hosting quote (e.g., Acquia/Pantheon commerce-tier hosting) not available from official docs alone. Left null rather than guessed.

Self-hosted open-source software has no "powered by" branding requirement at any tier.

No vendor subscription for the software itself, so there is no introductory-vs-renewal price gap; hosting-vendor pricing varies by provider and is out of scope for the core platform.

Not applicable; no purchase of the software occurs, so there is no money-back window. Hosting vendors set their own refund policies.

Drupal's total cost of ownership is driven far more by hosting and developer time than by any licensing fee.

Drupal CMS 2.0 (2026) ships Drupal Canvas as the default visual editor; a drag-and-drop, component-based page builder replacing the older Layout Builder as the primary experience. Classic Drupal (non-CMS core install) still centers on CKEditor 5 field editing plus optional Layout Builder.

Drupal Canvas (Drupal CMS 2.0) and core Layout Builder both provide drag-and-drop placement of components/blocks.

Drupal Canvas supports building/editing directly on the live page preview rather than switching to separate admin forms.

Content revisioning (view/revert/delete revisions) is a core Drupal capability, exposed as configurable permissions.

Could not verify a specific autosave claim for Drupal Canvas or core content forms from official docs; core historically relies on manual save plus revisions rather than confirmed continuous autosave.

No official native mobile app for content editing; Drupal CMS ships a desktop launcher app for installation/setup, not a mobile content-editing app. Admin UI is responsive in-browser.

Switching themes/templates in Drupal is not guaranteed content-safe by default; content is structured independently of theme, but page-builder layouts (Layout Builder overrides, Canvas component placement) are generally theme- and component-library-specific and can require rework on a template switch.

Editorial judgment: classic Drupal core has a well-known steep learning curve (concepts like entities, fields, permissions, contrib module management); Drupal CMS 2.0's Canvas builder and AI chatbot meaningfully lower this for basic site building, but the platform as a whole; especially anything beyond a template site; still requires more technical fluency than hosted builders like Wix or Squarespace.

Drupal CMS 2.0 ships with 2 official site templates at launch (Byte; a SaaS/marketing template; and Starter, a minimal Canvas-ready base). Separately, Drupal.org lists thousands of community contributed themes (see extensibility/theme ecosystem), which is a different thing from CMS-native "site templates."

Custom fonts can be added via theme CSS/webfonts; no platform restriction on font uploads since you control the theme's code.

Core ships a Breakpoint module and Responsive Image module; themes define breakpoints in YAML and site builders map image styles to them; configurable but not a full freeform visual control panel.

Full custom CSS via themes; no plan gating since there are no plans.

Full custom JavaScript via themes/modules; no plan gating.

Could not verify a native, no-code animation/interaction authoring tool in core or Drupal CMS from official docs; animation is typically implemented via custom theme CSS/JS rather than a built-in visual tool.

Drupal Canvas's Mercury component library and theme-level design tokens (via the active theme's CSS/config) provide global style control; classic Drupal achieves this through theme settings and base theme variables.

Editorial judgment: as self-hosted, code-accessible software, Drupal places no ceiling on design; any HTML/CSS/JS is possible via custom theming; though achieving that flexibility requires developer skill rather than being available to a no-code end user.

Drupal ships no hosting of its own; you must bring your own server or a hosting partner (Pantheon, Acquia, Platform.sh, shared hosts, etc.).

Drupal is inherently self-hosted software; this is the default mode, not an option layered on top.

No CDN ships with core Drupal; CDN is provided by hosting choice (e.g., Pantheon and Acquia bundle a CDN, generic shared hosts typically do not).

Not provided by Drupal itself; official docs cover enabling HTTPS at the web-server layer, and certificate provisioning depends entirely on the chosen host (most modern hosts include free SSL via Let's Encrypt, but this is a hosting-layer feature, not a Drupal one).

No platform-wide SLA exists since Drupal is not a hosted service.

Drupal core has no built-in bandwidth or storage cap.

Drupal is a dynamic PHP application backed by a database; it is not natively a static-site generator. Static caching layers and headless/decoupled front ends exist but full static export of a traditional Drupal site is not a core capability.

May 2026 CrUX data via HTTP Archive CWV Technology Report API: 65.0% of 189,014 origins with good CWV (desktop 65.1%, mobile 64.8%). Report technology name: 'Drupal'.

Core Responsive Image module + Image Styles provide automatic resizing/format handling; not automatic by default without configuration, but the tooling is native.

Drupal core adds native browser lazy-loading (loading="lazy") to image and iframe fields by default since Drupal 9.3+.

Core provides configurable page cache, dynamic page cache, and cache-tag-based invalidation; site owners/developers have granular cache control.

Native via core Metatag-adjacent fields is contrib (Metatag module), but page titles are core; full title/meta description control is standard practice via the widely-used Metatag contrib module.

URL aliases are editable per-page in core; the Pathauto contrib module automates pattern-based slug generation.

Flexibility is high but requires configuration; nothing is forced.

Handled by the widely-used contrib Redirect module (301/302, canonical URL enforcement); not shipped in core.

Core outputs canonical link tags by default; the Redirect module adds enforcement of canonical URLs.

robots.txt ships as an editable file at the site root in a standard Drupal install.

Not in core; the Simple XML Sitemap contrib module (multilingual, hreflang-aware) is the standard solution.

Core ships a basic RDF/RDFa mapping module (limited, no GUI); the standard approach is the contrib Schema.org Metatag module, which outputs JSON-LD but requires manual field-to-schema mapping, not automatic generation.

Core's Content Translation module outputs hreflang tags on translated entity pages; the contrib Hreflang module extends this to all page types. Treated as native since the base capability ships in core for content entities.

Standard via the Metatag contrib module (near-universal on Drupal SEO installs), which covers Open Graph and Twitter Card tags.

Achievable per-page via the Metatag module's robots meta tag field.

Alt text is a standard, required-by-default field on core Image fields; Drupal CMS 2.0 additionally adds an AI-assisted "Generate with AI" alt-text suggestion feature.

A Basic Page/Article content type ships in core (Standard install profile) suitable for blogging; Drupal CMS's Byte template includes a preconfigured blog out of the box.

Custom content types with custom fields are a foundational, native core capability (Field API + content type UI); one of Drupal's signature strengths.

Taxonomy vocabularies/terms with hierarchical parent-child support are native to core.

Core Content Moderation/Workflows modules support scheduled publish states; core also includes a Scheduler-type publish-on-date capability via contrib (Scheduler module) commonly paired with core moderation.

Native core capability across content entities, with granular per-role permissions for view/revert/delete.

Core's user/role system supports unlimited authors with granular per-content-type permissions.

RSS feed generation is native via core's Views module (default RSS feed displays ship with the Standard install profile).

Core JSON:API module (enabled by default, zero-config) exposes full read-write CRUD on entities; core REST module offers a more configurable but more complex alternative.

Ecommerce is not in Drupal core; Drupal Commerce is a separate, free, open-source module suite that is the de facto standard.

Unlike SaaS ecommerce platforms, there is no plan-tiered product ceiling.

No platform cut, unlike hosted ecommerce SaaS.

Gateway support depends on installing the matching contrib payment module.

Drupal Commerce supports digital/downloadable products via standard product-type configuration and contrib add-ons.

Recurring billing/subscriptions require the separate Commerce Recurring Framework contrib module, not core Commerce functionality.

Multi-currency is a native Drupal Commerce capability (Store > Configuration > Currency), with a Commerce Multicurrency contrib module available for more advanced conversion scenarios.

Commerce Point of Sale (POS) is an official contrib module maintained for Drupal Commerce 2, supporting in-person cash/card transactions, registers, and receipts.

Not native to Commerce core; achieved via contrib modules (e.g., Commerce Abandoned Carts).

Modular, not bundled into a single core checkout like some SaaS platforms.

Full database/content export is possible at any time (direct DB access, core Migrate API, or JSON:API entity export) since you control the hosting environment.

Because you control the server, export is not mediated or limited by a vendor.

Themes are plain code (Twig templates, CSS, JS) fully owned by the site operator and portable to any Drupal instance or, with rework, another platform.

Domains are managed independently of the platform.(standard DNS/registrar), as with any self-hosted software; official docs confirm Drupal runs on any compatible web server the owner controls, so the domain points wherever the owner chooses.

Core design principle; Drupal runs on any PHP/MySQL-or-equivalent-compatible server; moving hosts requires only a standard code+database migration.

Core JSON:API module exposes full, zero-configuration read-write access to all entity types by default.

Editorial judgment: as free, GPL-licensed, self-hosted software with full database and code ownership, Drupal has structurally low platform lock-in; the tradeoff is that avoiding practical lock-in (to a specific developer's customizations or contrib module choices) still requires technical expertise to actually execute a migration.

This total includes all historical/unmaintained/abandoned projects as well as actively maintained ones; not a curated "active and current" count; a smaller subset is in wide current use.

Core ships JSON:API (zero-config, entity-based) and a configurable REST module.

Not built into core JSON:API/REST, but standard via well-established contrib modules (e.g., REST Hooks for outbound webhooks to Zapier-like services, Webhook Receiver for inbound).

Full custom code (PHP modules, JS, CSS, Twig templates) with no plan restriction, since Drupal is self-hosted software you control.

Drupal core has used Symfony components since Drupal 8.

Drush is the de facto standard CLI/scripting tool for Drupal (install, config, cron, migrations); maintained as a companion project, installed via Composer, not part of core itself but universally used.

Achieved via JSON:API/REST endpoints plus contrib modules (e.g., a community Zapier integration built on JSON:API) or Zapier's generic Webhooks connector; not a single official first-party Zapier app on drupal.org, but a well-documented pattern.

Reflects Drupal's build-your-own-stack philosophy versus platforms with native bundled integrations.

Drupal CMS 2.0's AI features generate individual pages from a prompt (using existing Canvas components) and assist with content-type/site-structure setup via chatbot; this is page/content-model generation, not full autonomous "generate an entire site" scaffolding. Marked false to avoid overstating vs. tools built specifically for full-site AI generation.

The Drupal Agent Chatbot in Drupal CMS assists with site-building/content-structure tasks conversationally; combined with the AI module's broader text-generation tool integrations, this covers AI writing assistance, though it is opt-in and requires a connected OpenAI or Anthropic API key.

AI-assisted alt-text generation for images ships as a Drupal CMS AI feature ("Generate with AI" button); this is accessibility-focused alt text, not AI image creation/editing.

Could not verify a dedicated AI SEO-assistance feature (e.g., AI-generated meta descriptions or keyword suggestions) in official Drupal CMS AI documentation; current confirmed AI features are page generation, chatbot site-building help, and alt-text generation.

AI is opt-in and bring-your-own-API-key, not a bundled/metered vendor AI feature.

Drupal's role/permission system is a signature strength; granular per-content-type, per-transition, and per-entity permissions are natively configurable.

No real-time concurrent (Google-Docs-style) multi-user editing in core or Drupal CMS; the contrib Content Lock module exists specifically to block simultaneous edits, and its docs confirm core provides no concurrent-edit protection by default.

Core Content Moderation + Workflows modules provide configurable multi-state editorial approval workflows (e.g., draft → review → published) with per-transition permissions.

Core Workspaces module supports full-site content staging beyond simple draft/published states, letting editors build up changes in a workspace and preview/publish them together.

Core ships a public-facing Comment module (for site visitors commenting on published content), not in-editor internal collaboration comments/annotations for editorial staff; no native in-editor commenting feature exists for internal review.

Not in core; audit logging (tracking entity views/inserts/updates/deletes) requires the contrib Audit Log module or hosting-vendor-level logging (e.g., Acquia).

Support is community- and partner-driven rather than centralized.

No official 24/7 support exists for the open-source project itself; 24/7 support is only available by contracting a paid hosting/support partner (e.g., Acquia Enterprise).

Editorial judgment: Drupal.org's official documentation and User Guide are extensive and well-maintained, covering both core and major contrib modules, but the volume and technical depth can be hard for non-developers to navigate compared to consumer-focused SaaS help centers; not rated "excellent" for approachability.

Figures come from Drupal.org community statistics discussions rather than a single authoritative current dashboard; treat as an order-of-magnitude figure.

Certification lives at the hosting-vendor layer, not the software layer.

Not automatic in core; handled via the contrib Backup and Migrate module (manual or scheduled database/file backups) or at the hosting-platform level (e.g., Acquia/Pantheon automated backups).

Accessibility is a formal, documented core commitment, not just a contrib add-on.

Multilingual support (Language, Content Translation, Interface Translation, Configuration Translation modules) is built into Drupal core since Drupal 8; a widely cited core strength.

Core Content Translation integrates with Content Moderation, allowing per-language moderation states and editorial review workflow for translations.

Core supports per-language URL paths/prefixes and hreflang tags on translated content pages (extendable site-wide via the contrib Hreflang module).

Core has built-in RTL (right-to-left) language rendering support, including RTL-aware core themes.