WordPress owns durable state
Pairing, consent, Space, snapshots and aggregate counters stay in WordPress.
See scopes and storage ↘SET PARTNER SAFE SPACE VIA GPL WORDPRESS CONNECTOR
Partner directory. WordPress control.
PartnerOpen is a GPL WordPress Connector that makes a Host-controlled partner Space on your website. Collaborate with the best Creators while the Host keeps full control. Connect to the existing PRM (Partner Relationship Management) and CRM (Client Relationship Management), or use aggregate placement metrics to keep the operational workflows you already run.
M1 / AVAILABLE NOWWORDPRESS-OWNEDCONSENT-FIRSTANY CREATOR
- 01SAFEThoughtful participant protection, explicit consent and a visible WordPress boundary.
- 02EASY TO SETInstall the GPL Connector without external tooling or services on the Host side.
- 03FULL ADMIN LOGSAudit connection, access, consent, publication and pause events without visitor dossiers.
GPL-2.0-OR-LATER · FREE FOR THE USER · ANY COMMERCIAL TERMS · NO VISITOR DOSSIERS
PARTNEROPEN / CONNECTORREADY
WORDPRESS CONNECTOREasy setup
SAFEEASY TO SETFULL ADMIN LOGS
WordPress site connected v0.1.0
✓CONSENT GRANTED
✓CREATOR INVITED
FULL ADMIN LOGSSAFE METADATA
creator.invitedSite admin · accepted
NOWsnapshot.publishedSpace / verified
02mglobal_pause.changedHost control · ready
14m SAFE · EASY TO SET
FULL ADMIN LOGS · NO VISITOR DATA
00 / TRUST YOU CAN VERIFY. FOR BOTH PARTIES
Trusted Space via transparent collaboration.
PartnerOpen provides a safe place to work: content stays controlled by the owner while the Creator keeps publication freedom. Host controls the site boundary, not Creator content. Logs, a kill switch, safe Spaces and thoughtful participant protection make the trust boundary visible to both parties.
Independent Creator interface
PartnerOpen hosts the collaborator control panel and dashboards. No need to host additional data, flows or security tooling on your side.
See the setup path ↘Pause or disconnect
Global Pause hides public routes. Disconnect revokes the Connector secret and requires fresh pairing.
See owner controls ↘No visitor tracking provided
No cookies, IP addresses, fingerprints, visitor IDs or visitor-level click events. Just verified aggregate usage data.
See the data boundary ↘Technical evidence: Connector manifest ↗ · health endpoint ↗ · full consent scopes ↘ · privacy boundary ↗
00 / SAFE COLLABORATION
Different roles. One trusted space.
Provides the page to the Creator and works on their own website.
Brings the content and the commercial relationship to the page.
PartnerOpen provides the framework, consented publication records and verified aggregate data. Payment execution, legal terms and settlement remain between the participating parties under their own agreement, using that transparent data basis.
Together: grow traffic and get mutual benefits from it.
01 / PARTNER SPACE + PRM ENDPOINT
Pro? Connect your PRM and CRM — without replacing them.
Use PartnerOpen as the partner-facing framework for your ecosystem or set a new one. Publish the right partner Space, control access and visibility, and connect it to the PRM and CRM tools you already use.
01
Partner-facing Space
Publish a branded directory, partner profiles and approved content without changing the systems that run your business.
PUBLIC SURFACE02
PRM endpoint
Use PartnerOpen as a lightweight endpoint layer for the partner-facing surface while your existing PRM keeps its operational workflows.
ENDPOINT-FIRST03
CRM connection
Keep pipeline, ownership and revenue operations in the CRM you already use; PartnerOpen stays focused on the Space.
STACK-ALIGNEDDesigned to work alongside Partnero, Introw and PartnerStack or use PartnerOpen MCP.
PartnerOpen: light tooling to the partnership networks world.
01SIMPLE INSTALL02NO EXTERNAL TOOLING03FREE FOR THE USER04ANY COMMERCIAL TERMS
| Dimension | PartnerOpen | Kiflo Partner Directory ↗ | PartnerPage.io ↗ |
|---|---|---|---|
| Primary job | Host-controlled partner Space and lightweight PRM endpoint layer. | Public directory backed by partner data and PRM workflows. | Public partner directory builder. |
| Public profiles and directory | Public Space, profiles and approved partner content. | Public partner profiles, search and filters. | Partner listings and profile pages. |
| Partner self-service and approval | Creator publishes through the signed API, MCP or GUI; Host controls the boundary. | Partner profile self-edit with approval. | Partner-owned listings. |
| PRM / CRM role | Connects to the existing PRM and CRM instead of replacing them. | Directory and partner-management workflow. | Directory-first; referral capture is central. |
| Host control | Scopes, visibility, Global Pause, consent and disconnect. | Directory and PRM configuration with approvals. | Directory configuration and listing management. |
| Deployment / ownership model | WordPress Connector plus a host-controlled public surface. | Managed directory and PRM product. | Branded directory product on the customer domain. |
| Best fit | Own the partner Space and connect the existing stack. | Directory plus partner operations. | Launch a public partner directory quickly. |
A positioning comparison based on public product material, not a claim that one product replaces the others. Confirm current features and pricing with each provider.
02 / EASY WORK WITH PARTNEROPEN
A simple WordPress setup for a durable, flexible framework.
Install
Install the GPL PartnerOpen Connector in WordPress. Safe, transparent and local by default; no external tooling or services required on the Host side.
Set the Space and Creator
Choose a prefix and onboard a named Creator directly by email. No open registration, separate database or OAuth integration is required on your side.
Agree the boundary
Review the consent scopes, owner controls and collaboration terms before any connected data exchange.
Publish by signed API, MCP or GUI
The Creator publishes through the signed API, the simple MCP Connector or PartnerOpen GUI.
Keep global control and trace
The Host keeps Global Pause, consent withdrawal and disconnect. PartnerOpen keeps full admin audit logs, not visitor-level logs.
03 / HOST CONTROL / CREATOR FREEDOM
Full control for the Host. Freedom for the Creator.
Owner does not moderate, partially delete, hide or change Creator data: the control is Global Pause.
Global Pause
One switch hides every public Connector route under the configured prefix. It does not erase local data, and it does not let the Host edit Creator information.
Withdraw consent & disconnect
Stops data exchange, revokes the Connector secret and requires fresh pairing and consent to reconnect.
CREATOR CONTROL
Withdraw consent & disconnect
Creator can withdraw their consent and disconnect their participation. Connected Creator data is hidden until fresh consent is given.
CREATORTHE OWNER MANAGES
- ✓Install the Connector and set a prefix and Creator contact during setup.
- ✓Grant or withdraw each consent scope with its purpose and retention visible.
- ✓Turn Global Pause on or off for the public Connector surface.
- ✓Withdraw consent and disconnect the site; local snapshots remain until explicitly deleted.
THE OWNER DOES NOT MANAGE
- —Edit the Creator's Space content, links or agent-context files.
- —Operate the Creator's account or browser editor.
- —Manage individual Space publishing controls or Creator operations.
- —Receive a per-visitor profile, visitor-level event stream or hidden destination data.
- —Delete administrative audit proofs through normal content operations.
05 / LINK TRANSPARENCY
A visible path from placement to destination.
SAME-ORIGIN RESOLVERNO CLOAKING
/partneropen/go/l1/hero→https://destination.example/pathThe rendered HTML points to the same-origin resolver. The resolver checks pause state, Space status, link status, HTTPS allowlists and placement scope before redirecting.
Each outbound link includes a visible disclosure and rel="sponsored nofollow noopener". The Connector never emits a raw external href from a snapshot and never hides the commercial relationship.
- ✓Disclosure travels with the link
- ✓Resolver can return 404 without redirecting
- ✓Destination host is validated before use
06 / AGENT-CONTEXT PACK
Canonical files for a public Space.
PUBLIC OUTPUTSALLOWLISTED
01
AGENTS.mdcanonical02
llms.txtpublic03
ai-context.jsonpublic04
manifest.jsonpublic05
sitemap.xmlpublicThe Connector generates AGENTS.md as the canonical agent-context file. /agents.md is only a 308 alias. The pack also includes llms.txt, ai-context.json, manifest.json and sitemap.xml.
The pack is assembled from a positive field allowlist: each section and block type contributes only named public fields — Space slug, title and status, SEO title, description and canonical, block headings, labels, questions, answers, columns and rows, plus resolver identifiers. Everything else, including destinations, emails, identifiers, payout data and unknown future keys, is dropped rather than filtered, and a deny-list pass remains only as defence in depth.
Read Connector manifest ↗07 / NEVER COLLECTED BY PARTNEROPEN
Keep visitors safe. Just data.
PartnerOpen reports only verified aggregate usage data. No visitor dossier, hidden audience layer or visitor-level activity is created.
AGGREGATE_METRICS90-DAY RETENTION
dateYYYY-MM-DD
placementidentifier
countinteger total
PartnerOpen can provide aggregate placement data as a basis for the agreed share calculation. It does not process payments; settlement follows the legal agreement between participants.
NO VISITOR TRACKING PROVIDED
- —cookies
- —IP addresses
- —user agents
- —device fingerprints
- —unique visitor identifiers
- —visitor-level click events
Just proven usage data, without a hidden audience layer.
08 / TWO USE CASES
PartnerOpen use cases.
USE CASE 01 / AVAILABLE NOWPACKAGE v0.1.0
Host collaborators for free and take a share.
- Set Connector + get Creators: the Host keeps durable pairing, consent, Spaces, snapshots and counters in WordPress.
- This site: landing, health, consent-scope and Connector-manifest APIs; no tenant database.
- Reference client: pair, sign and publish snapshots, then read status and aggregate metrics.
- Creator paths: signed API, MCP Connector and PartnerOpen GUI are available after the Host sets the boundary.
PartnerOpen provides the data and share-calculation basis. Payments and settlement remain outside PartnerOpen under the legal agreement with the network or direct participant.
See signed publish flow ↗USE CASE 02 / MILESTONE 2 / BY REQUESTNETWORK
Set the publishing network.
Get Hosts for your content at scale: work with any number of Hosts simultaneously, assign Creators through the Organization → Site → Space hierarchy, and review the administrative event trail through the PartnerOpen network UX.
Milestone 2 · by request09 / SIGNED API / MCP / GUI
Publish safely. Choose your surface.
Pair once
POST /wp-json/partneropen/v1/pair consumes a one-time code and returns the Connector secret once.
Signed API
PUT /spaces/{space}/snapshot sends the canonical typed snapshot with HMAC-SHA256 headers.
MCP Connector
Use the simple MCP Connector as an agent-facing publication path while the Host keeps the WordPress boundary.
PartnerOpen GUI
Invite a Creator by email, scope access to Sites or Spaces, publish through the external UX and inspect full admin audit logs.
SIGNED PUBLICATIONVERIFIED
x-partneropen-sitetimestamp + nonce + signatureWordPress confirms the published snapshot.INSTALL THE CONNECTOR
Start with the GPL package.
Download the partneropen-connector-0.1.0.zip release package, then upload it in WordPress under Plugins → Add New → Upload Plugin. Activate it, set a prefix and Creator contact, review the six scopes, and connect without external tooling or services on the Host side.
Verify SHA-256 checksum ↗PACKAGEpartneropen-connector-0.1.0.zip
LICENSEGPL-2.0-or-later
REQUIRESWordPress 6.5 · PHP 8.1
VERSION0.1.0
QUESTIONS / ANSWERS
Straight answers about the boundary.
Does PartnerOpen host a partner editor today?+
Yes. PartnerOpen GUI is available as a Creator-facing publication surface alongside the signed API and MCP Connector. The public landing remains stateless; the GUI carries the external collaboration experience.
What does the Connector store?+
The Connector stores pairing, consent, Space, published snapshot and aggregate counter state in WordPress options. WordPress remains the durable system of record for the public runtime.
Can the Creator publish without a Host step?+
Yes. After setup and the required consent scopes, the Creator publishes through the signed API, MCP or PartnerOpen GUI. The Host keeps Global Pause, consent withdrawal and disconnect as the public overlay.
Are links redirected invisibly?+
No. Every outbound link uses a same-origin resolver, shows a disclosure and renders rel="sponsored nofollow noopener". Raw external href values are not emitted by the Connector renderer.
What happens when consent is withdrawn?+
The Connector stops outbound exchange, revokes its site secret and marks the connection disconnected. The latest local published snapshot stays in WordPress until the owner explicitly deletes it.
Does PartnerOpen process payments?+
No. PartnerOpen provides publishing data and the basis for an agreed share calculation. Payments and settlement remain between the Host, Creator or network under their legal agreement.
What can Milestone 2 (M2) include?+
Milestone 2 is the publishing network package: multi-Host distribution, Organization → Site → Space administration, network health and the network-level audit flow. It is available by request; MCP and PartnerOpen GUI are available publication paths now.
Is Milestone 2 available now?+
The publishing network package is available by request through the Connect with us to discuss path. The base Connector, signed API, MCP Connector and PartnerOpen GUI are available now.
How is a Creator invited?+
The Site admin enters the Creator email, assigns Site or Space access, and sends an invitation. The Creator enters through a short-lived passwordless magic link; there is no open registration.
What do the full admin logs contain?+
The audit timeline contains safe administrative events such as connection, Creator access, consent, draft, publication, pause and disconnect results. It does not contain cookies, IP addresses, visitor profiles or visitor-level activity.