Multitenancy

This approach provides clear separation and control while optimizing resource usage.

Multitenancy is a foundational concept within Fastn UCL that enables secure, scalable, and efficient management of multiple customers or teams within a single platform instance.

Core Concepts

Multitenancy means that a single deployment of the UCL platform can serve multiple distinct tenants, such as different customers, departments, or user groups. Each tenant operates in an isolated environment with its data, credentials, tools, and access policies. This ensures privacy and security, preventing any cross-tenant data exposure.

How Multitenancy Works in Fastn UCL — A Simple Case Study

Imagine Sarah, June, and Emily all work at the same company and share the same Space ID in your app, but each manages different tools and integrations as shown in the video:

1. Tenant Context Keeps Everything Organized

Each user operates within their own tenant context [tenant ID], even though they share the same Space ID. For example, when Sarah logs in and accesses integrations, Fastn UCL recognizes her tenant identity and:

• Displays only Sarah’s selected tools (e.g., Slack, HubSpot, Salesforce).

• Uses only her data and configurations when performing actions.

Similarly, June and Emily see and interact only with their own connectors and configurations, even if some connectors overlap in the space.

2. Different Tenants, Different Connectors and Actions

Within a shared Fastn workspace (same space ID), all users have access to the same set of available connectors, like Slack, Gmail, or Notion. However, each user or tenant can connect these tools with their credentials and enable only the actions they need.

For example:

• Sarah might connect Slack and enable message posting actions.

• June might use the same Slack connector, but might not have "send message" Action enabled.

• Emily might connect Notion and only enable read-only access for documentation.

This setup ensures everyone shares the same connector infrastructure but operates independently, with secure separation of credentials, access, and actions.

3. Seamless Isolation, Zero Mix-Ups

Despite all users operating in the same app and sharing the same Space ID, Fastn UCL keeps their tools, data, and actions strictly isolated:

• Sarah cannot see or affect June’s integrations.

• June cannot send messages using Emily’s Gmail setup.

• Each tenant’s data and configurations remain private and secure.

4. Platform Handles Complexity Automatically

All of this complexity is managed transparently by Fastn UCL. It reads the tenant ID on every request and automatically:

• Routes requests to the correct connectors per tenant

• Applies the appropriate permissions and roles

• Keeps all tenant data and actions isolated and secure

This lets you focus on building features instead of managing multi-tenant logic.

Key Benefits of Multitenancy

Fastn UCL's multitenancy architecture delivers several critical advantages that enhance both operational efficiency and user experience:

• Security: Tenant isolation prevents unauthorized data sharing or accidental exposure across teams.

• Simplicity: Teams manage their own integrations and tasks independently without interference.

• Scalability: A single UCL deployment can grow to support thousands of tenants without performance loss.

• Cost Efficiency: Shared infrastructure reduces overhead compared to maintaining separate instances for each tenant.

• Centralized Management: IT administrators can oversee multiple tenants from a unified dashboard while respecting tenant boundaries.

Architecture

The multitenant architecture of Fastn UCL consists of a centralized server that handles requests for all tenants. Each tenant's data, configuration, and authentication tokens are stored separately within secure workspaces. Connectors and actions are dynamically mapped based on tenant context, allowing seamless routing of operations. The architecture supports horizontal scaling to meet increasing demand while preserving tenant isolation and performance consistency.