DevOps agents should know your team's infrastructure preferences

DevOps workflows involve strong opinions on tools, providers, and configurations. pref0 learns infrastructure preferences so DevOps agents follow your team's conventions.

What pref0 learns

Real corrections pref0 extracts and compounds across conversations.

"Use Terraform, not CloudFormation"

iac_tool: terraform0.70

"Deploy to ECS Fargate, not EC2"

compute: ecs_fargate0.70

"Always use multi-stage Docker builds"

docker: multi_stage0.70

"GitHub Actions for CI, not Jenkins"

ci_cd: github_actions0.70

"Use environment variables, not config files"

config_method: env_vars0.40

"Always add health check endpoints"

best_practice: health_checks0.40

Example conversation

user

Set up CI/CD for this new service

assistant

Here's a Jenkins pipeline configuration for your service...

user

We use GitHub Actions, not Jenkins. Please redo this.

pref0 extracts the correction from this conversation and adds it to the user's preference profile. Next time, the agent gets it right.

Benefits

Tool consistency

The agent always suggests the right IaC tool, CI system, and cloud provider for your team.

Convention enforcement

Infrastructure conventions like Docker multi-stage builds are remembered and applied automatically.

Org-wide preferences

Set infrastructure preferences at the org level so every engineer gets consistent suggestions.

Faster scaffolding

New services start with the right configuration from the first prompt. No corrections needed.

Other use cases

Stop re-correcting. Start learning.

Your users are already teaching your agent what they want. pref0 makes sure the lesson sticks.