Back to templates
Notifuse icon

Deploy Notifuse on Sealos

Open-source emailing platform for newsletters, transactional emails, automations, and real-time user segments

Tools
Deploy Notifuse in a few clicks from the Sealos App Store.Run a self-hosted open-source service on Kubernetes-backed infrastructure.Get automatic HTTPS, routing, and resource management from Sealos.Avoid manual YAML while keeping control of the deployed workload.

Why deploy on Sealos

Sealos makes deploying any app effortless, secure, and production-ready. From one-click launch to ongoing operations, we handle the heavy lifting so you can focus on what matters.

One-Click Deploy
Sealos logo
Compute
Networking
Storage
Security
Observability
Your Application is Live

One-Click Deployment

Deploy any app template in seconds. No compose setup, manual configure, and go live.

Managed Kubernetes Reliability

Built on Sealos Managed Kubernetes for high availability, auto-scaling, and self-healing by default.

Automatic HTTPS & Security

Every deployment includes a secure domain with automatic SSL. We handle certificates and text protection for you.

Persistent Storage

Attach persistent volumes with ease. Your data stays safe, durable, and always accessible.

Scale when needed

Adjust resources as your app grows, no downtime required.

You Get the Whole Stack

Sealos provisions and connects every resource your application needs. Everything is ready to use.

One-click, fully provisionedSecure by defaultProduction ready

App Service

Your application is running and ready to serve requests.

Public HTTPS URL

Secure, global endpoint to access your application.

Database

Managed database instance for your application.

Persistent Volume

Durable storage for uploads and application data.

Environment Variables

Configuration and secrets injected securely into your app.

Logs & Metrics

Centralized logs and basic metrics are enabled.

README

README.md

Deploy and Host Notifuse on Sealos

Notifuse is an open-source emailing platform for newsletters, transactional emails, automations, and recipient-facing subscription management. This template deploys Notifuse v32.1 with PostgreSQL, persistent storage, and HTTPS ingress on Sealos Cloud.

About Hosting Notifuse

Notifuse combines email marketing, transactional delivery, audience management, automation workflows, and a notification center in one application. On first launch, Notifuse guides you through its Setup Wizard so you can set the root administrator email, confirm the public API endpoint, and configure SMTP for magic-code sign-in and outbound email.

This Sealos template provisions the platform components required for a self-hosted deployment: a PostgreSQL cluster, a bootstrap job that creates the notifuse_system database, persistent storage mounted at /app/data, and a public HTTPS URL for the web console. The application also exposes port 587 inside the cluster so you can extend the deployment for SMTP relay scenarios later.

Common Use Cases

  • Newsletter Operations: Manage subscriber lists, create campaigns, and send regular product or editorial updates.
  • Transactional Email Delivery: Trigger password resets, account alerts, receipts, and other system emails through one central platform.
  • Lifecycle Automations: Build event-driven onboarding, nurture, and re-engagement flows based on contact behavior.
  • Multi-Workspace Email Management: Separate email operations by brand, customer, or business unit with isolated workspaces.
  • Branded Preference Management: Let recipients manage subscriptions through Notifuse's notification center and unsubscribe flows.

Dependencies for Notifuse Hosting

The Sealos template includes all required runtime dependencies: the Notifuse application, a PostgreSQL database cluster, a database initialization job, persistent application storage, an internal service for HTTP and SMTP-relay traffic, and an HTTPS ingress for browser access.

Deployment Dependencies

Implementation Details

Architecture Components

This template deploys the following services and resources:

  • Notifuse Application: Runs the web UI and API on port 8080
    • Image: notifuse/notifuse:v32.1
    • Persistent storage: 1Gi mounted at /app/data
    • Health checks: /healthz startup, readiness, and liveness probes
  • PostgreSQL Cluster: Provides the backing database for system and workspace data
    • Engine: PostgreSQL 16.4.0
    • Persistent storage: 1Gi
    • Credentials: injected from Kubernetes secrets
  • Database Init Job: Creates the notifuse_system database before the main app starts
  • Service + Ingress: Exposes the web interface publicly over HTTPS and keeps SMTP-relay traffic available on port 587 inside the cluster

Resource Allocation

ComponentCPU RequestCPU LimitMemory RequestMemory Limit
Notifuse20m200m25Mi256Mi
PostgreSQL50m500m51Mi512Mi

Configuration

The template keeps runtime configuration intentionally small and defers application-specific setup to Notifuse's built-in Setup Wizard. Sealos generates the app name, hostname, and SECRET_KEY automatically, while the template wires database credentials through Kubernetes secrets and waits for PostgreSQL before starting the main container.

After deployment, finish the initial setup in the Notifuse UI:

  • Enter the root administrator email
  • Confirm the public API endpoint generated by Sealos
  • Configure an SMTP provider. Notifuse uses email magic codes for administrator sign-in, so SMTP must work before regular browser login succeeds.

Notifuse uses the database credentials provided by the template to manage its internal system database and workspace-level data. Keep the generated SECRET_KEY stable after deployment because upstream documentation notes that changing it will invalidate previously encrypted integration secrets.

License Information

Notifuse is licensed under the GNU Affero General Public License v3.0. This template follows the licensing terms of the Sealos templates repository.

Why Deploy Notifuse on Sealos?

Sealos is an AI-assisted Cloud Operating System built on Kubernetes that simplifies the full deployment lifecycle. By deploying Notifuse on Sealos, you get:

  • One-Click Deployment: Launch Notifuse with PostgreSQL, storage, and HTTPS from a single template page.
  • Managed Kubernetes Foundation: Get service discovery, persistent volumes, rolling updates, and ingress management without hand-writing manifests.
  • Simple Post-Deploy Operations: Use the Canvas, AI dialog, and resource cards to adjust resources or update configuration after the app is running.
  • Persistent Data by Default: Application data and PostgreSQL storage survive restarts and routine updates.
  • Pay-As-You-Go Efficiency: Start with small resource requests and increase them only when your email volume grows.
  • Secure Public Access: Sealos provisions a public URL with TLS for the Notifuse console automatically.

Deploy Notifuse on Sealos when you want the flexibility of self-hosting without manually assembling the surrounding infrastructure.

Deployment Guide

  1. Open the Notifuse template and click Deploy Now.
  2. Review the generated parameters in the popup dialog. In most cases, the defaults are ready to use, but you can change the app name, hostname, or secret key before deployment if needed.
  3. Wait for deployment to complete, which typically takes 2-3 minutes. After deployment, Sealos redirects you to the Canvas, where you can use the AI dialog or resource cards for later changes.
  4. Open the generated application URL and complete the Notifuse Setup Wizard:
    • Add your root administrator email
    • Confirm the public API endpoint
    • Configure a working SMTP provider for magic-code sign-in and outbound email
  5. After SMTP is configured, sign in with the root email and the emailed magic code, then create workspaces, lists, templates, broadcasts, or automations in the Notifuse console.

Configuration

After deployment, you can manage the stack in two layers:

  • Sealos Infrastructure Layer: Use the Canvas, AI dialog, or resource cards to change CPU, memory, storage, hostname, or ingress-related settings.
  • Notifuse Application Layer: Use the web console to manage SMTP settings, define workspaces, configure branded endpoint URLs, create senders, and manage lists or automations.

For recipient-facing email links and branded unsubscribe pages, configure each workspace's custom endpoint URL inside Notifuse after the initial setup is complete.

Scaling

This template is optimized as a single-instance Notifuse deployment with persistent local storage. For most teams, the first scaling step should be vertical scaling rather than adding more replicas.

To scale the deployment:

  1. Open the Canvas for your deployed app.
  2. Click the Notifuse StatefulSet resource card.
  3. Increase CPU or memory limits based on campaign volume, automation workload, and API traffic.
  4. Expand the application or PostgreSQL storage volumes if your templates, logs, or contact data grow over time.

If you need a more advanced multi-instance architecture, treat that as a separate customization project instead of simply increasing replica count on this template.

Troubleshooting

Common Issues

Issue: The UI opens, but setup is not complete

  • Cause: Notifuse always requires the initial Setup Wizard on first launch.
  • Solution: Open the public URL and finish the root email, API endpoint, and SMTP configuration steps.

Issue: The app stays unavailable for a few minutes after deployment

  • Cause: PostgreSQL and the database init job may still be preparing the notifuse_system database while the app waits on health checks.
  • Solution: Wait for the deployment to settle, then review the PostgreSQL cluster, init job, and StatefulSet status from the Canvas if it still does not become healthy.

Issue: Emails are not being sent

  • Cause: SMTP is not configured yet, the provider credentials are incorrect, or the SMTP server is unreachable.
  • Solution: Add or correct the SMTP settings in the Setup Wizard or Notifuse settings. Regular browser login depends on email magic codes, so confirm SMTP delivery before inviting users.

Issue: Click tracking or unsubscribe pages use the wrong domain

  • Cause: Workspace-level endpoint branding has not been configured.
  • Solution: Set the custom endpoint URL in each workspace so recipient-facing links use your preferred domain.

Getting Help

Additional Resources

License

This Sealos template follows the licensing policy of the templates repository. Notifuse itself is licensed under the GNU Affero General Public License v3.0.

Related templates

Explore more production-ready templates.

More

Ready to Stop Configuring and
Start Creating?

Get started for free. No credit card required.

Play