CEDX
Marketplace
Add capability without adding another login
ISV extensions and connectors that respect CEDX identity and data contracts.
Listing bar
Extend without forking the estate
Marketplace is for ISV extensions and connectors that respect CEDX identity and data contracts. It is not the Partners PRM product at /partners/, and it is not a second app store of unrelated tools.
Customers install industry extensions, connectors, and templates that land on the same login. Builders apply as ISV partners, pass security review, and prove the extension in sandbox before production listings.
Marketplace purpose
What marketplace is for
Marketplace exists as part of the CEDX resource library next to Academy, product pages, and customer scenarios. Content stays operator-grade and tied to live software wherever a product claim is made.
Use this surface when its job matches your moment: learning, release notes, live sessions, listings, or essays. Do not expect one page to replace the whole estate evaluation path.
Editorial and product truth rules still apply: no parallel mockup universe, no thin listicles, no bait-and-switch demos. If a session or essay points at a product, open the live app and test the claim.
Partners and customers share public surfaces; partner-only depth remains in the portal after approval. That split keeps evaluation open without giving away co-sell assets.
How to use it
Practical path
Start from the hero metrics and section map, then deep-link into product catalog or Academy as needed. Bring operators when decisions depend on queue design rather than feature checkboxes alone.
Capture decisions in your pilot doc or joint plan so sessions and essays produce artifacts. Without artifacts, content becomes entertainment.
Escalate to contact for estate map, partner intro, or private sessions when public material is not enough. Include industry, products, timeline, and constraints so routing is correct.
Related hubs always include Customers, Partners program, Developers, and Support where relevant. The estate is one system; the library is one map.
Standards
Quality bar
Live product when product is claimed; honest illustrative language for scenarios; written FAQs for procurement paste. Security and identity questions get real answers or a path to the security pack.
No paid directory ranking; no calendar filler essays; no webinars that cannot open the app. Violations are process bugs we fix rather than exceptions we normalize.
Accessibility and clarity beat cleverness; operators should finish a section with an action. If a section has no action, it is incomplete.
Refresh cadence follows product change, not an arbitrary publishing calendar. Material changes may appear in News when they affect programmes.
Next step
Leave with an action
Pick one product to open live, one Academy module or scenario to read, and one conversation to book if needed. Three actions beat thirty open tabs.
Share links with the people who own the queue so evaluation is not stuck in a single inbox. Estate programs fail when only one champion understands the map.
Partners: complete enablement and clean portal hygiene before promising Premier outcomes internally. Customers: write the retire list before config week one.
When ready, use contact with context both sides can act on within two business days for most intro and map requests. Serious inputs get serious routing.
For customers
What you install
Industry extensions
Vertical workflows on core apps.
Connectors
Bring adjacent systems into the graph.
Templates
Starter configs for common motions.
For builders
How to list
Apply as ISV
Partner path plus security review.
Use the API
Identity and data contracts.
Sandbox first
Break things without breaking prod.
Customer journey
Install with confidence
Browse
Industry and connector catalogs.
Review
Security and identity notes.
Sandbox
Try before production.
Support
ISV first-line; platform via CEDX.
Builder journey
List with discipline
Partner apply
ISV path under partner program.
Contracts
Identity and data rules.
Review
Security gate before list.
Operate
Versioning and support expectations.
Platform
Extend without forking the estate
If it needs a second login for the same user, it is not done.
FAQ
Marketplace: practical questions
Straight answers before you book time or open a ticket.
Is Marketplace the Partners app?
No. Marketplace lists extensions. CEDX Partners (/partners/) is channel PRM software.
Who supports a listed app?
The ISV first-line; CEDX supports platform contracts.
Can listings require a second login?
No. Same human, same estate identity — or redesign.
Put this into practice
Open the relevant product, bring the operating question, and leave with a named next action.