Production, defined in a
file in your repo.
Versioned, reviewed in the pull request and reproducible by anyone on the team. Your production setup is code, not tribal knowledge.
Start now — it's free
Only one person knows how production is set up
and she leaves in two weeks?
Production shouldn't live in someone's head. With Axebow it lives in a definition file next to your code: not just what runs, but how it's deployed, balanced, monitored and rolled back. Anyone can read it, change it and deploy it. Redeploying is restoring a file. Migrating is changing a line.
Versioned. Reviewed. Reproducible.
Redeploying is restoring a file
Lost an environment? Pull the definition from the repo and deploy it again. Same result, on any cloud, every time.
Migrating is changing a line
Change the target cloud in the definition and redeploy. No rewrite, no runbook, no lost weekend.
Definition file (DSL)
Modules, connectivity, dependencies, and also how it's deployed, balanced, monitored and rolled back. All in one file in the repo.
Versioned with the code
Every change to production has a commit behind it.
Reviewable in the PR
Infrastructure changes get the same review as your code.
Reproducible on any cloud
The same file deploys to OVHcloud, AWS, Azure or Aire.
Full API
Everything you can do in the dashboard, you can do from code.