Pursae
WordPress, rewritten in Go.
One binary · PostgreSQL · the admin you already know · 18 built-in plugins.
Quick start · Tour · Plugins · AI agents · Privacy · Full guide · Developer docs
⚡ Quick start
You need Docker (with Compose v2), git and make.
On a server (production build, updates from hub.pursae.com, behind your TLS proxy):
git clone https://github.com/pursae/pursae.git && cd pursae
cp .env.example .env # set WPGO_DB_PASSWORD, WPGO_SITE_URL (https://…), SMTP
docker compose up -d --build # → 127.0.0.1:8088; point Caddy or nginx at it
The installer is locked with a setup token: open the install link the server prints on its first start
(docker compose logs pursae, a line like https://example.com/wp-admin/install?token=…), or set your own
WPGO_SETUP_TOKEN in .env. Lost the link? docker compose exec pursae wpgo setup-token prints a new one.
Updates arrive in Dashboard › Updates (one click); data lives in Docker volumes. Every setting is listed
in .env.example.
On your machine (development build to try it out; it does not talk to hub.pursae.com):
make docker-up # → http://localhost:8088
Ports, env vars, proxies, backups: docs/GUIDE.md.
✨ Why Pursae
🐹One Go binaryNo PHP, no FPM, no extensions. |
🐘PostgreSQL 17Typed schema, JSONB, migrations on start. |
🧩Wasm pluginsSigned, sandboxed, permission-gated. |
🚀Fast by defaultBuilt-in page cache, static builder output. |
🧭 Tour
![]() Dashboard — the WordPress admin, 1:1 |
![]() Pursae Editor — the real block editor |
![]() Pursae Web Builder — visual pages, static output |
![]() Twenty Twenty-Five — demo content in one click |
Posts Media Library Themes Menus Plugins Users & multi-role Site Health Settings📸 More core screens — posts, media, themes, menus, plugins, users, health, settings








🧩 Built-in plugins
Native, switched on and off with one click under Plugins; all of them are off on a fresh install except Pursae Cache and Classic Editor. Click a heading below the table to open its screenshots.
| | Plugin | In one line | Docs | |---|---|---|---| | 🛒 | Pursae Commerce | Store, cart, checkout, orders, bookings & premium modules | → | | 🎨 | Pursae Web Builder | Visual pages, Theme Builder, popups, theme library | → | | 🔎 | Pursae SEO | Analysis, schema, sitemaps, redirects | → | | ⚡ | Pursae Cache | Full-page cache + page optimization | → | | 🛡️ | Pursae Security | 2FA, MFA codes, lockouts, activity log | → | | ☁️ | Pursae CDN | S3/R2 offload, image service, purge | → | | 🔌 | Pursae Headless | Content types, REST, GraphQL, webhooks | → | | 🍪 | Pursae Cookie | GDPR/KVKK banner, Consent Mode v2 | → | | 📈 | Pursae Pixel | Meta, GA4, Ads, TikTok + server-side | → | | 📊 | Pursae Analytics | Cookieless stats + real-user Core Web Vitals | → | | 💬 | Pursae Forum | Forums, email + Google sign-up, levels & badges | → | | ✉️ | Pursae SMTP | Mailers, email log, reports | → | | 🗂️ | Pursae Custom Fields | Field groups, CPTs, options pages | → | | 🌍 | Pursae Multi Language | Languages, translations, hreflang | → | | 📝 | Pursae Contact Form | Forms, mail templates, spam guard | → | | 🚧 | Pursae Maintenance | Maintenance / coming-soon page | → | | 💾 | Pursae Backup Manager | One-click backup & migrate | → | | 📄 | Classic Editor | TinyMCE editing, per-user switch | — |
Store themes with a full demo shop Premium modules, built in Home & setup tasks Analytics🛒 Pursae Commerce




Sections, design, devices Theme Builder: header, footer, templates🎨 Pursae Web Builder


Visitors, views and Core Web Vitals Who is counted, goals, retention📊 Pursae Analytics


Privacy-friendly site statistics on one page (Analytics in the admin menu), without cookies, without storing IP addresses and without a consent banner — in the class of Plausible and Jetpack Stats:
- Visitors, visits, page views, views per visit, bounce rate and visit duration, each compared with the previous period, a chart and live visitors.
- Top and entry pages, sources (Google, ChatGPT, social networks, other sites), UTM campaigns, countries, devices, browsers and operating systems.
- Goals: outbound link clicks, file downloads, form submissions and 404s.
- Real-user Core Web Vitals: LCP, INP, CLS, FCP and TTFB at the 75th percentile, site-wide and for the slowest pages.
- A 2.3 KB script (1.2 KB gzipped) that works behind the page cache; visitors are counted with a daily salted hash that cannot be followed across days. JSON summary at
GET /pursae/v1/analytics.
Overview, moderation, members, badges Campfire theme with its demo content💬 Pursae Forum


A bbPress-class discussion board that renders inside any theme (Forums in the admin menu):
- Categories, forums, topics and replies, pinned and closed topics, search, profiles and a member list — all plain forms, no JavaScript.
- Membership on the front end: email sign-up with confirmation, "Continue with Google" (OAuth with PKCE), an account page with profile photos.
- Levels and badges: points for topics and replies, six default levels, rule-based and hand-awarded badges with icons or images.
- Moderation: approve, pin, close, spam, trash and block from the post itself or the admin queue; first-post moderation, flood and hourly limits.
- Themes: four forum themes with demo content (Campfire, Devboard, Guild Hall, Study Circle),
--pf-*design tokens and per-view template overrides; works with Pursae Web Builder and Pursae Multi Language. REST API at/wp-json/forum/v1: public read routes (forums, topics, replies, tags, stats, online counts and more), plus community write routes — a view beacon and presence (no login), and likes, reports, follows, solutions, previews and drafts for logged-in members (cookie +X-WP-Nonceor an Application Password). See the endpoint list.
All features → · Making a forum theme →
🗂️ Custom Fields · 🌍 Multi Language · 📝 Contact Form



🚧 Maintenance · 💾 Backup Manager


🤖 AI agents (MCP)
![]() Tools › AI Access — endpoint, client configs, connected apps, activity log |
A built-in Model Context Protocol server at
|
🔁 WordPress compatibility
- Admin: the WordPress admin markup and CSS 1:1 under
/wp-admin/(old.phpURLs still work). - Editors: the real block editor (
@wordpress/*bundles) and a built-in Classic Editor. - REST API:
wp/v2with cookie + nonce and Application Passwords;wc/v3with Commerce on — REST docs. - Content: WXR import and export under Tools; WooCommerce's product CSV under Products.
- Not supported: PHP plugins and PHP themes (themes are Go templates with a
theme.jsonmanifest) and multisite.
🐹 Go architecture
- One static binary (
CGO_ENABLED=0) with the admin, the editors and the bundled themes embedded. - gin for HTTP, pgx on PostgreSQL 17 (14+ works); migrations run on start.
- Plugins run as WebAssembly in wazero — no cgo, no separate runtime.
- Details: What is Pursae · binary install.
🧩 The WordPress ecosystem without PHP
- Plugins are Go compiled to signed Wasm, sandboxed and permission-gated — plugin docs, signing.
- Built in: Commerce, Web Builder, SEO, Cache, Security, CDN, Headless, Cookie, Pixel, Analytics, Forum, SMTP, Custom Fields, Multi Language, Contact Form, Maintenance, Backup Manager, Classic Editor (table below; what each replaces).
- Themes are zip packages of templates and assets with no code in them — theme packages; a marketplace of both on the Hub.
📊 Performance benchmarks
Same content (1000 posts, 200 products), Twenty Twenty-Five, same container limits; WordPress 7.1.4 + PHP 8.3 OPcache against Pursae 0.1.9, Apple M2 Pro under Docker, 2026-11-09:
| | WordPress | Pursae | |---|---:|---:| | Single post, no page cache | 58 req/s | 394 req/s | | Single post with the usual plugins (Woo, Yoast, Polylang, ACF, Elementor, CF7 vs built-ins) | 19 req/s | 232 req/s | | DB queries, home page with those plugins | 139 | 16 | | Memory idle, whole stack | 233 MiB | 95 MiB |
Cached pages tie (WP Super Cache + nginx ≈ Pursae Cache), cold start is the same, and WordPress' page cache serves
search while Pursae's does not. Method, every config, all tables and make bench: benchmarks.
🛡️ Security
- Core secure by default: argon2id, login throttling, nonces, CSP and security headers, no account enumeration, sandboxed uploads — security.
- Plugins are signed and sandboxed; a site installs only packages whose signature it trusts.
- Multi-role users: capabilities are the union of the roles, with per-user allow and deny — deny wins.
- Pursae Security adds 2FA, lockouts, a custom login URL and an activity log — features.
📦 Installation & migration
- Docker (Quick start) or one binary against your own PostgreSQL — install the binary.
- From WordPress: export with Tools › Export (WXR), import with Tools › Import here — posts, pages, terms, comments, menus, and media fetched from their public URLs. Products move with WooCommerce's product CSV.
- Users' passwords, settings, PHP plugins and themes do not move — content export and import.
- Pursae to Pursae: Backup Manager moves a whole site in one archive — Backup Manager.
🔒 What Pursae sends to hub.pursae.com
Every production build talks to Pursae Manager at https://hub.pursae.com. It is how a site gets updates, the theme and plugin marketplace and licenses. Here is everything it sends, plainly:
| When | What | |------|------| | Once a day (and a minute after a core update) | the site's URL, Pursae version, language, OS and CPU architecture, license key (if you entered one), active theme, and the list of installed plugins and themes with their versions, whether they are active, and where they came from (built in, from the Hub, uploaded) | | As it happens (sent in batches) | what was done with packages: a plugin installed, updated, activated, deactivated or deleted; a theme installed, updated, activated, previewed or deleted; a demo imported; the core updated — each with the slug, version and time | | On every request to the Hub | the site's URL and license key as headers; the Hub also sees the server's IP address, as any web server does |
The Hub uses this for the numbers you see on it (theme and plugin download and install counts, which versions sites run) and to decide what a license unlocks. **It never receives your content, users, e-mail addresses, passwords, visitors, orders or anything else from your database.**
What a site gets back:
- Updates: the newest Pursae release, offered under Dashboard › Updates and installed with
- Plugins: Wasm plugins from the marketplace, each signed; by default a site installs only
- Themes: the theme library with demo content, checked against their SHA-256.
- Licenses for pro and beta packages, and the product logo.
WPGO_HUB=off in the environment (with Docker: in docker/.env) and restart;
the site then sends nothing to hub.pursae.com. We do not recommend it: the site gets no update
notices or one-click updates — security fixes included —, no marketplace, no signed plugins and no
licenses, and you have to replace the binary yourself for every release. While it is off, every admin
page says so; remove WPGO_HUB and restart to get updates again.
🛠️ Build on it
| | |
|---|---|
| 🧩 Plugins — Go → signed Wasm, hooks, REST, settings | docs/developer/plugins |
| 🎨 Themes — Go templates + theme.json | docs/developer/themes |
| 💬 Forum themes — Pursae Forum wrapper, view overrides, --pf-* tokens | docs/developer/themes/forum.md |
| 🔗 REST API — wp/v2 + plugin routes, Application Password scopes, OAuth 2.1 | docs/developer/rest-api |
| ⌨️ Command line — pursae (alias wpgo), WP-CLI style pursae post list, pursae help | docs/developer/operations/cli.md |
| 🤖 AI agents — MCP server, wpgo mcp bridge, tool list | docs/developer/operations/ai-mcp.md |
| 🏪 Hub — marketplace, updates, licenses | docs/developer/hub |
| ⚙️ Operations — config, TLS, backups, cron | docs/developer/operations |
📚 More
Full guide (install, configuration, troubleshooting, project layout) · Developer docs · License · Notice
GPL-2.0-or-later. "WordPress" is a trademark of its owner; Pursae is not affiliated with it.

















