Suger is now Fours. Read the announcement
Customers
Pricing
Insulin
Sign in Get a demo

Marketplace integrations,
from your CRM to your ledger.

Connect the cloud marketplaces to the systems you already run, from Salesforce and HubSpot to NetSuite, Stripe and Slack.

Browse integrations Request an integration

What moves, and where.

The flows teams turn on first.

  1. CRM opportunities and co-sell referrals

    Salesforce or HubSpot ⇄ Fours ⇄ AWS, Microsoft, Google Cloud

    Salesforce setup

  2. Private offers from CRM records

    Salesforce or HubSpot → Fours → the marketplace

    Private offer guide

  3. Usage into marketplace billing

    Chargebee, Lago, Metronome or Orb → Fours → the marketplace

    Metering guide

  4. Revenue and disbursement into finance

    The marketplace → Fours → NetSuite or QuickBooks

    Revenue guide

  5. Entitlement and offer alerts

    Fours → Slack, Teams, email or a webhook

    Slack setup

Your reps stay in the CRM.

Offers, co-sell, partner deals and funding run from the record your reps already work.

Salesforce Managed package

Private offers, resale authorizations, co-sell referrals, partner deals and AWS funding requests, from the opportunity.

See the Salesforce integration HubSpot HubSpot app

Offers, resale, co-sell to clouds or partners, and AWS funding, prefilled from the deal, with each status back on the record.

See the HubSpot integration

Everything Fours connects to.

65+ integrations, each linked to its setup guide.

Pick how you connect, by the lift.

Connect once per organization; every workflow, report and API call uses the same connection.

Pre-built connector

Authorize it once in Settings. Fours handles credentials, token refresh and field mapping.

Effort Minutes, no engineering Browse the setup guides

Workflow builder

Branching, filters, schedules and webhook triggers between connected systems. No service to write.

Effort Hours, no code Build your first workflow

REST API and SDKs

Every console operation, for a system outside the directory or to embed Fours in your product.

Effort Engineering, API key or OAuth Read the API reference

Customer outcomes

More partner-driven growth.
Less operational drag.

Marketplace revenue, co-sell referrals and partner programs, run by teams who moved off spreadsheets and portals.

See all customer stories

Frequently asked questions

From teams wiring the marketplace into the rest of their stack.

What does Fours integrate with?

The cloud marketplaces, your CRM (Salesforce, HubSpot and others), cloud co-sell programs, billing and metering tools, finance systems such as NetSuite and QuickBooks, data warehouses, Slack and Teams, sign-in providers and your own AI model keys. Every integration is configured in Fours Settings.

Is a connection made per user or per organization?

Most connectors are organization-level: one shared key, OAuth app or service account for the whole team. A few, such as Google Calendar and Atlassian, are connected by each person. Each integration's doc page says which applies.

What if a tool we use is not listed?

The generic OAuth 2.0 and MCP connectors cover most services without a purpose-built connector. The workflow builder handles custom orchestration between connected systems, and every console operation is on the REST API.

How do we know a connection still works?

Each time Settings, Integrations is opened, Fours re-checks the stored credential with the provider, so a revoked or rotated credential shows up there rather than when a workflow needs it. Reconnecting is the fix.

Which sign-in providers are supported?

Okta (OIDC single sign-on with SCIM provisioning) and Google Workspace (single sign-on with Directory Sync).

Can Fours AI run on our own model keys?

Yes. Bring your own key for Anthropic, OpenAI, Google Gemini, OpenRouter, Together AI, Fireworks AI, Baseten, DeepInfra, Cloudflare Workers AI or DigitalOcean GradientAI.

See what connects to your stack.

Tell us what you run today, and we will show you what connects and what it moves.

See Fours in action