profitctl is a CLI for profit-first unit economics simulations.
It helps teams model fixed + variable costs, simulate growth and stress scenarios, validate profitability covenants, and (optionally) detect services/dependencies from source config files using an LLM.
- Canonical repository:
github.com/IntelIP/ProfitCtl - Go module path:
github.com/IntelIP/ProfitCtl
simulate: run 12-month scale + Monte Carlo stress simulationscompare: evaluate multiple pricing scenarios side by sidecalibrate: normalize YAML, JSON, or CSV calibration exports into ProfitCtl calibration artifactsvalidate: validate config structure and rulesdetect: scan repository config files and return JSON service/dependency analysis- pricing modes:
tiered,mix, andhybrid - workspace-aware pricing and minimum-floor scenario modeling
- payment-fee modeling with monthly vs annual billing mix
- calibration deltas for modeled vs actual revenue and fees
calibration_filesupport for external calibration artifacts- explicit
billable_userssupport for hybrid seat-based contracts - booked vs operating margin reporting for one-time-heavy contract scenarios
- full-economics reporting across delivery, productization, and adoption cost layers
- Output formats: human CLI, JSON, Markdown
- CI/CD via Woodpecker (Hostinger VPS + builder pool)
curl -fsSL https://raw.githubusercontent.com/IntelIP/ProfitCtl/main/scripts/install.sh | bashbrew tap IntelIP/profitctl
brew install profitctlSee Install Guide for pinned versions, Homebrew, custom prefixes, and source-based installs.
git clone https://github.com/IntelIP/ProfitCtl.git
cd ProfitCtl
go build -o profitctl .
./profitctl --helpgo install github.com/IntelIP/ProfitCtl@latest# simulate
profitctl simulate -f examples/valid_profit.yml
# mix-mode open-core pricing
profitctl simulate -f examples/mix_profit.yml
# hybrid contract pricing with pilot
profitctl simulate -f examples/hybrid_profit.yml --json
# compare steady-state vs pilot hybrid contracts
profitctl compare examples/hybrid_steady_profit.yml examples/hybrid_profit.yml
# normalize a calibration export
profitctl calibrate --input examples/calibration_exports/hybrid_profit_calibration.csv
# strict config validation
profitctl validate -f examples/valid_profit.yml
# detect services/dependencies from repo files
OPENROUTER_API_KEY=... profitctl detect --path . --out detect-report.jsonCanonical public release artifacts are published on GitHub Releases:
https://github.com/IntelIP/ProfitCtl/releases- each release includes:
- per-platform archives
- per-platform SPDX JSON SBOMs
- detached Cosign signatures
SHA256SUMSplus a detached signatureprofitctl-release-cosign.pubfor offline verification
Operational mirrors may also publish to:
https://downloads.intelip.co/profitctl/releases/<tag>/https://downloads.intelip.co/profitctl/current/
The open-source core gives teams a local CLI to model pricing, recurring-margin risk, and contract safety before they ship pricing or sign deals.
The paid layer should sit on top of that core through hosted workflows, collaboration, policy enforcement, and support, not by weakening the local product.
The repo now includes IntelIP-specific economics scenario packs for conservative, target, stress, paid-pilot, and tight-free rollout analysis.
- calibration notes:
benchmark_scenarios/intelip_model_calibration_notes.md - cost inventory:
benchmark_scenarios/intelip_tooling_cost_inventory.md - rollout recommendation pack:
benchmark_scenarios/intelip_ops_pricing_pack.md
- Documentation Index
- Install Guide
- Quick Start
- Architecture
- Open-Core Packaging
- Open-Core Roadmap
- Benchmark Scenarios
- Full Economics Cost Layers
- IntelIP Ops Pricing Pack
- Growth Assets
- Benchmark Outreach Pack
- Value Proposition
- Design-Partner Offer
- Outreach Message Templates
- Evaluator Session Template
- Adoption Dashboard
- Design-Partner Operating System
- MVP Pricing Release Guide
- Woodpecker + Hostinger Runbook
See CONTRIBUTING.md.
See SECURITY.md.
ProfitCtl can publish PR security findings into the separate appsec-mvp service.
- PR scans run in Woodpecker via
semgrep,trivy,gitleaks, andosv-scanner - findings are uploaded to
appsec-mvp - GitHub PRs receive:
- commit status
appsec/mvp - check run
AppSec MVP Review - selective inline comments for high-confidence findings
- commit status
Required Woodpecker secret:
APPSEC_API_URLAPPSEC_API_TOKEN
Required appsec-mvp runtime config:
GITHUB_APP_IDGITHUB_APP_PRIVATE_KEY_PEMorGITHUB_APP_PRIVATE_KEY_PATHGITHUB_WEBHOOK_SECRET
The initial /.appsec.yml policy is set to report_only for rollout validation, and the helper scripts default APPSEC_STRICT_API to false so AppSec service outages do not hard-fail PRs during onboarding. Switch the policy to enforce and set APPSEC_STRICT_API=true once the integration is stable.
MIT. See LICENSE.