* Configuration Management - Use Chef to create a code-based model for your infrastructure. Consistently deploy servers and scale applications. Align resources with specific policies and business goals. Save time by automating manual tasks. * Cloud Management - Chef gives you the flexibility you need to manage a dynamic, cloud-based infrastructure, no matter which cloud provider you use now-or in the future. * Devops & Chef - DevOps is a cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners. * Chef Compliance - How can you ensure that your systems are secure without slowing down development and deployment of business-critical systems? Use Chef Compliance to express your infrastructure security requirements as code and automate the assessment and remediation of your IT infrastructure. * Continuous Delivery - Continuous delivery is an automated process that gives you control over your software and infrastructure deployments. With it, you time your releases to meet your business requirements. You're not hampered by slow, often faulty, manual processes. * Continuous delivery needs a collaborative relationship among all of a project's stakeholders. When used for modern, full-stack deployments, such a culture is called DevOps. The open, direct communication advocated by DevOps means that everyone involved, such as developers, operations teams and managers, work together to clearly define the code's purpose and requirements. DevOps also reduces the number of handoffs, which cause delays and wasted effort.

* Technology Awareness - One reason TeamCity is dubbed an "Intelligent CI server" is its approach to integration. When we say we support a tool, we mean it in every way possible. For example, support for Visual Studio projects provides automatic detection of tool versions, testing frameworks support, code coverage, static code analysis, and more. And the best thing is, you get all this support without installing any plugins and with no modifications to build scripts! * Configuration - Skillful software developers try to avoid code duplication; similarly, build engineers avoid duplication of settings. TeamCity understands this and provides several ways to reuse settings. * VCS Interoperability - TeamCity version controls systems integration is comprehensive. It’s hard to imagine a project whose source code couldn’t be retrieved by TeamCity. * Key Integrations - It’s impossible to imagine a great CI and CD server without an integration with some key tools like your version control, you issue tracker, your build tool, and your package repository. TeamCity takes it very seriously to provide full support for these key integrations. * Build History - We believe that keeping a history of builds, changes and failures is crucial to the success of any software development process. TeamCity enables you to run history builds, see statistics and test history reports, as well as pin, tag, and add builds to favorites. All of the changes are accumulated in the change log. * Extensibility and Customization - TeamCity provides you with multiple ways of interaction, customization, and extending your server. Use service messages in your build scripts, interact via REST API, or create plugins for TeamCity using Open API. * Cloud Integrations - TeamCity takes advantage of cloud computing by dynamically scaling out its build agents farm on Amazon EC2, Microsoft Azure, and VMware vSphere. * Build Infrastructure - Imagine a conveyor belt of changes from developers and a bunch of testers taking the changes, verifying them and complementing these changes with verification results. TeamCity is such a conveyor, except that testers are replaced with Build Agents. * System Maintenance - TeamCity helps you maintain your CI server healthy and stable even when no builds are running so that you don’t waste your time when it’s needed the most. It provides you with useful reports like Disk Usage, Build Time, and Server Health reports