What one-click deployment is, who it is for, and how it works: deploy a full-stack app, redeploy, auto-deploy on git push, and roll back in one click.
What is one-click deployment?
One-click deployment packages everything a release needs behind one button: building the app into a container, provisioning its database and storage, wiring secrets and connection strings, and publishing it at an HTTPS URL. You configure the app once; after that, shipping a new version, redeploying, or rolling back is a single action instead of a runbook.
Who it is for
Founders and small teams without a DevOps engineer, developers who want push-to-deploy without writing a pipeline, people shipping apps built with an AI app builder, and agencies launching client apps. It also suits larger teams for internal tools and previews, while their CI pipelines handle apps that need tests and approvals first.
What happens when you click Deploy
NEXUS AI detects the framework and builds the container, generating a Dockerfile if the app has none. It starts the databases and workers you chose, injects DATABASE_URL and your secrets, runs a health check, and publishes the app at an HTTPS URL, with build and runtime logs you can follow as it goes.
When to use it, and when to add more
Use one-click deployment for prototypes, MVPs, internal tools, previews, and small production apps where speed matters most. Once an app needs tests or approval before release, keep the one-click controls for redeploys and rollbacks, and add a CI step that runs your tests and then deploys, or limit production deploys to specific roles.
Push to deploy: zero clicks
Connect a GitHub repository, set a branch allowlist, and turn on Auto Deploy. Every push to an allowed branch is verified by its webhook signature and queued as a deployment, and webhook delivery logs show what happened for each push.
One click after launch
The deployment page puts the everyday actions one click away: Redeploy with the same configuration, Roll back to a previous version (Pro and above), Stop and Start, Scale replicas, and set an auto-destroy time for preview environments. Each one is also a single CLI command or MCP tool call.
One click, one command, or zero
First deploy from the dashboard
Set the app up once in the deploy form; every later deploy is a button.
Open a project and choose Deploy Full App, or click Deploy in the AI Builder.
Pick the source (repository, ZIP, or folder) and any databases, Redis, or a worker.
Click Deploy and follow the status until the public URL is live.
Connect a GitHub repository, or choose a ZIP, folder, or AI Builder project.
Set the build and start commands, databases, and environment variables once, or keep the detected defaults.
Click Deploy, or turn on Auto Deploy so each push to an allowed branch deploys.
Redeploy, roll back, scale, or stop the app in one click from the deployment page.
Every one-click action, three ways
Action
Dashboard
CLI
MCP tool
Deploy
Deploy Full App, or Deploy in the AI Builder
nexus deploy source
nexusai_deploy_source
Redeploy
Redeploy
nexus deploy redeploy
nexusai_deploy_redeploy
Roll back (Pro and above)
Rollback
nexus deploy rollback
nexusai_deploy_rollback
Stop and start
Stop, Start
nexus deploy stop, nexus deploy start
nexusai_deploy_stop, nexusai_deploy_start
Scale
Scale
nexus deploy scale
nexusai_deploy_scale
Preview expiry
Auto destroy, Change
nexus deploy auto-destroy
nexusai_deploy_auto_destroy
One-click deployment vs a CI/CD pipeline
One-click and push-to-deploy
CI/CD pipeline
Setup
Minutes: connect a repo or click Deploy
A pipeline file and runner configuration
Tests before release
Run them yourself, or add CI
Built into the pipeline
Best for
Prototypes, MVPs, internal tools, previews, small production apps
Apps with test suites, approvals, and several environments
On NEXUS AI
Deploy button and GitHub auto-deploy
GitHub Actions running nexus deploy redeploy --wait with a scoped token
Frequently asked questions
What is one-click deployment?
Releasing an app with a single action. The platform builds the app, provisions its database and storage, wires secrets and connection strings, and publishes it at an HTTPS URL, so shipping a new version, redeploying, or rolling back does not need a manual runbook.
How does one-click deployment work on NEXUS AI?
You set the app up once: source, databases, and environment variables. Clicking Deploy then builds the container (generating a Dockerfile if needed), starts the services, injects DATABASE_URL and your secrets, runs a health check, and publishes the app. Later deploys reuse that configuration.
Who is one-click deployment for?
Founders and small teams without DevOps staff, developers who want push-to-deploy without a pipeline, people shipping AI-built apps, and agencies launching client apps. Larger teams use it for internal tools and preview environments.
When should I use a CI/CD pipeline instead?
When an app needs automated tests or an approval before every release. Keep the one-click controls for redeploys and rollbacks, and add a CI step that runs your tests and then runs nexus deploy redeploy with a scoped access token.
Can I deploy automatically on every git push?
Yes. Connect the repository, set a branch allowlist, and enable Auto Deploy. Each push to an allowed branch is verified by its webhook signature and deployed, with delivery logs for every webhook.
How do I roll back a bad deploy in one click?
Click Rollback on the deployment page, or run nexus deploy rollback <name> from the CLI. Rollback is included on Pro and above.
Does a one-click deploy include the database?
Yes. PostgreSQL, MySQL, MongoDB, Redis, and background workers can be part of the deployment on the NEXUS AI runtime, and cloud targets get a managed PostgreSQL or MySQL database, with the connection injected into the app.
Is one-click deployment safe for production?
Yes, with the right controls: secrets come from an encrypted vault, health checks run before an app is marked healthy, rollback is one click, and roles can limit who deploys to production. Add CI tests for apps where a bad release is costly.
Can I add a Deploy button to my GitHub README?
Yes. Add the Deploy to NEXUS AI button markdown to your README and, optionally, a nexus.json that lists the databases, worker, and environment variables the app needs. Anyone who clicks it can deploy the public repository to their own account.
Can an AI agent deploy in one step?
Yes. MCP clients such as Claude, Cursor, and Codex can call nexusai_deploy_source, nexusai_deploy_redeploy, and nexusai_deploy_rollback with the scopes you approve.