Problem: You have configuration files and you’re not sure whether to use CUE, Nickel, or both.
Solution: conflow analyzes your configs, recommends the right tool, and orchestrates the entire pipeline.
# Instead of:
nickel export config.ncl > temp.json
cue vet schema.cue temp.json
cue export schema.cue --out yaml > deploy.yaml
rm temp.json
# Just:
conflow runIntelligent analysis - Recommends CUE vs Nickel based on complexity
Pipeline orchestration - Chain tools with dependency management
Smart caching - Only re-run what changed
Educational - Learn why certain tools fit certain problems
Type-safe - Catch errors before deployment
RSR Integration - Full Rhodium Standard Repository compliance checking
# Install
cargo install conflow
# Initialize
conflow init my-project
# Analyze existing configs
conflow analyze config.yaml
# Run pipeline
conflow run# .conflow.yamlversion: "1"name: "k8s-deployment"stages:
- name: "generate"tool:
type: nickelcommand: exportfile: config.ncloutput: generated/config.json
- name: "validate"tool:
type: cuecommand: vetschemas: [schemas/k8s.cue]input:
from_stage: generatedepends_on: [generate]
- name: "export"tool:
type: cuecommand: exportout_format: yamlinput:
from_stage: generatedepends_on: [validate]output: deploy/k8s.yaml$ conflow run
✓ generate (0.08s)
✓ validate (0.05s)
✓ export (0.03s)
Pipeline completed in 0.16s✅ Validating configuration
✅ Expressing constraints
✅ Merging configurations
✅ Simple transformations
✅ Generating configurations
✅ Complex logic needed
✅ Functions and abstraction
✅ DRY configuration
| Command | Description |
|---|---|
| Initialize project |
| Analyze config files |
| Execute pipeline |
| Watch mode |
| Validate pipeline |
| Show pipeline graph |
| Cache statistics |
| Clear cache |
| Check RSR compliance |
| List RSR requirements |
conflow init --template cue-validation # Simple CUE validation
conflow init --template nickel-generation # Nickel config generation
conflow init --template full-pipeline # Generate → validate → export
conflow init --template kubernetes # Kubernetes manifests
conflow init --template multi-env # Multi-environment configsconflow includes full RSR (Rhodium Standard Repository) integration:
Compliance checking - Validate against RSR requirements
Auto-remediation - Automatically fix common issues
Badge generation - Generate compliance badges for CI
Diff reports - Track compliance changes over time
# Check compliance
conflow rsr check
# Auto-fix issues
conflow rsr check --fix
# Generate badge
conflow rsr check --badge badge.svg# Using Nix (recommended)
nix develop
# Using just
just build # Build
just test# Run tests
just check # Run all checks
just install # Install locallyCLAUDE.md - AI assistant guidance
CONTRIBUTING.md - Contribution guidelines
SECURITY.md - Security policy
GOVERNANCE.md - Project governance
CODE_OF_CONDUCT.md - Code of conduct
This project follows Rhodium Standard Repository guidelines:
✅ Memory-safe language (Rust)
✅ Offline-first design
✅ Reproducible builds (Nix)
✅ Comprehensive documentation
✅ SPDX license headers
✅ Security policy
✅ TPCF contribution framework
This project is dual-licensed under:
MPL-2.0-1.0 License
Apache License, Version 2.0
See LICENSE.txt for details.
Contributions are welcome! Please read our Contributing Guide first.
See TOPOLOGY.md for a visual architecture map and completion dashboard.