Decide what data is exposed, who can access it, and how it is shaped. Self-hosted, open-source, built for developers who are done rebuilding the same things from scratch.
SaaS CMSes are convenient until they are not — pricing changes, data lives on someone else's server, and migrating out is painful. WordPress has powered the open web for 20 years. Application Layer gives it the application infrastructure it was always missing.
Authentication, data shaping, API scoping, event automation, security hardening: the features you have been assembling from a dozen plugins on every project, now in one coherent layer — with a clean admin UI, a full hooks API, and zero vendor lock-in.
WordPress exposes a lot by default — user data, internal meta, raw field structures. Application Layer lets you audit every route, globally disable HTTP methods, post types or taxonomies, and in Pro, decide field by field what leaves your server.
Stop massaging responses client-side. Apply sitewide transforms for free: resolve embedded terms, flatten rendered wrappers, strip domain from URLs. Pro adds per-property rename, remap, and fully custom schemas.
One WordPress installation. Multiple applications — each with its own auth method, data view, rate limit, and secret. The same content, safely served to different consumers.
No subscription required for the core feature set. No telemetry. No external dependency. Your WordPress, your server, your rules.
Use WordPress as the content back-end for a React, Next.js, Nuxt, or mobile app. Enforce authentication, transform responses to match your front-end schema, and keep WordPress internals invisible to consumers.
Self-host your content infrastructure. Keep editorial teams on a familiar interface while giving developers a clean, controlled API — without recurring costs or third-party data custody.
Serve multiple client applications from a single WordPress back-end. Isolate authentication, content views, and rate limits per application — each client sees only what they are entitled to.
Serve content in multiple languages across separate websites or applications, each with its own REST API scope, response schema, and delivery configuration.
| Feature | Free | Pro |
|---|---|---|
| REST API route explorer | ✅ | ✅ |
| Authentication & Rate Limiting | ✅ | ✅ |
| Properties & Models (sitewide transforms) | ✅ | ✅ |
| Routes: global method / post-type / taxonomy disable | ✅ | ✅ |
| WordPress Security Hardening | ✅ | ✅ |
| Webhook (single, post lifecycle events) | ✅ | ✅ |
| Hooks & Filters API | ✅ | ✅ |
| Multiple Applications | — | ✅ |
| IP Filtering (blacklist) | ✅ | ✅ |
| IP Filtering whitelist + CIDR + country blocking | — | ✅ |
| Collections & Sort Order | — | ✅ |
| Properties & Models (per-property control + custom schemas) | — | ✅ |
| Settings Route schema editor (ACF options, menus) | — | ✅ |
| Per-Route Policy (per-route disable, redirect, user restriction) | — | ✅ |
| Automations | — | ✅ |
| Multiple Webhooks (unlimited, per application) | — | ✅ |
| Email Templates | — | ✅ |
| Request Logs & Audit Trail | — | ✅ |
The next modules in development:
WooCommerce Bridge
Headless access to WooCommerce — products, cart, checkout, and Stripe/PayPal payments — through the same application security layer.
Forms Bridge
Secure form submission endpoints with entry management, configurable data retention, GDPR options, and AES-256 encryption. Compatible with WPForms and Contact Form 7.
Site Import / Export
Cherry-pick content and configuration to sync, migrate, or replicate between WordPress installations through the REST API — powered by the same field mapping already in Models.
Editorial Workflow
Authors scoped to their own posts and media. Validation workflows, co-authoring, post duplication, post type conversion, and multi-author taxonomies — for production editorial teams.
Static Pages & Custom URLs
Spin up static landing pages on any domain directly from WordPress. Choose any URL pattern for posts and pages — free from WordPress's default URL constraints.
Database Encryption
An optional encryption layer for sensitive data stored in wp_options and custom tables — transparent to the application.
