Design and diagrams decision

Dracula PRO

Keep paying only if you need Dracula Pro paid assets; otherwise use the project's open-source repository to self-host and publish theme packages — the repo already provides the core product and is straightforward to package and maintain.

Visit website

You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$20one-off6 h to build

$0/mo1 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Dracula PRO alternatives, with the arithmetic →

dracula/dracula-themethe vendor’s own source23,554MIT🧛🏻‍♂️ One theme. All platforms.Open on GitHub catppuccin/catppuccin19,647MITA cross-application pastel dark theme with ports and tooling for many apps.Open on GitHub folke/tokyonight.nvim8,169Apache-2.0A polished Neovim dark colorscheme that includes themes for several terminal apps.Open on GitHub

What a replacement has to do

Provide theme files, package them for common platforms, and publish documentation and previews so users can install the theme.

What it still won’t have

Paid Dracula Pro commercial assets and any premium-only bundles (site lists a separate 'Dracula Pro' product).
Any premium or shop items sold via Dracula Shop or Pro (purchase-only content).
Official paid support or subscription perks tied to Dracula Pro.

What remains hard

Integration maintenanceDracula Theme for 400+ apps
Brand trustThe most famous theme ever created and available everywhere.

Read the build prompt

First-year cost

No published price

Dracula PRO does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying

—

Subscription price × seats × 12

Build it

—

AI build —APIs + hosting —

Time you would spend

—

What you would spend

Your monthly price$/moAI to build it$ onceAPIs + hosting$/mo

What we assumed

Initial buildhrsMonthly upkeephrsYour rate$/hr

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet

Build a minimal open-source Dracula theme distribution and preview site using Node.js (18+), npm, Sass, and Eleventy: produce (1) canonical CSS/SCSS variable files and a tokens JSON, (2) an npm package that bundles compiled CSS and per-app subfolders (VSCode, iTerm, Alacritty, Vim/Neovim), (3) zip downloads for each app, (4) a static Eleventy preview site with live code samples and screenshots, and (5) README installation snippets per app. Out of scope: recreating any paid 'Dracula Pro' art assets or e-commerce/shop functionality. Include error handling for build/publish steps, CI pipeline (GitHub Actions) that lints SCSS, runs a build, and publishes the npm package on tag, and unit/integration tests for the build steps.

How we checked3 sources · 2/2 runs agreed · evidence score 99

How the score was reached

Self-host verdict base92
An open-source build was found+5
3 cited sources+3
2/2 assessment runs agreed+4
Evidence score99

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

official productDracula Theme — official product
open sourcecatppuccin/catppuccin
open sourcefolke/tokyonight.nvim

Integrity checks

What held up, and what did not.

✓ 2 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page