"Deploy" is one word for five jobs: hosting, a database, authentication, HTTPS, and a way to ship updates. Here is what each one means, and the shortcut that turns all five into one command.
| Job | Traditional answer | On Benmore |
|---|---|---|
| Hosting | VPS, container platform, or PaaS | Included, per-app subdomain |
| Database | Managed Postgres/MySQL, connection strings | Included, per-app, migrations automatic |
| Auth | Auth provider SDK + integration work | Included: email, OTP, OAuth, MFA, roles |
| HTTPS | Certificates, renewals, redirects | Automatic, custom domains too |
| Shipping updates | CI/CD pipeline | Push a file, live in a second; promote dev to prod |
brew install Benmore-Studio/benmore/benmore
benmore login
benmore deploy
From any Benmore app directory, that creates the app on first run, ships every file, and returns a live URL on a hosted dev instance. Iterate against the live URL, then benmore promote to production and benmore domain for your own domain. The full walkthrough is in deploying from your terminal.
If the app does not exist yet, skip the code entirely: describe it in the builder and deploy is something that already happened by the time you finish reading the first build log. Starting from a spreadsheet? That is its own guide. Starting from code an AI wrote? That one too.
The part most guides skip: what happens after the first deploy. Benmore apps come with per-app git history and one-command rollback, separate dev and prod instances with their own databases and secrets, automated backups, audit logs, request logs, error capture, and zero-downtime updates. None of it is configuration you write; it is what the platform does.
Deploy your first app free