When an IT vendor hosts data for many clients: a tenant-owner boundary map that splits what the custodian runs, what each client owns and decides, and what SourceX reviews, so every tenant is introduced as its own company or not at all

Short answer

Hosting many clients' data can show an IT vendor which clients might hold valuable records; it never gives the vendor the right to license, export or describe them. Each tenant's records belong to that client, so each client is a separate company with its own CEO, its own fit test and its own introduction. The vendor may introduce a willing client's CEO, using facts the client hands it, or introduce itself for records about running its own business.

Visual briefFull-size diagram
A building-style diagram: one shared floor labeled vendor, custodian not owner, with four tenant units above it, each holding its own key for that client's CEO. Only tenant B shows a yes, a single line runs from tenant B to SourceX labeled one tenant, one introduction, and a strip below says no tenant contents leave for a referral.
Illustrative platform and tenants; roles follow the boundary map on this page.

The situation covers hosting providers, managed service providers running a shared platform, resellers of a hosted system and anyone holding admin rights across many customers' environments. The temptation is the same in each: the vendor can see, at a glance, which tenants have deep histories. This page draws the line between seeing and deciding.

Pooled infrastructure, separate owners

NIST's definition of cloud computing describes resource pooling in one sentence: "The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model." The same definition notes that the customer generally has no control or knowledge over the exact location of the provided resources. What is pooled is the machinery. Microsoft's shared responsibility page draws the other half of the picture: whatever the deployment type, the customer always keeps responsibility for its data, its endpoints, its accounts and its access management (paraphrase).

Put those together and a hosting vendor is a custodian of shared machinery holding many separate owners' records. SourceX's screening guidance looks at the same split from the licensing side. A company needs the right to license what it offers: the material has to be its own, or licensable without breaking a duty it owes clients, staff or a contract partner. Material that belongs to a company's clients rather than the company is usually not a fit. From the vendor's seat, every tenant's contents are its clients' material. The vendor cannot license them, and it cannot speak for the client that can.

The system events that put a tenant in view

A vendor usually learns that a client's history is in play through the service itself, not by looking. These are the common moments, what the vendor sees without opening anything, and whose decision follows.

EventWhat the vendor sees without opening contentsWho inside the client may sponsorWho decidesA question for the client
Tenant leaving the platformA cutover plan or an export request ticketIT director or COOThe client's CEOWill the history move with you, or stay behind and expire?
Platform end of lifeThe vendor's own sunset noticeOperations leadThe client's CEOWhich years do you still need, and who chooses?
Shorter retention or a cheaper storage tierA change requestController or records ownerThe client's CEOWhat happens to records older than the new limit?
The client is acquiredA request to merge tenantsIntegration leadBefore closing the target's CEO; after closing the acquirer's CEOWhich company's records are these now?
Contract renewalA renewal quoteCFOThe client's CEOIs the archive part of what you are renewing?

Service metadata of this kind is enough to know a conversation might be timely. It is not permission to open a tenant's contents to size the opportunity. When records change hands in an acquisition, the tenant control and data ownership worksheet separates the two questions in detail.

The tenant-owner boundary map

Three parties, six questions. Read down a column to see one party's whole role; read across a row to see where a responsibility sits.

QuestionTechnical custodian (the vendor)Tenant owner (the client company)SourceX
What does it hold?Infrastructure, backups and the admin credentials it was issuedThe records, and whatever rights it has to themNothing from the referral
What does it decide?How the platform runs, within the service contractWhether to discuss licensing, what is in scope, who acts for itWhether the company and its records fit a current program, and on what terms
Who signs for it?The vendor's own officers, for the vendor's own businessThe client's CEOSourceX
What may it say in an introduction?That it serves the client, plus what the client asked it to pass onAnything about its own recordsIts published process and terms
What does it never do?Open, export, sample or count tenant contents for a referralLet a vendor speak for it in place of its own decisionTreat the vendor's word as the client's yes
Which papers govern it?The client's service agreement; the Channel Partner Agreement for the referralIts own contracts with customers and staffA Master Supplier Licensing Agreement and Dataset Deal Confirmation signed with the client

A vendor's platform usually carries three record families, and each points to a different introduction or none:

Record familyWhose it isIntroduce whomUnknown until SourceX reviews it
Tenant contents: each client's documents, tickets and transactionsThat clientThe client's CEO, if she wants itRights, customer contract limits, fit with a current program
The vendor's own operating records: runbooks, change logs, its own service historyThe vendorThe vendor's own CEO, with the vendor as the companyWhether those records mention clients in ways contracts restrict
Mixed records, such as tickets describing a client's problemsContestedNobody, until the question goes to SourceX's rights reviewAlmost everything

The second row is easy to overlook: a vendor with 50 or more full-time employees at its peak and years of its own operating history may be the company worth introducing. What service desk histories look like as a data type is described on the MSP ticket and time-entry page.

Admin rights, the service contract and the power to license

These are three different permissions, and holding the first two gives none of the third.

  1. Admin access is technical ability, issued by the client so the vendor can run the service. On Microsoft's account of shared responsibility, access management stays the customer's job even when the vendor holds the keys.
  2. The service duty is what the service agreement asks the vendor to do. A licensing introduction is not part of it; it is a separate relationship under a separate agreement, and clients deserve to hear that you may earn a reward. The MSP disclosure guide covers that conversation.
  3. Licensing authority belongs to the client's CEO, and whether the records can be licensed at all is settled in SourceX's rights review. The partner agreement gives a partner no authority to share a company's inventory, records, raw data or personal information, or to access extraction systems (4.2). It bars collecting or keeping dataset copies through the referral program without separate written authorization (4.4), and a partner is not SourceX's agent and cannot commit SourceX to prices, licenses or payouts (7.1).

One tenant, one company, one introduction

Every client on the platform is screened as its own company: 50 or more full-time employees at peak with contractors left out, documented operating history, rights to license, and a CEO who agrees. Each has its own 90-day attribution window, its own duplicate check and its own verified application. One partner is credited per company, so a client already introduced by its accountant is a duplicate when the vendor arrives second, and a client that once emailed SourceX is a duplicate for everyone.

Groups need one more rule. There is no cap on rewards, per company or per group, but the USD 50,000 floor applies once per referred company, to its first qualifying transaction, and not again on a repeat, renewal or amendment. Illustrative only: if SourceX credited one group company to the partner and its first qualifying transaction paid USD 500,000, the reward would be USD 75,000, and that company's floor would not apply again to its later transactions. Whether an earlier introduction of one group company changes the credit for its sister is not answered by the terms; SourceX works that out in duplicate review. The subsidiaries guide goes further into group structures.

Introducing a tenant's CEO with the client's facts, not yours

  1. Ask first. Through the client's sponsor or directly, ask the CEO whether she wants a conversation about licensing records her company created. Say that you may receive a reward if she goes ahead.
  2. Let the client describe the records. Record types, years covered, systems and rough volume, in the client's words. Never figures read off a console you administer.
  3. Write a short introduction. Who you are, that you host a system for the company, the CEO's own description, and nothing attached.
  4. Step back. SourceX may deal with the company directly without affecting valid attribution, so the vendor's part ends with the introduction.

An Illustrative screen of four tenants on a 70-person hosting provider's document management platform:

Tenant (Illustrative)What the vendor knows from running the serviceVerdictReason
320-person civil engineering firmA May cutover ticket; the COO asked how far back project files goAsk the CEO, through the COOIts own project records, a dated event and a reachable CEO
Bookkeeping practice whose full-time staff peaked at 44A renewal quoteDo not raise itIts peak full-time headcount never reached 50
260-person logistics subsidiary whose parent is also a tenantOne group administrator for both tenantsRaise it once, with the subsidiary's CEO, and note the once-per-company floorCredit between sister companies is SourceX's call
150-person claims administratorSupport tickets show it stores files for insurer clientsDo not pitch it as a fit; its CEO may still ask SourceXMaterial belonging to its clients is usually not a fit

What the boundary map cannot settle

The map shows roles, not contract terms. A service agreement may restrict what you can say about a client at all, even its name, so read yours before you raise anything. A client's own contracts with its customers decide much of what it may license, and only SourceX's review reaches those. And demand moves: a tenant that fits today's programs may not fit next year's, and the reverse. For the wider screen of which clients deserve a conversation, see how MSPs recognize suitable client businesses, the managed service provider overview and the parallel screen for staffing firms' business clients.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Pick the one tenant whose CEO has already raised the company's records with you, introduce that company on its own in the CEO's words, and leave every other tenant's contents untouched; register as a partner first, then check that client against who qualifies and the attribution sections of the program terms. The guides hub has more partner playbooks.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

May a hosting vendor check a tenant's storage to estimate how many records it holds?

Not for a referral. Admin access exists to run the service the client bought, and the partner agreement gives a partner no authority to access a company's records or extraction systems. Ask the client to describe its own records, in its own words, if it wants an introduction.

Can the vendor introduce itself instead of its clients?

Yes, if the vendor is a company that fits in its own right and the records are about running its own business, such as its runbooks and change history. Tenant contents never count as the vendor's records, and anything that mixes the two is a question for SourceX's rights review.

Two tenants belong to the same corporate group. Are they one referral or two?

Each operating company is screened and introduced on its own, and there is no cap on rewards for the parent or any subsidiary; the USD 50,000 floor applies once per referred company, to its first qualifying transaction. Whether credit for one sister company is affected by an earlier introduction of another is decided by SourceX in duplicate review.

Sources

  1. refer.sourcex.si/who-qualifies
  2. refer.sourcex.si/terms
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. nvlpubs.nist.gov/nistpubs/legacy/sp/nistspecialpublication800…
  5. learn.microsoft.com/en-us/azure/security/fundamentals/shared-res…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment