Skip to content

Use cases

One platform, many kinds of services

From a personal site to a team application, the work is the same: deploy, operate, observe and keep control. What changes is the infrastructure you put behind it.

Examples, not silos

Each example explains the operational value, what it requires and where the platform stops.

Personal applications & websites

Run the sites, dashboards and small tools you build, on a server you already pay for.

What you get

  • Deploy from a Git repository or a Docker image
  • Attach a domain and a certificate without editing a proxy config
  • Keep logs and rollbacks for the day something breaks

Prerequisites

A Linux server with Docker, and a domain if it should be public.

Limits

One machine is a single point of failure. Redundancy is your design decision, not a default.

Homelab services

Give the services on your NAS or home server a consistent way to deploy and restart.

What you get

  • Templates and Compose stacks for common self-hosted tools
  • Remote hosts over SSH when one machine is not enough
  • Volumes and backups you control, on storage you choose

Prerequisites

Hardware you can reach, Docker, and a plan for DNS and inbound access.

Limits

Power, network and disk are yours. Notploy does not make consumer hardware highly available.

Developer tools & internal services

Ship the internal services and preview environments a small team needs, without assembling a platform.

What you get

  • Deploy on push and keep a deployment history
  • Environments and per-environment variables
  • Logs, metrics and rollback in the same place

Prerequisites

A Git provider, and a server or cluster the platform can reach.

Limits

Preview and environment behaviour depends on how your repository is configured.

Team & business applications

Operate customer-facing or internal applications with access control and a trace of changes.

What you get

  • Organisations, projects and role-based access
  • Single sign-on and SCIM where the commercial offer includes them
  • Audit logs and backup workflows for internal oversight

Prerequisites

An identity provider if you enable SSO, and a backup destination you control.

Limits

Compliance obligations stay with your organisation. Notploy provides controls, not certification.

Data services, game servers & specialised workloads

Run stateful or long-lived services where the runtime and the platform support them.

What you get

  • Databases with scheduled backups
  • Persistent volumes for stateful services
  • Resource limits and scheduled jobs

Prerequisites

Check the documented runtime and storage requirements before promising production use.

Limits

Not every workload type is supported. Running a container is not by itself evidence of production readiness.

Use case questions

What these examples do and do not promise.

Start with the infrastructure you already have.

Install Notploy Self on a server you control, or let Notploy operate the control plane with Cloud. Both paths lead to the same platform.