> ## Content Index
> Fetch the complete content index at: https://blog.moltern.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Service Catalog Use Cases: PostgreSQL, Redis, n8n, Gitea, Ghost, and Grafana on Moltern
- URL: https://blog.moltern.com/moltern-service-catalog-use-cases-postgres-redis-n8n-gitea-ghost-grafana/
- Published: 2026-06-28T15:37:31.000Z
- Updated: 2026-09-12T21:00:11.000Z
- Description: The Moltern service catalog turns databases, automation, Git tooling, CMS, and monitoring into repeatable workspace deployments.
- Author: Moltern Editorial
- Tags: Service Catalog, Databases, Automation, Monitoring

The Moltern service catalog is built for the software your applications depend on: databases, queues, automation tools, Git services, CMS platforms, observability dashboards, AI tools, and internal utilities. Instead of asking each team to hand-roll a deployment, Moltern gives them a guided catalog workflow inside the same workspace as their apps.

![Moltern service catalog for deploying databases, automation, CMS, and monitoring](https://moltern.com/blog-assets/moltern-service-catalog.jpg)

The service catalog helps teams launch supporting infrastructure without leaving the deployment workspace.

## Six common service catalog use cases

| Service    | Use case                                                                                         | How Moltern helps                                                                          |
| ---------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ |
| PostgreSQL | Primary relational database for APIs, SaaS products, dashboards, and internal tools.             | Deploy it as a managed workspace service with storage, ownership, and environment context. |
| Redis      | Cache, queue backend, rate-limit store, or session storage for app workloads.                    | Keep it close to the app that depends on it and visible as a service workload.             |
| n8n        | Workflow automation between APIs, internal tools, CRM systems, forms, and notification channels. | Launch it from the catalog and attach a route only when access controls are ready.         |
| Gitea      | Lightweight self-hosted Git, issue tracking, pull requests, and package workflows.               | Deploy it as an internal development service for teams that need a private Git surface.    |
| Ghost      | Publishing, blog, newsletter, documentation, or content hub.                                     | Run it beside the rest of the product stack without managing chart details by hand.        |
| Grafana    | Dashboards for metrics, service health, business operations, and observability.                  | Keep monitoring as a first-class service with ownership and environment context.           |

## Why a catalog is better than a list of scripts

A service catalog is not just a prettier install command. It gives the platform a source of truth for service names, categories, resource expectations, required credentials, dependencies, and post-deploy guidance. That is how Moltern can present a normal product workflow instead of exposing raw infrastructure to every user.

Moltern's public service directory at [moltern.com/docs](https://moltern.com/docs?ref=blog.moltern.com) is service-focused. It helps users understand what a service does, when to use it, and what to check before exposing it publicly. The platform docs at [docs.moltern.com](https://docs.moltern.com/service-catalog?ref=blog.moltern.com) explain the broader workflow.

## Public or private by default?

Not every service should be public. A database should normally remain private. A CMS, dashboard, identity app, automation UI, or analytics tool may need a public route, but only after authentication and ownership are clear. Moltern's environment and service model makes that decision explicit instead of hiding it inside a deployment script.

## Best practice checklist

- Choose the environment before deploying the service.
- Record the owner and purpose.
- Decide whether the service needs a public URL.
- Review storage expectations for stateful services.
- Keep service credentials in variables or generated platform secrets, not in source code.
- Check usage and workload quota after deployment.

That is the core Moltern value: services become understandable product objects, not invisible infrastructure chores.