What this guide helps you decide
- whether the user wants a one-time deployment or an ongoing workspace
- whether future changes should be guided or manual
- whether the draft spec should preserve richer intent for later
- how much responsibility should move into kombify Cloud
Install only
Choose install-only when you want StackKits to create a working baseline and then operate it yourself. This fits when:- you are comfortable with CLI workflows
- you want local ownership over changes
- you do not need ongoing guided recommendations
- you prefer to inspect generated files directly
Managed with kombify Cloud
Choose kombify Cloud management when you want the intent, target state, and future changes to stay visible in one place. This fits when:- you want guided recommendations
- you want to revisit decisions later
- you want status and change history in the dashboard
- you expect to add services, nodes, or custom domains over time
Decide later
If you are still discovering your needs, choose “decide later.” The finder can still capture intent and generate a first spec without forcing the operating model.Decision table
| Need | Install only | Managed with kombify Cloud |
|---|---|---|
| Fast first deployment | Good | Good |
| Ongoing recommendations | Manual | Guided |
| Future changes | CLI/spec workflow | Dashboard-assisted workflow |
| Good for beginners | Possible | Better |
| Good for advanced users | Strong | Strong when multiple environments exist |
How this maps to the finder
The finder uses the operating model to decide how detailed the resulting spec should be:- install-only keeps the recommendation close to the selected kit
- managed mode preserves more intent for future changes
- decide-later avoids locking the user into a workflow too early
