Deployment & Operations

Your integrations. Your infrastructure. Your rules.

Uniflox produces standard Go applications, so you can run them anywhere Go runs.

Deployment options

Ship it the way your platform team prefers.

Native binary

Cross-compile for Windows, Linux or macOS on x86 or ARM. A single file with no dependencies.

Docker container

A multi-stage Dockerfile is generated with every service, producing small images for fast pulls.

Kubernetes / OpenShift

Deploy the containers like any other microservice. The /health endpoint supports liveness and readiness probes.

Any cloud or on-premises

AWS, Azure, Google Cloud, private cloud or bare metal.

Windows Linux macOS Docker Kubernetes AWS Azure Google Cloud On-premises
Build once, run anywhere

Standard Go. Standard tooling.

Exported services build with the Go toolchain and ship with a multi-stage Dockerfile, so they fit straight into the pipelines you already run.

  • Cross-compile for x86 or ARM, with an optional static build
  • Small images for fast pulls
  • A /health endpoint for liveness and readiness probes
# Cross-compile for Linux on ARM
GOOS=linux GOARCH=arm64 CGO_ENABLED=0 go build -o order-api .

# Run with environment-based configuration
PORT=8081 DB_URL=postgres://… ./order-api

# Check health
curl localhost:8081/health
{"status":"UP"}
Illustrative example. Generated output varies by project.
Designer installation

Install the Designer on your own infrastructure.

The Uniflox Designer installs on-premises with a Windows MSI installer or an Ubuntu/Debian package. RHEL and CentOS are also supported.

Windows

MSI installer

Ubuntu / Debian

DEB package

RHEL / CentOS

Supported

Operations

Operate integrations like any other service.

  • Environment-based configuration

    Environment-variable-based configuration that fits your CI/CD and secrets tooling.

  • Structured logging

    Structured logging in every generated service.

  • Versioning and rollback

    Flow versioning, publishing and rollback.

  • Health checks

    A /health endpoint for load balancers and orchestrators.

Illustrative example.

Why it matters

Lighter services, lower bills, familiar tooling.

Faster cold starts

Faster cold starts for autoscaling and serverless-style workloads.

Lower infrastructure cost

Lower infrastructure cost from a smaller CPU and memory footprint.

No runtime license

No runtime license to buy per core or per worker.

Standard DevOps tooling

Build, scan, sign and deploy the same way as your other services.