Can AI replace Dorik?
The core loop is buildable, but a dependable replacement becomes a real weekend or multi-day project. For Dorik, build a small responsive site with pages, collections, and simple forms. The hard boundary is hosting, cms, memberships, templates, and no-code editing polish, plus editor polish, hosting, templates, and ecosystem.
01What it costs
Checked Aug 14, 2026 · source: dorik.com.
| Plan | Monthly | Billed yearly | What you get |
|---|---|---|---|
| Personal | $29 | $20.75/mo | 1 custom domain; 25 static pages; 200 blog posts; 5 CMS collections and 200 collection items; no collaborators |
| Business | $59 | $41.5/mo | 3 custom domains; unlimited pages/blog posts/storage/bandwidth; 10 collaborators |
| Agency | $99 | $79/mo | Unlimited custom domains, pages, collaborators, blog posts, storage and bandwidth; agency white-label/client-billing features |
Hidden costs: Dorik does not sell domains; you must buy one separately. Lifetime Personal charges $199 one-time per additional website; Lifetime Business charges $149 per additional website and limits code export to 15/month.
02Could AI build it for you?
The core job: Assemble a small responsive site from sections with pages, collections, and simple forms, edit copy and media, preview breakpoints, and publish a static site to a user-owned target.
What a working version needs:
- Node.js 22
- domain and deploy target
- local images
- optional form-email API key
Editorial comparison targets the Personal plan and a single-site builder DIY substitute. Recheck price before merge.
03What you'd give up
- hosting, CMS, memberships, templates, and no-code editing polish
- large template marketplace
- managed hosting and CDN
- advanced CMS
- commerce and agency workflows
People still pay for Dorik because the page renderer is reproducible, but customers pay to avoid becoming their own hosting and browser-compatibility team. The recurring cost buys responsive rendering, forms, domains, certificates, deploys, backups, template maintenance, and browser regressions, not just the visible interface.
04Free and cheaper alternatives
A proper in-page CMS for people who prefer editing the page to editing a dashboard about the page.
Versus paying: Concrete CMS is less visually freeform and polished than Dorik, and the owner must provide hosting, updates, backups and form delivery.
concretecms.org →A drag-and-drop PHP CMS with pages, forms and collections; simple to edit, not maintenance-free.
Versus paying: Microweber's templates and integrations are less polished, and replacing Dorik means running the PHP host, updates, backups and mail yourself.
microweber.org →Unlimited hosted projects, CMS and custom domains free; the badge is cheaper than Dorik.
Versus paying: Plasmic is much more React/component-oriented than Dorik, and its free hosted output keeps Plasmic branding.
plasmic.app →A visual multi-page static-site builder with export; collections are manual rather than magical.
Versus paying: Silex has no comparable built-in collections/CMS workflow, so repeated content and simple data-driven pages become manual.
silex.me →A finished visual CMS with forms, posts and custom content; obscure enough that support starts with reading docs.
Versus paying: Vvveb is less polished and approachable than Dorik, and the reader becomes responsible for the PHP server, mail, security and backups.
vvveb.com →A polished visual builder and CMS connector; using your own domain for free moves hosting onto you.
Versus paying: Webstudio lacks Dorik's all-in-one collections/forms/hosting simplicity, and a free custom-domain site requires export or self-hosting.
webstudio.is →05The build prompt
Paste this into an AI coding tool (such as Claude, ChatGPT, Lovable or Replit) to build your own version.
Build a personal replacement for Dorik in an empty repository. Use Next.js 15, TypeScript, Tailwind CSS, SQLite, Drizzle ORM, and static export; do not offer alternative stacks. The core loop is: assemble a small responsive site from sections with pages, collections, and simple forms, edit copy and media, preview breakpoints, and publish a static site to a user-owned target. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Provide a section library for hero, proof, features, pricing, FAQ, and footer blocks. Use a constrained design-token system rather than arbitrary CSS controls. Allow inline text editing and local image upload with responsive optimization. Preview desktop, tablet, and mobile widths and surface overflow errors. Persist projects in SQLite and support a portable JSON export. Generate a clean static Next.js output and document deployment to one target. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Deliberately leave out a plugin marketplace. Deliberately leave out multi-tenant managed hosting. Deliberately leave out advanced ecommerce, memberships, and agency billing. Finish by running the tests and listing the exact commands used.
06Open-source starting points
- Webstudio: Open-source visual website builder designed around web standards.
App prices, verdicts, alternatives and build prompts are adapted from Can I Vibecode It? (MIT License, © 2026 Rob Hallam). Each price shows the date it was checked and its source. Prices change; confirm on the vendor's site before you decide.
Get new verdicts in your inbox.
One short email when new verdicts land: what AI can now do for you, and what it still gets wrong. No spam. Unsubscribe anytime.