Skip to main content

Workspace Operations

Workspace operations are the recurring actions that keep Moltern workloads understandable, secure, and cost controlled.

This page is for workspace owners and application operators. It focuses on what you can do from the Moltern UI.

Moltern dashboard summary for operations

Daily Review​

Moltern dashboard workload table

Start in the dashboard:

  1. Check the needs attention count.
  2. Open failed or crashing workloads.
  3. Review recent deployments.
  4. Confirm production routes are live.
  5. Check whether any service is sleeping before sharing a link.
  6. Review billing if a deploy or resize is blocked.

Weekly Review​

For production workspaces:

  • Review unused applications.
  • Review unused catalog services.
  • Remove temporary environments that are no longer needed.
  • Check storage usage and reclaimable artifacts.
  • Review webhook endpoints and owners.
  • Confirm critical domains are active.
  • Confirm production workloads have owners.

Change Management​

Use this order for planned changes:

  1. Deploy to a non-production environment first when one exists.
  2. Check logs and route behavior.
  3. Confirm variables are correct.
  4. Review billing impact for size changes.
  5. Deploy to production.
  6. Watch deployment logs until success.
  7. Open the production route.
  8. Notify stakeholders when the change is complete.

Incident Triage​

When a workload fails:

  1. Open the workload detail page.
  2. Read the recovery card or error hint.
  3. Open logs.
  4. Check recent variable changes.
  5. Check repository access for applications.
  6. Check billing or quota if the action was blocked.
  7. Retry only after correcting the likely cause.
  8. Record the cause and fix for future runbooks.

Ownership Model​

Every production workload should have:

  • Product or team owner.
  • Technical owner.
  • Environment.
  • Public route decision.
  • Variable owner.
  • Storage owner.
  • Billing owner.
  • Recovery expectation.

What Not To Store In Moltern Docs​

Public workspace docs should not expose:

  • Real passwords or tokens.
  • Private keys.
  • Customer data.
  • Internal network maps.
  • Temporary incident credentials.
  • Direct platform administration instructions.

Use Moltern variables and the receiving systems' secret managers for sensitive values.