Glossary
Current BullSequana AI product, tenancy, and operational terminology.
| Term | Meaning |
|---|---|
| AI | Product domain for models, RAG, assistants, document intelligence, voice, and agents. |
| Data | Product domain for integration, lakehouse, catalog, data science, orchestration, streaming, and BI. |
| Foundation | Product domain for shared identity, inference, networking, observability, storage, databases, and delivery services. |
| Installation | One deployed BullSequana AI platform. |
| Tenant | Customer or organization isolated from other customers on an installation. |
| Team | Department or working group inside one tenant. |
| Provider administrator | Administrator with installation-wide and tenant-lifecycle responsibilities. |
| Tenant administrator | Administrator responsible for identity, teams, membership, and delegation inside one tenant. |
| BSQAI API | Stable platform-facing interfaces used by applications and supported tools. |
| Portal | User-facing web experience for BullSequana AI capabilities. |
| MCP Server | Model Context Protocol endpoint a Platform Admin has made available to an organization. |
| Managed Server | MCP Server whose container the platform runs inside the cluster. |
| Remote Server | MCP Server that runs outside the platform, reached at a stored address. |
| MCP Gateway | Single authenticated entry point that every MCP call passes through. |
| Upstream | Third-party system an MCP Server acts against, such as GitHub or Linear. |
| User Credential | Secret that authorizes one user against one MCP Server's Upstream. |
| Linking | Act of a user supplying their User Credential for an MCP Server. |
| Tool Allowlist | Subset of an MCP Server's tools a Platform Admin permits the organization to call. |
Historical product names can appear in release notes, repository names, image paths, and deployment identifiers. They do not define the current documentation taxonomy.