Download RuleFence
Start with one agent.
Keep every permission explicit.
Install the local-first control plane for WordPress agents. Begin free with one narrow Ability, inspect the full decision path, and expand only when the work earns more authority.
RuleFence Free
One clear starting point for learning the governed request path on a WordPress site you control.
Download plugin ZIPFree plan · WordPress plugin ZIPWHAT YOU ARE INSTALLING
Managed identityKnow which agent is acting and why.
Native WordPress authorityExisting permissions remain the ceiling.
Explicit Ability decisionsAllow, review, or block the exact request.
Readable evidenceKeep decisions and outcomes inspectable.
Before you install
Three things you need. Nothing hidden.
RuleFence installs as a WordPress plugin and begins from the authority your site already recognizes.
A WordPress site you manage
Use a site where you understand the users, roles, plugins, and operating environment.
Permission to install plugins
The WordPress administrator performing setup must be allowed to upload and activate a plugin ZIP.
A safe place to begin
Start with one low-consequence workflow. A staging environment is recommended when available.
Install in WordPress
From ZIP file to first governed request.
The installation is familiar. The important part is what you do after activation: grant one useful permission deliberately.
Upload
Open Plugins → Add Plugin → Upload Plugin and choose the downloaded ZIP.
Activate
Activate RuleFence and open its control plane in WordPress.
Register
Create one managed agent identity tied to its purpose and environment.
Grant
Allow one narrow WordPress Ability and inspect the resulting decision path.
Your first safe boundary
Do not begin by granting broad access.
Start with visibility, one managed identity, and one useful Ability. Confirm the native WordPress authorization, policy decision, outcome, and evidence before adding more.
- Name the agent and its purpose
- Choose the smallest useful Ability
- Keep consequential work behind review
- Verify what actually happened
MANAGED IDENTITYContent AssistantStaging
What Free is for
Learn the real control model—not a decorative demo.
Use Free to understand how governed agent access behaves before production consequence or multi-site operations enter the picture.
See managed identity
Make the acting agent explicit instead of treating automation as an anonymous connection.
Trace one request
Follow identity, authorization, policy, decision, execution, and evidence as one path.
Preserve the ceiling
Confirm that a plugin cannot silently create authority WordPress did not grant.
Read the outcome
Keep the decision and what actually happened understandable to the operator.
Install with confidence
Use the right help before expanding access.
The fastest safe path is documented. When your site behaves differently, bring the full request context to support.
Download questions
Know what happens before you install.
Begin with the smallest safe boundary and keep WordPress authority visible throughout setup.
Does RuleFence require an AI API key?+
No required AI API key is needed for the local-first control core. Any separate agent or AI service you connect may have its own requirements.
Does installing the plugin grant an agent access?+
No. Installation creates the control plane. A managed identity and explicit WordPress Ability still need to be configured.
Should I begin on a production site?+
Begin with low-consequence work. Use a staging environment when available before granting authority over production workflows.
Where should I go after activation?+
Open Getting Started and follow one agent and one safe Ability through the complete decision path.
Start with one useful permission
Download free.
Keep WordPress in control.
No required AI API key. No per-call fees. Native authority remains the ceiling.