Productify

Appearance

Deployment Overview ​

This section covers deploying the complete Productify Framework stack across different platforms.

Early Development

Productify Framework is in active development. While the deployment guides are functional, expect potential breaking changes and ensure you have proper backup and rollback strategies in place before deploying to production.

Components ​

The Productify Framework consists of three main components:

Manager ​

Core management platform for multi-tenant SaaS:

  • Backend: Go-based API server with GraphQL
  • Frontend: Vue.js 3 UI
  • Database: PostgreSQL
  • Run Modes: API, Executor, or Both

Manager Deployment Guide

Autoscaler ​

Intelligent predictive scaling:

  • Nomadscaler Plugin: Go-based Nomad Autoscaler strategy plugin (productify-scaler)
  • Optimizer Service: Python-based MILP optimizer
  • Metrics Integration: Nomad APM, Prometheus

Autoscaler Deployment Guide

Proxy ​

Dynamic reverse proxy and load balancer:

  • Caddy: HTTP/2, automatic HTTPS
  • Service Discovery: Nomad integration
  • Load Balancing: Health-checked upstreams

Proxy Deployment Guide

Architecture Overview ​

For detailed system architecture, network topology, and deployment models, see the Architecture Guide.

Launch Criteria ​

The framework's "Early Development" warnings and the website "early access" badge are dropped only when an enforced exit-criteria gate reports green — never by manual sign-off. See Launch Criteria for the criteria, their verifiable signals, and how the gate blocks a premature launch flip.

Generated Deployment Artifacts ​

Since the Wave 3 release train, deployment artifacts render from specs — you maintain inputs, not HCL or Caddyfiles. See Generated Artifacts for the full workflow.

  • Application jobs — each application's Nomad job (ports, health checks, migration prestart, secrets templates, scaling policy) renders from a deployment spec stored on the Manager's Deployment entity: pfy nomad render|deploy.
  • Platform stack — Manager, proxy, identity provider, and database jobs (or the Compose equivalent) render from one install.yaml: pfy platform render|deploy.
  • Proxy configuration — per-application vhosts render from Manager data and push live through Caddy's admin API; the install-level prelude (OAuth portal, global options) renders from install.yaml.
  • Drift detection — rendered files carry a GENERATED header with the spec hash; pfy deploy diff compares spec vs. repo vs. cluster, and CI fails on hand-edited drift (pfy proxy diff|sync for the proxy).

Rendered outputs are committed, deterministic, and never contain secrets (they reference Nomad variables / environment instead).

Deployment Platforms ​

Nomad (Production) ​

Recommended for production deployments

See Nomad Deployment for complete guide with service discovery, horizontal scaling, and zero-downtime deployments.

Docker Compose (Development) ​

Recommended for development and testing

See Docker Compose Deployment for quick local setup with minimal resource requirements.

Manager Run Modes ​

The Manager can run in three modes:

  • both - Single process for development (API + Executor)
  • api - Horizontally scalable API instances for production
  • executor - Single dedicated trigger execution instance

For detailed configuration, see Manager Deployment.

Deployment Strategies ​

For deployment patterns including blue-green, canary, and rolling updates, see the Architecture Guide - Deployment Strategies.

High Availability ​

For complete high availability setup including database replication, application redundancy, and proxy HA, see the Architecture Guide - High Availability.

Monitoring & Observability ​

For comprehensive monitoring setup including metrics collection, centralized logging, health checks, and alerting, see the Architecture Guide - Monitoring.

Centralized logging ships as ready-to-run configuration (Loki + Promtail) for both the Compose and Nomad paths under deployments/ops/logging/ — see Architecture Guide - Logging.

Security ​

For security best practices including network security, secrets management, and access control, see the Architecture Guide - Security.

Operations ​

For incident response, keyed to the shipped alert rules and log/backup tooling, see the Incident Runbook. For severities, escalation, and where alerts land, see the On-Call Guide.

Backup & Recovery ​

For backup strategies, disaster recovery planning, and RTO/RPO guidelines, see the Architecture Guide - Disaster Recovery.

Next Steps ​

  1. Choose your deployment platform (Nomad or Docker Compose)
  2. Review architecture diagram
  3. Deploy Manager
  4. Deploy Proxy
  5. Deploy Autoscaler
  6. Set up monitoring