Skip to main content
Nemofy

Deployment

On the infrastructure you already own.

Same Nemofy, every target. Boot a single container on a laptop, a Compose stack on a VM, or a Helm chart on a managed cluster. Pick your infra; the config schema is the same.

Pick your infra

Five targets. One install path per shop.

Nemofy ships the same artefacts to all of them. The team that runs your apps already runs at least one of these. Pick the one that matches.

VM
1 vCPU · 2 GB RAM

Single node, bare metal.

Drop the binary on any Linux VM. One process, one config file, one port. Smallest possible install for a side-by-side evaluation.

  1. Run the install script
  2. Edit one config file
  3. Open the admin
Best for · Evaluation · isolated environments
Docker
512 MB RAM

One container, local in seconds.

A single image. Run it locally to try it, run it on a host to ship it. No supporting services, no orchestrator, no surprises.

  1. docker pull
  2. docker run
  3. Open localhost
Best for · Dev laptops · CI sandboxes
Docker Compose
~1.5 GB RAM

Compose stack, one command.

A turnkey stack for a pilot on a single VM. Health, audit, and admin all up in one `docker compose up`. Same configuration surface as Helm.

  1. Download the compose file
  2. docker compose up -d
  3. Open the admin
Best for · Pilots · staging environments
Helm
Cluster baseline

Chart, declarative.

A Helm chart with sensible defaults and a values file you can put in git. GitOps-ready out of the box; rolls out the same way every other workload in your cluster does.

  1. helm repo add nemofy
  2. Edit values.yaml
  3. helm install
Best for · GitOps shops · standard K8s
Kubernetes
Multi-replica, autoscaling

HA, multi-zone, production.

Run as a workload in your existing cluster. Scales horizontally, plugs into your ingress, your metrics stack, your identity. The shape your platform team already operates.

  1. Apply manifests
  2. Wire ingress + secrets
  3. Scale replicas
Best for · Production · regulated workloads

Same artefacts, every target

Low-footprint. Boring to install.

  • One image, one config schema. The Compose file and the Helm chart consume the same values.
  • No customer data leaves your perimeter. Identity stays federated with the one you already operate.
  • Pilot in an hour on Docker. Move to Helm without changing copy-pasted YAML around.

Ready to scope it

Tell us what you run. We'll pick the path.

Book a deployment review