Skip to main content
Nemofy
Book a demo

Deployment

On the infrastructure you already own.

Docker Compose or Helm. Java 21 + Spring Boot 4. PostgreSQL or MySQL. Redis. Plugs into the identity you already run.

01 · Architecture in your infrastructure

Nemofy + its data plane sit inside your perimeter.

Your perimeterOutbound · provider APIs

02 · System requirements

Standard ops surface. No exotic dependencies.

Runtime
Java 21 · Spring Boot 4
Database
PostgreSQL 14+ or MySQL 8+
Cache & queue
Redis 7+ · JobRunr
Identity
Keycloak (federates AD · LDAP · SAML)
Packaging
Docker Compose · Helm chart
Build
Maven multi-module

03 · Identity integration

Plugs into the identity you already run.

Nemofy ships with Keycloak. Keycloak federates with your existing Active Directory, LDAP, or SAML provider. Roles map to scopes; scopes apply to every surface — UI, API, SDK, CLI. No parallel user store, no parallel password policy.

04 · Install path

Docker Compose for a pilot. Helm for production.

Day-0 install runs against a single VM with Docker Compose for evaluation. The Helm chart targets your existing Kubernetes cluster for production — same configuration surface, different orchestrator.

05 · Day 0 to Day 30

Days, not quarters.

  1. Day 0

    Install

    Docker Compose or Helm. Keycloak federates with your existing directory. Postgres + Redis stand up. Healthcheck endpoints green.

  2. Day 7

    First app integrated

    One application sends through Nemofy. One channel routed. First template registered. First audit entries flowing.

  3. Day 30

    Multi-app, multi-channel

    Multiple applications across multiple channels. Vendor performance and notification analytics dashboards live. Audit log queried.

Book a deployment review