Productify Documentation
Welcome to the Productify documentation. Productify is a comprehensive multi-tenant configuration management platform with autoscaling capabilities.
Early Development
Productify Framework is currently in early development stages. While functional, it may contain bugs and undergo breaking changes. Use with caution in production environments and ensure thorough testing for your specific use cases. See the current known issues and limitations.
Quick Links
- API Reference - Complete GraphQL and REST API documentation
- Manager Guide - Core platform features and usage
- CLI - Command-line interface for project management
- Integration - Frontend and backend integration libraries
- Autoscaler - Intelligent workload optimization
- Proxy - Traffic routing and TLS management
- Deployment - Production deployment guides
Getting Started
Choose your setup:
- Zero-to-App Local Quickstart -
pfy dev up— the whole platform in one command, both dev loops, a trigger firing locally - Docker Compose - Quick local setup
- Nomad - Production-ready orchestration
A one-command local platform (pfy dev up) plus the two documented dev loops now ship — see the Zero-to-App Local Quickstart.
Future Support
Kubernetes deployment support is planned for a future release.
Platform Model
Single deployment, multi-app, multi-tenant. One proxy instance serves every application and tenant, and one running backend per application serves all tenants.
Planned model vs. shipped model
The target model — applications defined once per project and enabled per tenant, with first-class dev/staging/production environments, and proxy vhosts rendered from Manager data and reloaded live — is not what ships. Today the hierarchy is Project → Tenant → Application (an application belongs to one tenant, so a tenant is in practice the environment), and the proxy's vhosts are hand-authored. See Multi-tenancy and Known Issues.
Architecture
Productify consists of four main components:
- Manager - Multi-tenant configuration API with a fixed role vocabulary, and trigger execution (customer self-service and invitations are planned, not implemented)
- CLI - Command-line interface for project, tenant, application, pilet, and Nomad job management (a local platform and rendered deployment artifacts are planned)
- Autoscaler - SARIMAX forecasting with MILP optimization; scaling policies are hand-written into Nomad jobs
- Proxy - Caddy-based reverse proxy with automatic HTTPS and a hand-authored Caddyfile (tenant switching and Manager-rendered config are planned — see Known Issues)
Server libraries are official for Go and Node.js/Express; the browser client is framework-agnostic with Vue and React packages — see Integration.