English
Apprise Hosting
Send one notification to dozens of services at once through a single API.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Apprise’s official links and original website
Apprise Website
More
Tech
- Docker image
- caronc/apprise:latest
- Default port
- 8000
How Apprise works
Apprise API wraps the Apprise notification library in a web service. A caller submits a title, body, format, attachment, tag, or configuration key, and the gateway translates that request into the syntax required by the configured destination services. This keeps provider-specific notification URLs out of each monitoring script and gives several applications a consistent endpoint.
Configuration files and persistent settings live in the mounted /config path. Administrators can organise destinations by keys or tags so one request reaches a selected group rather than every configured service. Delivery still depends on the destination provider, its credentials, quotas, network availability, message limits, and current API behaviour.
Key Apprise features
The API can support monitoring alerts, job results, deployment notices, and other machine-generated messages without becoming a full incident-management platform. It does not create destination accounts, issue provider credentials, manage on-call schedules, acknowledge incidents, or prove that a person read a notification. Applications should retain their own event history when an audit trail matters.
The catalogue configuration exposes Apprise with no built-in login. Anyone who can reach the URL may be able to invoke configured notification services, so the address must be treated as a secret and access restricted outside the application. Provider tokens stored in configuration are sensitive credentials; they should be scoped narrowly and replaced if the endpoint or configuration is exposed.
Who uses Apprise
Infrastructure teams can send health alerts to several chat or push services, developers can reuse one notification endpoint across test jobs, and home-lab operators can centralise provider URLs. A small internal automation may also target different destinations through configuration tags.
Apprise is not a transactional email platform, durable message broker, paging service with escalation policies, secrets manager, delivery guarantee, or replacement for provider-side monitoring. Operators must decide which destinations are appropriate, protect every credential, and handle retries or failure records in the calling system.
Self-hosting Apprise: requirements and cost
Apprise resource use depends on request volume, message size, attachments, number of destinations, provider latency, and concurrent calls. PostgreSQL and MariaDB are Not required in the catalogue; persistent configuration is stored in /config. The software carries no separate application charge, and most modest notification workloads are limited more by external provider behaviour than by local storage.
On AvaHost, Apprise uses Plan 1 at €2. The hosted Apprise package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The deployment has no built-in Apprise login and its URL functions as a sensitive invocation endpoint. AvaHost does not supply notification-provider accounts, tokens, delivery guarantees, escalation logic, or application email. Configure only services you control, restrict reachability, and avoid placing broader credentials in a shared configuration.
F.A.Q
Apprise starts at €2 on Plan 1. A light internal gateway with short messages and a modest number of destinations should fit that starting point. Request rate, concurrent calls, attachment size, provider response times, and the number of services addressed per message determine when more processing headroom is useful.
The catalogue deployment does not configure a built-in Apprise login. Treat the application URL as a secret, restrict who can reach it, and avoid exposing provider tokens through shared configurations or logs. Anyone who can invoke the endpoint may be able to send through the services you configured.
The hosted package includes the Apprise gateway, not accounts or credentials for chat, push, SMS, email, or other destination services. You must configure notification URLs and tokens belonging to services you are authorised to use. Provider quotas, content rules, outages, billing, and delivery behaviour remain outside the hosted application.
Automatic application updates keep the persistent `/config` data attached, and scheduled backups cover the hosted installation. Store approved configuration in that path, maintain a separate record of critical notification URLs, and test a representative message after changes that affect provider integrations, authentication, attachments, or request formatting.