Engineering Readiness Brief

Use this brief to estimate what your engineering team needs to build to connect Partner Fleet's
App Marketplace to your product.

The App Marketplace ships in two deliveries, and you pick one (see App Marketplace:
Overview → "Choose your delivery"):

• Embedded — the marketplace renders in an iframe inside your product.
• Gated — the marketplace is a standalone site at its own domain, behind your single
  sign-on.

Most of the engineering work is shared. The one area that differs is how you connect the
marketplace to your product — embedded uses an embed script; gated uses a domain plus an SSO
gate. This brief calls out which is which.

Effort at a glance. Connecting the App Marketplace takes 8–16 hours of engineering for
most teams (either delivery). If you don't yet issue JWTs, budget 24–40 hours. You
configure the rest — marketplace UI, branding, content, personalization, and analytics — in
Partner Fleet's admin without code.

What this document covers

The integration has three areas. Two are the same for both deliveries; the middle one branches.

1. Authentication (shared)

Partner Fleet identifies your users with a signed JWT (embedded), or a SAML assertion (gated). Each delivery uses its own SSO mechanism (covered in section 2).

What Partner Fleet provides

• JWT shared-secret management in the admin UI
• Built-in Test Tools (Generate Test Token, Decode & Verify Token) to validate without
  touching your backend
• Ruby, Node.js, and Python reference implementations in the help docs

What your team provides

• (Embedded) a signed JWT (HS256) with the required claims — standard fields your auth system likely
  already stores: email, first/last name, account identifier, and account name.
• (Gated) your Identity Provider configured for IdP-initiated SAML SSO, plus
  its IdP SSO URL and signing certificate.

Effort: 2–4 hours for most teams. Near-zero if you already issue JWTs.

2. Connecting the marketplace (differs by delivery)

This is the one area where the work depends on your delivery.

Embedded — Frontend Embed

The marketplace embeds through a lightweight JavaScript loader (the embed script), available
in the admin under Developer Settings → Embed Script.

• Partner Fleet provides: the auto-generated embed snippet (with your CNAME and URLs), CNAME
  configuration with SSL, an Allowed Domains whitelist, and a setup checklist with live status.
• Your team provides: a page/route where the marketplace appears (e.g. /integrations), a
  CNAME DNS record pointing your subdomain (e.g. marketplace.yourcompany.com) to
  proxy.partnerfleet.app, and the token wiring. Because it's served from your own CNAME, it's
  first-party and needs no CSP changes.
• Effort: 2–8 hours (place a <div>, include the script, add the DNS record, wire the token).

Gated — Domain + SSO gate

A gated marketplace has no embed script, no <div>, and no iframe. Instead you point a
domain at the store and implement the sign-in gate.

• Partner Fleet provides: the hosted gated store, the sign-in gate, the SSO callback that
  verifies your signed assertion, and all the session/redirect security around it.
• Your team provides:
  1. a domain (DNS/CNAME) pointed at the gated store; and
  2. the SSO gate — a SAML IdP configured for IdP-initiated SSO (it authenticates the user and POSTs a signed SAML assertion to Partner Fleet’s ACS).
• Effort: 2–8 hours (point the domain, configure SAML, confirm the round-trip). See Gated Marketplace: SSO & Setup for the full flow.

3. Status Sync & Visibility (shared concept, different mechanism)

The marketplace personalizes what each user sees — which listings appear, which CTAs render, and
which integrations show as installed.

How you pass integration status depends on your delivery:

• Embedded — the embed script's integrations array (client-side), and/or the Core API.
  (postMessage is available for embedded CTAs.)
• Gated — the Core API (server-to-server). There's no embed script and no postMessage,
  so the Core API is the primary way to sync install state from your backend.

Effort: 4–16 hours depending on whether you already track integration statuses. If your
system already knows which integrations each customer has, this is minimal.

Total effort summary

What you do not need to build

Partner Fleet provides the marketplace infrastructure — either delivery. Your team only provides
the connection points. You do not build:

• Marketplace UI, search, or filtering logic
• Integration listing management or CMS
• Visibility or access-rule engine
• Conditional CTA matching logic
• Analytics or usage-tracking infrastructure
• Partner onboarding or listing-submission workflows
• (Gated) the sign-in gate, session handling, or redirect security — Partner Fleet owns that

Quick readiness checklist

Share this with your engineering lead.

Both deliveries:

• Does your app authenticate users?
• Can your backend generate a signed JWT (HS256)? (Embedded; gated uses SAML — see below.)
• Do you track which integrations each customer has installed? (Needed for install-state badges;
  the marketplace still works without it.)

If embedded:

• Can your frontend include an external JavaScript file and render a <div>?
• Can you add a CNAME pointing a subdomain to proxy.partnerfleet.app?

If gated:

• Can you configure IdP-initiated SAML SSO?
• Can you point a domain (DNS/CNAME) at the gated store?

If you can answer "yes" to the shared questions and your delivery's questions, you're ready. The
integration-tracking question is the usual variable — even without it, the marketplace works;
install-state badges appear once status sync is wired up.

Next steps

Schedule a 30-minute technical walkthrough with the Partner Fleet team. We'll screen-share the
admin UI, walk through the setup checklist live, and answer architecture questions. Most teams
leave that call with a clear plan and a confident sprint estimate.

Partner Fleet powers ecosystems for Gong, Mindbody, Salesloft, Greenhouse, ZoomInfo, Motive, and
50+ others.