jtakeit
Try for free

For developers leaving WordPress

A WordPress alternative for developers who maintain client sites

jtakeit is a WordPress alternative for developers: each client site is prerendered at build — in Astro by default, or in any framework that renders its pages to HTML — with no plugins to update, and the owner still edits their own text.

tree client-site
client-site/
├── src/
│   ├── pages/index.astro     # the design — yours
│   └── content/blocks.ts     # what the owner may edit
├── jtk/
│   ├── catalogue.json        # generated, never hand-edited
│   └── content/index.json    # the published words
└── package-lock.json

# no wp-content/plugins/ — nothing here to update
A whole client site on jtakeit, here on the Astro scaffold: one project in git.

01/ why developers leave

Why developers look for WordPress alternatives

WordPress is flexible, can do almost anything with the right plugin, and many clients already know its dashboard. For a lot of sites it is the right answer.

The cost lands on you. Every client site is a PHP application with a database, a theme and a set of plugins, each with its own updates — and you look after all of them, for every client, for as long as the site is live.

jtakeit takes the other route: the site is written by your AI agent and prerendered at build — Astro by default, or any framework that renders its pages to HTML — and the parts that need a server — forms, bookings, billing, hosting — are run by the platform.

02/ what moves where

WordPress to static: what moves where

The jobs a WordPress site does with plugins, and where each one lives on jtakeit.

WordPress building blocks and their jtakeit equivalents
On WordPressOn jtakeit
Theme and page builderPages and components in your git repository — Astro by default, or another static generator
wp-adminThe owner taps the text on their own page to edit it
A contact-form pluginForms protected against spam; enquiries go to Telegram, email or the admin inbox
A booking pluginThe bookings module; paid bookings go straight to the business’s own Stripe
A backup pluginBackups run by the platform — and the site itself is a repository you hold
An SEO plugin’s warningsA build with noindex, a robots.txt that blocks crawlers, an empty sitemap or a canonical on another host is refused
Hosting, PHP and a databaseA static build, hosted by jtakeit; under a minute on the Astro scaffold

03/ static, still editable

A WordPress static site, without a plugin to make it static

Pages are built ahead of time into plain HTML. There is no plugin layer turning a dynamic site into a static copy — static is simply what the site is.

  1. Scaffold. jtakeit’s Astro scaffold starts the project with the platform’s contract in it — or use another static generator.
  2. Rebuild. Your agent writes the pages again from the current site, and declares what the owner may edit.
  3. Preview. The client signs off on the new site before they pay.
  4. Launch. A person moves the domain in the panel — an agent cannot.
zsh — client-site
$ npx @jtakeit/astro create client-site --locale en
# the agent rebuilds the pages from the current site
$ npx @jtakeit/astro catalogue
$ git push origin main
# preview → the client signs off → a person launches the domain

04/ what it isn’t

Sites like WordPress — and what jtakeit deliberately isn’t

jtakeit has no plugin directory and no “add page” button for the owner. Structure is a commit, made by you or your agent; the owner fills in the words the catalogue lets them fill in.

If a client wants to build new pages themselves, install plugins or redesign their own site, WordPress serves them better. If they want a site that keeps working, edits they can make in a minute and a developer who isn’t updating plugins for them, read on.

05/ many sites, one developer

Among ManageWP alternatives, a different answer: nothing to update

Tools like ManageWP exist to update plugins, themes and core across many WordPress sites at once. jtakeit removes the thing being updated: each client site is static output and a git repository you hold.

What is left to manage is what the client cares about — their words, their enquiries, their bookings — and the client can take their data out as CSV and JSON whenever they want, with or without a live subscription.

See how editing is declared in the Astro CMS for client sites, or how an agent does the rebuild in building client sites with Claude Code. Prices are on the pricing page, and the editing side on its own is described in a static CMS for client sites.

06/ questions

Moving off WordPress

Is jtakeit a good WordPress alternative for developers?
It fits developers who build brochure sites, landing pages and booking sites for clients and want to stop maintaining plugins. It does not fit a client who wants to add pages, install plugins or redesign the site themselves; for that, WordPress is the better tool.
Can I turn a WordPress site into a static site with jtakeit?
The move is a rebuild, not a plugin export. Your AI agent writes the site again from the existing pages and content — on the Astro scaffold or in any framework that prerenders its pages; the platform builds it and serves it, in under a minute on the Astro scaffold.
Can my client still edit the site after leaving WordPress?
Yes. The owner taps the text on their own page to edit it, and can change anything the site’s catalogue declares as theirs. They cannot add pages or blocks, which is what keeps the design intact.
What replaces contact form and booking plugins?
Enquiry forms are run by the platform and protected against spam, and enquiries arrive in Telegram, by email or in the admin inbox. The bookings module takes paid bookings straight into the business’s own Stripe account.
Is jtakeit one of the ManageWP alternatives?
Not directly. ManageWP manages many WordPress sites; jtakeit replaces the WordPress layer, so there are no plugin or core updates to manage at all. You still run many client sites from one place, and each one is a git repository you hold.

07/ try it free

Move a client off WordPress

Sign up in the panel and build your first client site. Building and previewing cost nothing — you pay a wholesale price only when a site goes live.

Try for freeadmin.jtakeit.com

  • Free until a site goes live
  • Then a wholesale price per live site, from €5 a month
  • The code stays in your git repository