The identity team already has a directory. It has an enterprise identity provider, established access policies, and a straightforward requirement which states that new vendors must fit that environment. What it doesn’t need is another collection of partner logins that turns into a separate federation project for every application.
That’s the basic architectural question behind QueryTek Tapestry: can an organization extend access across partner systems without repeatedly rebuilding the connection between enterprise identity and downstream applications? QueryTek Tapestry is a secure identity and routing platform that unifies access across disparate partner applications, carrying verified identity and context between them. It’s a governed boundary between the enterprise’s identity environment and the partner services its people need.
Keep the enterprise identity provider upstream
For the buyer, the enterprise identity provider stays upstream. Tapestry makes identity usable across connected partners rather than become a duplicate employee directory.
QueryTek’s federation description is simply this: Tapestry normalizes identity into a canonical claims model, then routes users to partner applications through registered outbound adapters, with strict multi-tenant isolation. A canonical claims model gives the intermediary a consistent representation of identity information rather than requiring every destination to interpret every upstream identity arrangement independently.
“We support single sign-on” does not, by itself, explain who must configure each connection, maintain each mapping, or resolve each partner-specific failure. Tapestry’s documented architecture places normalization and outbound routing in a shared layer. That provides a concrete basis for evaluating how much integration work the platform consolidates—and what work remains for each partner. It’s a disciplined integration boundary.

Draw the hallway, not another doorway
Think of Tapestry’s architecture as a hallway. The enterprise identity provider establishes the person’s upstream identity at one end of the hall. Tapestry governs the passage toward a connected partner. The partner remains the destination, with its own application and responsibilities.
This shared layer is one identity model and one governed routing layer, allowing eligibility, organizational scope, and progress to travel with a person rather than being re-established at every boundary. That context is important: knowing who someone is does not, on its own, establish which organization they represent or which interaction is appropriate.
For a person entering a certified partner application, Tapestry’s intended experience is continuity rather than another login setup exercise. For the identity team, however, that experience must rest on an established partner connection. Tapestry’s registered outbound-adapter model makes the connection itself part of the architecture.
Does this partner already participate through the governed layer, and what configuration is still required for our organization? That’s a lot more useful than counting logins.

A smooth passage still needs a closed gate
Fail-closed operations, strict tenant isolation, and comprehensive observability are all elements of Tapestry’s security baseline. They are defense-in-depth controls for identity brokering and partner routing. The session must fail closed: when the conditions needed to trust a passage cannot be established, the access process should stop right there.
A shared routing layer must preserve separation between the Tenant organizations using it; a convenient route cannot become a route into another tenant’s context. QueryTek explicitly identifies strict multi-tenant isolation in its federation architecture.
Together, these controls frame the hallway: passage is conditional, and organizational boundaries remain critical.
Partner access does not transfer partner compliance
A successful identity handoff is not the same thing as a compliant downstream service. Tapestry is an identity and routing interoperability layer with controls intended to protect sensitive data while enabling partner integrations. A partner holding health or payroll data still owns its compliance chain. Tapestry’s identity and routing controls won’t substitute for evidence about how that partner handles the information entrusted to it.
