My BeastDiscounts and news by email. Unsubscribe in one click.
Put mybeast-deploy in front of the deploy command you already use. It runs your script as it is and reports who ran it, from which machine, the commit, its log and how it ended. Each app and environment shows what is live now.
For developers and operations.
You sign up and pay for Deploys separately from hosting.
Prices are without VAT: VAT is added at checkout, where it applies. Plans renew each month or year until you cancel. Ask within 30 days of your first payment, or 14 days of a renewal, and you get it back in full. Sold by our reseller Paddle, which handles payment, VAT and invoices. Terms · Refunds
Pick Deploys and a plan, name your project and pay.
Put mybeast-deploy on your PATH, and give it the service's address and a server key from your project's settings.
Run mybeast-deploy run with the app, the environment and your usual deploy command. The app is added on its first deploy.
Follow the log on the deploy's page. If it went wrong, mybeast-deploy rollback runs your rollback command the same way.
| Starter€9 a month€90 a year | Team€25 a month€250 a year | Business€39 a month€390 a year | |
|---|---|---|---|
| Apps | 3 apps | 10 apps | 20 apps |
A new app's first deploy past the plan's limit still runs but is not recorded, and the apps you have keep deploying.
mybeast-deployDeploys run where you start them; the service holds no SSH keys. The server key never reaches the deploy command, secret-looking values on its command line are not sent, and an app's saved commands may hold no secret. A Telegram bot token, a Slack webhook and an Errors key are kept encrypted.
Your plan counts apps, and an app is added on its first deploy. Past the limit, a new app's first deploy still runs but is not recorded. The apps you have keep deploying, and a smaller plan takes none away.
There is no free plan and no test mode. The CLI comes with demo scripts that talk like a real deploy and change nothing, and your project's settings can send a test notice.
Any. mybeast-deploy runs the deploy command you already have, whatever it is written in. It needs bash 3.2 or later and curl. Anything else can report its deploys through the API with a server key.
On our servers in Germany. Deploys, their logs and your apps' settings are kept with no end date: nothing removes them on a schedule. The project's audit log is kept for 24 months.
No. Your deploy runs where you start it, as it always has. The service holds no SSH keys and never logs in to your servers.
Not your key: it is never handed to the deploy command. A secret-looking value on the command line, like DEPLOY_PASSWORD=…, is not sent, and what you type at a prompt never reaches the service. The log is kept as your script prints it, so keep secrets out of its output.
The deploy runs all the same, and mybeast-deploy says it was not reported. A log that did not all arrive is kept in a file on your machine. A deploy whose end never arrived is marked lost after 10 minutes.