Application hosting

Hosting ntfy

A notification service for sending messages to topics and receiving them on connected clients. Run a private server or use the hosted service.

Understand the setup

Check runtime, storage and installation requirements before choosing a server.

See requirements

Budget your resources

Allow room for the operating system, database and your actual workload.

Open resource planner

Build your shortlist

See the cheapest plans that meet the starting size, then check each provider's page.

See plans

Must have

Installation requirements

  • A supported binary, package or container architecture.
  • Persistent storage where accounts, caching or attachments are configured.

Recommended

Planning guidance

No further general recommendations are published for this version.

Capacity depends on your workload

The guide does not establish a universal minimum. Example resource limits are not measured workload capacity.

Deploy with

Supported paths

  • Linux service
  • Docker Compose
  • Kubernetes

The host must provide

Runtime

ntfy server
AMD64, ARMv7 and ARM64 builds documented

Storage

Persistent data

The Docker example mounts /etc/ntfy and /var/cache/ntfy. Preserve databases and attachments as configured.

Step by step

Plan a ntfy deployment

  1. Install the service

    Choose a supported package or image and configure server.yml.

    Official instructions
  2. Check permissions

    Ensure the service user can access configuration, databases and attachments.

    Official instructions

Security

Before you go public

  • Review topic access controls before sending private messages.

Cost

Beyond the server price

  • Budget for retained messages, attachments and traffic.

Providers rarely list runtime versions or extensions, so confirm PHP, database and other requirements with the provider before you buy.

Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.