KEEP YOUR SCRIPTS
Your language. Your workflow.
Run ordered Bash, PowerShell, and Python steps. Bring the scripts you already know and give them a repeatable deployment process.
YOUR INFRASTRUCTURE. YOUR DEPLOYMENTS.
Your scripts.
A better way to deploy.
Bring your scripts. Keep your infrastructure.
Turn deployments into a workflow you can see, repeat, and trust.
Self-hosted Open source · MIT Script-first
View full screenshot Actual DurpDeploy application · demo data
BUILT FOR THE WAY YOU WORK
Bash PowerShell Python Docker / Podman Your servers
FAMILIAR SCRIPTS. A CLEARER PICTURE.
All the flexibility.
A lot less guesswork.
Your scripts already do the work.
Give them a place to work together.
CAPTURE THE RELEASE
Know what you’re shipping.
Capture project steps and variables in a release. Each deployment keeps its own snapshot, so its execution history stays intact.
DEPLOY WITH INTENTION
A pause before production.
Add approval gates, review generated artifacts, and inspect verification results. Cancel or roll back when a deployment needs another look.
REACH YOUR ENVIRONMENTS
One place. Multiple targets.
Route work to matching remote agents by environment and capability over pinned mTLS. Run server steps in Docker or Podman containers.
MAKE OPERATIONS REPEATABLE
Less “who ran that script?”
Turn routine work into runbooks, reuse step templates, and schedule deployments. Keep live logs and an audit trail close at hand.
CONNECT THE PIECES
Fits into your toolkit.
Use the JSON API with bearer tokens. Send notifications to Slack, email, Gotify, or Discord, and add optional OIDC and browser MFA.
FROM PROJECT TO PRODUCTION
A clear path to deployed.
- 01
Bring your scripts
Create a project and arrange script steps in the order they should run.
- 02
Set the environment
Define your environments and their variables, with masking for secrets.
- 03
Capture a release
Snapshot the project configuration into a versioned release.
- 04
Deploy and follow along
Choose an environment, follow live logs, and review approvals and verification.
Build with your existing tools. Let DurpDeploy handle the deployment workflow.
A LOOK INSIDE
Everything in context.
Projects, releases, and logs.
An interface built around the work.
Screenshots from the project’s demo fixtures. Open an image to take a closer look.
YOUR STACK. YOUR CALL.
Small footprint.
Your infrastructure.
A Go binary, a web interface, and SQLite by default. Use PostgreSQL or SQL Server when that fits your stack. Keep deployment orchestration on infrastructure you control.
Find your setup Self-hosted MIT licensed SQLite by default JSON API
MAKE IT YOURS
Your next deployment
starts here.
Pick the guide that fits your setup.
Build something, then ship it.
Actively being built. DurpDeploy doesn’t have a stable release yet. Review the versioning guide before installing or upgrading.
SELF-HOSTING
Docker Compose
Run DurpDeploy with Caddy for HTTPS and Litestream for SQLite backups. Follow the complete configuration and bootstrap steps.
Installation guideLOCAL DEVELOPMENT
Build from source
Use Go 1.26+, Node.js, the templ CLI, and Docker or Podman. Build locally, create your first admin, and explore the application.
Development guideYOUR INFRASTRUCTURE
Kubernetes & agents
Host the server using the Helm chart. Pair standalone agents to run executable steps on the environments you manage.
Helm chart guideNeed to connect a target? Read the remote agent guide Source and guides are on GitLab; sign-in may be required.
What is DurpDeploy?
DurpDeploy is a self-hosted, single-binary deployment tool for Bash, PowerShell, and Python scripts. It organizes projects, environments, releases, and deployments in a web interface, with live logs and a JSON API.
Is there a stable release?
Not yet. DurpDeploy is under active development. Check the source repository and its versioning guide for current build information, compatibility, and upgrade guidance before choosing a version.
Does DurpDeploy replace my CI system?
DurpDeploy focuses on deployment orchestration and repeatable operations. It does not provide a CI/build pipeline or parallel step execution. Keep your existing build process and use DurpDeploy to orchestrate deployment steps.
Where do my scripts run?
Server-side steps run in containers and require a container image and a ready Docker or Podman runtime. Remote steps run on matching active agents. There is no SSH deployment target or automatic local fallback for remote work. The Helm chart hosts the server; it does not add a Kubernetes-native execution backend.
Which databases are supported?
SQLite is the default and suits a single application instance without a separate database server. PostgreSQL and SQL Server are also supported. Follow the deployment and backup guides for configuration and maintenance.
Is DurpDeploy open source?
Yes. DurpDeploy is licensed under MIT. Read the code, report an issue, or contribute through the GitLab repository. The authoritative self-hosted GitLab instance may require sign-in.
OPEN SOURCE. OPEN TO WHAT’S NEXT.
Good scripts.
Great deployments.
Explore the code. Try it on your infrastructure.
Help shape what comes next.