Service Partner
Implementation, training, support, governance, and enterprise adoption.
Dify Implementation Lane
Dify-ready agent systems with the policy layer attached.
CREATE SOMETHING packages Dify as the visible agent runtime, MCP as the tool boundary, and Policy OS as the approval, runbook, and evidence layer. The current track is to apply for Dify Service Partner, Marketplace Partner, and Affiliate participation without claiming approval before it exists.
Build. Validate. Disclose. Convert.
Marketplace Partner
Templates, plugins, and repeatable Dify plus MCP solutions.
20 paid conversions
The first affiliate economics milestone after Dify accepts the application.
Proof Packet
Dify is already part of the operating model.
The partner packet is grounded in repo-owned artifacts: Dify inventory, MCP coverage, public trust evidence, DSL snapshots, Infisical references, and Braintrust eval coverage. Public materials use sanitized evidence only.
Public Guide Agent
A public Dify guide agent backed by read-only MCP cards and trust catalog evidence instead of private traces.
Abundance Delivery
A Dify-backed delivery surface with agent inventory, eval coverage, and production-oriented evidence controls.
Transcript To Notion
A repeatable Dify plus MCP workflow pattern for turning media intake into structured operating records.
Marketplace Creator Pipeline
A Dify-supported marketplace workflow that keeps review context, tool access, and policy boundaries inspectable.
Partner Evidence
The proof is artifact-backed, not a pitch deck.
The Dify application can reference generated inventory, coverage, trust, and Policy OS records without exposing private traces or credentials.
dify_inventory.md
Codified Dify agents, server cards, manifests, DSL snapshots, and eval references.
mcp_coverage.md
Coverage states for ready, intake-ready, brokered, dormant, and missing Dify MCP cards.
trust_catalog.md
Public proof that intentionally excludes raw traces, private hubs, and credential references.
policy_os.md
The package definition for approvals, runbooks, golden tasks, tuning, and escalation.
Partner Ecosystem
Dify is the agent lane inside a broader partner stack.
The public posture should keep each vendor role precise: Dify carries the agent surface, Cloudflare carries the runtime substrate, and Notion carries the operator workspace.
Agent runtime
Dify
Primary live laneService Partner first, Marketplace Partner as proof, Affiliate as the self-serve acquisition lane.
Infrastructure runtimeCloudflare
Infrastructure proof laneWorkers, Pages, D1, and edge delivery are the substrate for governed MCPs and client review surfaces.
Operator workspaceNotion
Solutions Partner targetConsulting Partner first, templates and builders as proof, Technology Partner after a public integration exists.
Funnel Shape
One Dify route for three high-intent audiences.
Ship Dify apps with real tool contracts.
Start with MCP server cards, Dify DSL snapshots, smoke checks, and setup steps that a new user can run.
Run agents with approval states attached.
Policy OS defines what can run, what needs a human, what stops, and what evidence gets recorded.
Package repeatable Dify delivery.
Turn proven workflows into templates, plugin candidates, client-safe case studies, and affiliate-ready content.
Learn Validate Adopt
Dify plus MCP control plane
Explain how Dify becomes the visible agent surface while MCPs carry tool access and Policy OS carries boundaries.
Agent eval gates
Show API health, expected tool use, forbidden tool use, secret refusal, latency, and write confirmation checks.
Client-safe delivery evidence
Route self-serve buyers through disclosed affiliate surfaces after acceptance and route implementation buyers through the partner lane.
Affiliate Lane
Self-serve adoption stays separate from partner deals.
Current Dify links are direct reference links. After acceptance, approved affiliate links can be added with disclosures on declared domains and channels. Implementation, reseller, enterprise, and co-sell opportunities stay in the partner lane.
Compliance
The public posture is intentionally conservative.
The goal is to make CREATE SOMETHING ready for Dify approval without implying endorsement, certification, or undisclosed affiliate economics.
- No official Dify partner or certified provider claim before approval.
- No affiliate link replacement until the affiliate application is accepted.
- No raw Braintrust traces, private hub records, broad connector surfaces, or credentials in public proof.
- No Dify commercial brand asset use in sales collateral without explicit authorization.
Next Step
Book Mapping SessionMap the first Dify plus MCP workflow.
Bring the workflow, source systems, and approval owner. CREATE SOMETHING will map the Dify surface, MCP contracts, policy states, and evidence needed for a partner-grade delivery.