BuildMaster’s Features
When releases are scattered across disconnected tools and rigid, one-size-fits-all pipelines, teams lose visibility, speed, and confidence. BuildMaster fixes this with a single source of truth, multi-cadence release tracks, and guided self-service deployments; all built to fit the infrastructure you already run.
Central Command Center
When your release process is fragmented across separate tools, teams struggle to see the full picture and move with confidence. BuildMaster fixes this by sitting on top of the tools you already run, acting as the connective layer between them, and giving you a single real-time view of what’s happening across your entire portfolio.
Connected Toolchain
Unify your CI/CD, Git, issue tracking, and SCA tools together into a single source of truth, so stakeholders get answers without needing access to every underlying tool.
CI/CD
Integrate with GitHub, GitLab, Azure DevOps, Jenkins, and more, with build artifacts imported automatically
Git
Connect your repositories so branches, commits, and code changes are always tied back to the release they belong to
Issue Tracking
Connect to issue trackers like Jira, so open issues are automatically linked to the builds and releases they affect
SCA
Connect software composition analysis tooling so dependency and vulnerability data shows up directly in your release view
Real-Time Visibility Across Your Entire Portfolio
BuildMaster gives you a real-time view across your entire portfolio, so you always know what’s happening across every application without hunting through multiple tools.
Unified Portfolio View
See every application, build, and release in one place
Real-Time Status Tracking
See which builds and deployments are in progress, awaiting approval, or failing across all applications, without digging through separate tools
Relevant Issues
See which issues are tied to each release in real time, without logging into your issue tracker
Code Changes
See Git changes between builds, releases, branches, and commits in the context of what’s shipping
Multi Cadence Releases
Not every release carries the same risk, but most teams handle routine fixes and major changes through the same process, so small changes get stuck behind big, risky ones. BuildMaster fixes this with multi cadence release tracks; routine pipelines for small, scheduled changes and major pipelines for large, risky changes.
Routine Releases for Low Risk Changes
BuildMaster lets you schedule low-risk changes, small fixes and routine maintenance, on a fixed, predictable release pipeline.
Routine Scheduling
Routine releases stay on schedule regardless of what’s happening on the major track
Continuous Iteration
Ship small, low-risk changes continuously, one release at a time
Major Releases for High-Risk Changes
BuildMaster gives high-risk changes and large features their own process, with a flexible schedule to take the time they require.
Risk-Based Process
Major releases follow whatever process and timeline the risk actually demands, without being forced into a routine release schedule
Independent Releases
Major releases sit alongside routine releases, but move on their own timeline without ever delaying, or being delayed by the routine track
Release Calendars
BuildMaster shows all releases in a release calendar, so all releases for every application are visible side by side.
Portfolio-wide Scheduling
See all releases for every application in your portfolio scheduled on a calendar, side by side, so everyone knows exactly when the next release ships
Dedicated Release Tracking
Track major release progress and target windows separately to avoid cluttering your routine schedule
Self Service Delivery
Deployments often depend on a handful of specialists who know the tribal knowledge and manual steps required to ship safely. BuildMaster offers a self-service deployment experience incorporated into every pipeline, so any team can move releases forward confidently, without waiting on specialists or manual coordination.
Deployments Anyone Can Own
BuildMaster guides every user through what’s needed, what’s blocking them, and what to do next.
Guided Deployment Steps
Clear, guided deployment experience that shows users what’s required, and what’s blocking progress
Built-In Deployment Gates
Approvals, deployment windows, and quality gates built directly into the pipeline, not buried in documentation
Frictionless Approvals & Rollbacks
Stakeholders can review, approve, or roll back releases without bottlenecks
Flexible Override Controls
Teams can easily override deployment blocks when they genuinely need to
Clear Governance
BuildMaster enforces rules and compliance automatically, so every release follows the same process.
Automated Compliance Gating
Deployment gating enforces compliance, testing, and sign-off requirements automatically
Criteria-Based Blocking
Block deployments when issues aren’t resolved or don’t meet defined criteria
Configurable Deployment Windows
Configure deployment windows so releases happen at the right time, every time
Enforced Process Consistency
Consistent process applied across every release; no relying on someone to remember the rules
Build, Customize, and Evolve Your Process
BuildMaster lets you build, adapt, and grow your pipelines as your team’s needs change.
No-Code Pipeline Builder
Pipelines configured through a visual interface; no custom code or workflow engines required
Bring Your Own Scripts
Bring the existing scripts and tools your teams already use and integrate them into BuildMaster
Otterscript Visual Editor
Otterscript and its visual editor lowers the barrier for non-engineers to create their own scripts
Evolve Without Rebuilding
Teams can evolve their deployment process over time without redesigning from scratch
Built to Fit Your Organization
BuildMaster works with the infrastructure, tools, and security requirements you already have, so you can adopt Lean Platforms without starting from scratch.
Modern and legacy platform support
BuildMaster supports almost all projects built on both new and legacy development platforms, including .NET (.NET Console Applications, ASP.NET MVC & WebForms, .NET Core, NuGet Packages, Running NUnit, xUnit, MSTest, and more with VSTest Runner, Running Unit Tests with NUnit Runner, Entity Framework, FxCop, Web Deploy Packages), Java (Maven, Ant, Tomcat, WildFly/JBoss EAP, Gradle, Jetty, JUnit Tests, Scala), Node.js, Docker, PHP, Python, WordPress, and more.
BuildMaster offers out-of-the-box integration with a wide variety of tools including build automation, issue tracking, CI tools, GitHub, GitLab, TeamCity, etc.
Deploy on-premises, in the cloud, or both
BuildMaster is an automated deployment tool that can target virtually any platform used by any application in your organization including; Windows (Windows Service and IIS), Linux or Unix Server Using the SSH Agent, Azure (Cloud Services Packages and Deployment using az.exe), Terraform, FTP, Kubernetes, and mobile apps.
Enterprise-grade security and access control
BuildMaster’s role-based access control lets you scope access to applications and environments so that you can control who builds and deploys different applications in different contexts. You customize and create granularly scoped roles that let everyone see the details they need while keeping safe things like debug-level logs.
By using BuildMaster’s Software Composition Analysis integration, you can also identify and mitigate vulnerabilities in third-party software components.
Easy Installation and Management
The installation and management of Inedo’s BuildMaster are designed to be easy and scalable, with high availability and load-balancing capabilities.
Simple Upgrades or Downgrades
BuildMaster can be installed and upgraded quickly and easily using the Inedo Hub or a Docker container. Rolling back (downgrading) is just as easy.
High Availability & Load Balancing
BuildMaster can be configured as a highly available, load-balanced server cluster, which means no single point of failure, and build/deployment executions can be evenly distributed across agents.
