Coordinate source changes
Connect
SPIRITT
DeployHQDeployHQ
Make deployment operations deliberate
Coordinate DeployHQ projects, build configuration, server groups, and verified deployment follow-through. Give SPIRITT the outcome and put your connected account to work.
What you can do with DeployHQ.
Prepare consistent delivery
Configure projects, repositories, servers, commands, and exclusions from an approved release setup.
Know what changed
Connect repository revisions and deployment history to a source-linked operations view.
Control configuration rollouts
Deploy configuration files to named targets and follow the recorded deployment through its outcome.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for your DeployHQ workflows, connected apps, and finished outcomes.
02
Connect DeployHQ
Connect DeployHQ and select the account and records your agent should work with.
03
Hand over a mission
Describe the result, scope, and handoffs. SPIRITT builds the workflow and follows the work through.
Hand over a mission.
Choose a mission. Make it yours.
Put DeployHQ to work.
Make deployment operations deliberate
Questions
DeployHQ, with SPIRITT.
01What can SPIRITT do with DeployHQ?+
Coordinate DeployHQ projects, build configuration, server groups, and verified deployment follow-through. Configure projects, repositories, servers, commands, and exclusions from an approved release setup. Connect repository revisions and deployment history to a source-linked operations view.
02Can SPIRITT build an app around DeployHQ?+
Yes. Ask it to "build a deployment operations board". Build a DeployHQ operations board joining projects, deployment history, server groups, and repository revisions. Route failed or unexpected releases to Slack with the exact target and commit context, and track engineering follow-ups until the recorded deployment and application checks are resolved.
03How does SPIRITT handle a configuration rollout?+
It reads current files and target groups, changes only the approved configuration, starts a configuration-file deployment, and checks deployment history for the outcome. A created deployment is tracked separately from a successful rollout.
04How does DeployHQ work with my other apps?+
Connect the apps your mission uses. GitHub to coordinate source changes; GitLab to link release revisions; Slack to own deployment handoffs. SPIRITT carries the handoff through and checks the result in the destination.
05What should I know about the DeployHQ connection?+
DeployHQ can configure delivery and create configuration-file deployments. Configuration-file deployment is separate from a code release. Server-group auto-deploy settings can affect future releases, and changing a project permalink requires updating its repository webhook.
06How do I get started with DeployHQ?+
Open a SPIRITT workspace, connect DeployHQ, and name the target records and desired outcome. Start with "Build a deployment operations board" or bring your own mission. Set the scope for changes and external actions, then let your agent run the work.