How to manage single tenant SaaS deployments in compass

[Alexander]

We sell our products as a single tenant SaaS provider. This means that we have a few components which can be considered "Applications" that are built using a lot of the "Library" and "Capability" components in our Compass catalog.

Deployment of our applications happens using a separate pipeline that deploys these applications in different configurations as standalone platforms.

When I look at the list of Component Types then I struggle to find what would be the best representation of such a deployment (which is owned by a team and wants to be informed about its dependencies).

A single deployment may use multiple services to support the application (and generally has its own instance of service types), so the service type doesn't feel appropriate.

The website type also doesn't feel appropriate since it seems to be aimed more at marketing or documentation sites, rather than very interactive platforms.

I'm curious to hear how others might have organized this in Compass or how the Compass team has envisioned this (or whether a new component type would be needed).

[Black Jalid]

Given the complexity of your deployment model, you might consider creating a custom "Platform" component that encapsulates all related services and components. This could provide the visibility you need for tracking dependencies and ownership, while differentiating from the service or website types. It may also be useful to reach out to Compass support to suggest a new component type or get more guidance on organizing your deployment.

[Jeff Madison]

How about an Application component that Depends On the various Services and other components that comprise it?

The documentation for the Application component type has a list of examples that doesn't specifically include "SaaS product offering", I have been interpreting it that way anyway.