Pursae
Pursae

1:1 WordPress in a single binary. The plugins you need built in, a drag-and-drop builder ready, easy on RAM.

Scroll down

Keeping WordPress running takes a lot of moving parts.

PHP, PHP-FPM, a web server, MySQL, cron, caching and security plugins. Each with its own config, its own updates, its own problems.

Pursae takes all of that on.

HTTP server, scheduled tasks, page cache, plugin runtime. Everything you used to install separately is handled by one core written in Go.

All of it comes together in one core.

The dashboard, Pursae Editor and the starter themes ship inside the binary. No config to carry between parts, no versions to keep in step. One body, one version.

With Pursae, it's all one binary, ready to deploy.

All it needs beside it is PostgreSQL 17. Database migrations run on start, and caching, scheduled tasks and the plugin sandbox live inside the core. One command is enough: wpgo serve

Same site. A fraction of the load.

The same 1,000-post site, same theme, same container limits. The big number is Pursae, the one below it WordPress.

Single post, no cache
394req/s
WordPress 58 · 6.8×
Doing the jobs of WooCommerce, Yoast, ACF and Elementor
232req/s
WordPress 19 · 12×
Database queries on the home page
16queries
WordPress 139
Idle memory, whole stack
95MiB
WordPress 233 MiB

Same content and theme, same container limits · measured 9 November 2026How we measured

Same WordPress, fewer headaches.

The chores that eat your time when you run a site are the core's job in Pursae. Here are the main differences.

01Dashboard

The admin matches WordPress screen for screen; even the old .php URLs work. Posts, pages, media, menus and roles are where you expect them. You write in Pursae Editor, a real block editor, or in the Classic Editor if you prefer.

02Updates

No PHP versions, no server config, no scattered files. A new release shows up under Dashboard › Updates and installs in one click; database migrations run on their own at start. Every release is signed, and the site refuses one whose signature doesn't match.

03Plugins

Store, page builder, SEO, caching, security, CDN, cookie banner, forum and more. Each one switches on in one click on the Plugins screen; nothing you leave off weighs on your site, and none of them needs its own licence.

04Security

Every plugin runs as a signed Wasm package in its own sandbox: no file system, network only with permission, limited memory. It asks you what it may access when you switch it on, and a package with a bad signature never installs. If something goes wrong, the plugin stops and the site keeps running.

05AI

Pursae has an MCP server built in. Connect Claude, Cursor or any other MCP client with OAuth 2.1 or an Application Password, and it can write posts, upload media, build menus and clear the cache. Every action runs with that password's permissions, so it can't touch anything it isn't allowed to.

06Speed

Same 1,000 posts, same theme, same container limits. On a single post WordPress answers 58 requests a second and Pursae 394. Add WooCommerce, Yoast, ACF and Elementor and WordPress drops to 19, while Pursae, doing the same jobs with its built-ins, stays at 232. When you do want a cache, Pursae Cache switches on in one click and refreshes only the pages that changed.

On WordPress, you collect plugins. On Pursae, they're already there.

One for pages, one for the store, one for backups. You install each one, update each one, and pay for some of them. In Pursae they come with the core.

On WordPressOn Pursae

01

plugins installed

Side by side with WordPress

TopicWordPressPursae
A separate plugin on WordPress, built into Pursae
Page builderElementorElementor Pro $60/yrWeb Builder
E-commerceWooCommerce and paid add-onsSubscriptions $279 + Bookings $249 + Product Bundles $79 + Gift Cards $79/yrWooCommerce is free, its add-ons are paidPursae CommerceCard payments with Stripe, subscriptions, bookings and 14 modules
MultilingualWPML, PolylangWPML Blog €39/yrPursae Multi LanguageLanguages, translations, hreflang
Backup and migrationUpdraftPlusUpdraftPlus Premium $70/yrPursae Backup ManagerThe whole site in one archive
SecurityWordfenceWordfence Premium $149/yrPursae SecurityTwo-factor login, login lockout, custom login URL, activity log
SEOYoast SEOYoast SEO Premium $118,80/yrPursae SEOContent analysis, schema, sitemaps, redirects
Caching and CDNWP Rocket, WP Offload MediaWP Rocket $60 + WP Offload Media $69/yrPursae Cache, Pursae CDNFull-page cache, offload to S3/R2, WebP image delivery
Contact forms and SMTPContact Form 7, WP Mail SMTPWP Mail SMTP Pro $99/yrContact Form 7 is freePursae Contact Form, Pursae SMTPSpam protection, email log and reports
Custom fieldsACFACF PRO $49/yrPursae Custom FieldsField groups, custom post types, options pages
Cookie banner and pixelsCookieYes, PixelYourSiteCookieYes $100 + PixelYourSite Pro $199/yrPursae Cookie, Pursae PixelGDPR banner, Consent Mode v2, server-side conversions
Visitor analyticsJetpack Stats, Site KitJetpack Stats $100/yrSite Kit is freePursae AnalyticsCookieless; real-user Core Web Vitals
ForumbbPressFreePursae ForumMembership, Google sign-in, levels and badges
Headless and GraphQLWPGraphQLFreePursae HeadlessContent type builder, REST, GraphQL, webhooks
Maintenance modeSeedProdSeedProd Basic $79/yrPursae Maintenance
Infrastructure
What it needs to runPHP, a web server, MySQL, cronOne binary and PostgreSQLCaddy or Nginx in front for HTTPS
UpdatesCore, theme and every plugin separatelyOne click in the dashboardEvery release is signed; the site won't install one that doesn't verify
Plugin licences, per year$1.838,80 + €39≈ $1,880 a year, one site0 ₺No separate licences for the built-ins; Pursae is free on your own server
If a plugin crashesThe error can take down the whole siteThe plugin stops in its sandbox, the site stays up

Running on Pursae today.

A few of the sites running on Pursae today: a community, a design studio, a personal blog and a fan site.

See all

Pursae for developers

Write one of the first plugins.

  1. Write it in Go. You write your plugin in plain Go. TinyGo compiles it into a small WebAssembly (.wasm) file.
  2. Declare what it needs. plugin.json says up front what the plugin may touch; the package is signed and runs in its own sandbox inside wazero. Everything it does not declare stays closed: no file system, network only with permission.
  3. Send it to us. When it is ready, send your plugin to us; we review it and add it to the Pursae Marketplace.

Toggle the permissions and watch plugin.json.

plugin.json
 
gopher-factsSample plugin, version 1.2.0

Anything not on the list is closed. If the plugin crashes, the site doesn't.

You're invited.

Three invitations, three ways in. Install the beta today, ask the community, or let us host your site when Hosting opens.

You're invited to the open beta.

Today, on your own machine.

Install it with three commands and try moving your site over. Be the first to tell us what's missing.

You're invited to the community.

Every day, on the Pursae forum.

Install, plugin and theme questions get answered there, and the team is around. Post your question, or answer someone else's.

You're invited to the launch of Pursae Hosting.

1 December 2026, on our servers.

We take care of servers, HTTPS and backups. Join during the beta and your first three months are free; all we ask in return is your feedback.

By signing up you accept the Privacy Policy. Pricing and terms are in the FAQ.

Our team

The small team that builds, tests and designs Pursae.

  • Bora Ata Türkoğlu

    Bora Ata Türkoğlu

    Founder & Lead Developer

  • Aleyna Özyaman

    Aleyna Özyaman

    Co Founder & Head of Designer

  • Could it be you?

    Frontend Developer wanted

    Apply
  • Could it be you?

    Product Designer wanted

    Apply

FAQ

If your question isn't here, ask on the community forum.

No. PHP plugins and PHP themes don't run on Pursae. The 18 plugins people need most ship with the core, and themes are made of Go templates and a theme.json. There are 68 ready-made themes with demo content, plus the Web Builder's Theme Builder.

Your content, yes. Export a WXR file from Tools > Export in WordPress and upload it under Tools > Import in Pursae. Posts, pages, terms, comments and menus come across, and media files are pulled from their public URLs. Products move with WooCommerce's product CSV. User passwords, settings, PHP plugins and themes don't move.

No. It runs anywhere you can run a binary and reach PostgreSQL: a VPS, a container platform or your own server. If you'd rather not deal with servers, Pursae Hosting opens on 1 December.

If you join during the beta, the first three months are free and then it's $5 a month. No card needed to sign up, and you can export your site and move it to your own server at any time. On your own server, Pursae is always free.

Pursae serves HTTP itself. On your own server, put a reverse proxy like Nginx or a PaaS in front of it for TLS. On Pursae Hosting, that's our job.

For new brochure and content sites, yes. Stores can take card payments through Stripe; local providers like iyzico aren't there yet. Before you take a site live, go through the security and production notes first. We track bugs reported during the beta openly on GitHub.

Yes. Pursae has an MCP server built in. Connect a client like Claude or Cursor with OAuth 2.1 or an Application Password, and it can write and publish posts, upload media, build menus, switch plugins on and off and clear the cache. Every action goes through the REST API with that password's permissions.

Once a day, a production install sends hub.pursae.com its site URL, Pursae version, language, operating system, licence key if there is one, the active theme and the list of installed plugins and themes. Your content, users, email addresses, passwords, visitors and orders are never sent. WPGO_HUB=off turns it off completely; one-click updates, signed plugins and the marketplace switch off with it.