NEXUS AI documentation
NEXUS AI docs for deploying full-stack apps: CLI, databases, workers, volumes, buckets, backups, restores, secrets, and cloud providers.
Full-stack deployment guides
Learn how to deploy an app from a prompt, Git repository, local source folder, or image. The docs cover app services, database services, background workers, storage, backup, restore, logs, custom domains, scaling, rollback, and auto-destroy controls.
CLI and API references
Use the NEXUS AI CLI for terminal-first workflows or call the REST API for automation. MCP tools expose deployment, database, storage, backup, auto-destroy, and project operations to AI clients with scoped permissions.
Operational troubleshooting
The docs include practical fixes for build failures, service networking, database connection environment variables, worker sidecars, bucket credentials, volume mounts, and restore safety.
App plus database plus worker
A typical NEXUS AI deployment can run a web app, a PostgreSQL database, a Redis queue, and a background worker as one connected service group. The app and worker share the same deployment network, so application code can use internal hostnames such as postgresql and redis instead of hard-coded host ports or external database addresses.
Storage and recovery included
Production apps usually need more than compute. NEXUS AI supports persistent filesystem volumes for apps that write to paths such as /data, S3-compatible buckets for uploads and generated files, database backups, in-place restore, and restore into another compatible service in the same organization.
One workflow across interfaces
The same stack can be managed from the dashboard, CLI, REST API, or MCP tools. Developers can deploy from GitHub, add database services, attach storage, run workers, scale replicas, inspect logs, create backups, and recover data without switching between cloud consoles and hand-built scripts.
Frequently asked questions
What does NEXUS AI deploy?
NEXUS AI deploys full-stack applications from prompts, Git repositories, local source folders, and container images. Deployments can include app containers, PostgreSQL, Redis, MySQL, MongoDB, worker sidecars, persistent volumes, S3-compatible buckets, custom domains, logs, health checks, database backups, restore workflows, scaling, and rollback.
Do I need to write Docker or Kubernetes configuration?
No. NEXUS AI detects common frameworks, builds a production container, provisions runtime resources, configures service networking, injects database and storage environment variables, and exposes a CLI, dashboard, REST API, and MCP tools for lifecycle operations.
Can NEXUS AI run databases and background workers?
Yes. Docker deployments can include PostgreSQL, MySQL, MongoDB, Redis, worker sidecars, persistent volumes, S3-compatible buckets, and database backup and restore workflows. Workers attach to the same service network as the app, so queue processors can reach Redis, Postgres, and other attached services by internal hostname.
Where should I start?
Start with the full-stack app deployment guide, then read the database services, worker sidecars, storage volumes and buckets, and backup and restore sections.
Can I change auto-destroy after deployment?
Yes. Deployment details include an Auto Destroy control, the CLI supports nexus deploy auto-destroy, REST exposes PATCH /api/deployments/:id/auto-destroy, and MCP exposes nexusai_deploy_auto_destroy. Updating the schedule does not restart the running app.
About NEXUS AI
NEXUS AI is an AI-native deployment platform for full-stack application teams. Learn more on the About page, read the documentation, or contact the team through nexusai.run/contact.
Start for free · Read the documentation · About NEXUS AI · Contact