README
¶
Atlas
The Autonomous Deployment Pipeline
Atlas analyzes your project, runs the build, uses an LLM to auto-fix build errors, and deploys to a cloud provider—all in a single command.
✨ Features
- 🧠 Auto-Healing Builds: When a build fails, Atlas diagnoses the error, suggests a patch using an LLM (Anthropic, Mistral, Groq, etc.), and retries autonomously.
- 🚀 One-Command Deploy: From local directory to live URL without opening the browser.
- 🔌 Multi-Provider Support: First-class deployments for Vercel, Render, and Netlify.
- 🔎 Framework Detection: Automatically detects React, Next.js, Express, and Vite projects and runs the correct build tools.
- 🛡️ Secure Credential Management: Employs the OS keychain (via
go-keyring) to store your sensitive LLM and Provider API keys safely. - 🤖 Deterministic Pipeline: Not a wild looping agent. Atlas follows a strictly bounded, predictable state machine for safe deployments.
⚡ Getting Started
1. Installation
You can install Atlas using our seamless installation scripts:
macOS & Linux:
curl -sSL https://raw.githubusercontent.com/Yashh56/atlas/master/install.sh | sh
Windows (PowerShell):
iwr -useb https://raw.githubusercontent.com/Yashh56/atlas/master/install.ps1 | iex
Or via Go directly:
go install github.com/Yashh56/atlas/cmd/atlas@latest
2. Set your LLM API key
Atlas requires an LLM to fix broken builds. We support Anthropic, OpenAI, Mistral, Gemini, Groq, and xAI.
# Example: Store your Anthropic key securely via the CLI wizard
atlas models set anthropic
You can also use environment variables like export ANTHROPIC_API_KEY=...
3. Deploy Your Project
Navigate to any supported project directory and let Atlas do the magic:
cd ./my-nextjs-app
atlas .
Atlas will interactively ask you to choose a provider (e.g., Vercel), authenticate if you aren't already, run the build, fix any errors, and give you a live URL.
(For CI/CD usage, you can run non-interactively: atlas . --action deploy --provider vercel)
📚 Commands
| Command | Description |
|---|---|
atlas <path> |
Interactive deployment wizard |
atlas <path> --action deploy --provider <name> |
Full non-interactive pipeline |
atlas providers |
Check deploy provider auth status |
atlas models |
Check LLM API key status |
atlas testllm <path> |
Verify LLM key with a live ping |
For a full breakdown of the architecture, see our Documentation.
🌐 Supported Integrations
Frameworks
| Framework | Status |
|---|---|
| NextJS | ✅ |
| React | ✅ |
| Vite | ✅ |
| Express | ✅ |
| Django | ⏳ Planned |
Deployment Providers
| Provider | Status |
|---|---|
| Vercel | ✅ |
| Render | ✅ |
| Netlify | ✅ |
| Fly.io | ⏳ Planned |
| Railway | ⏳ Planned |
❓ FAQ
Q: Does Atlas rewrite my code unexpectedly?
A: No. Atlas uses exact-match patching. It does not rewrite entire files and will explicitly ask for approval before continuing the deployment after a patch.
Q: Where are my API keys stored?
A: Atlas stores credentials securely in your operating system's native keychain (Keychain on macOS, Credential Manager on Windows, Secret Service on Linux) and never writes them to plaintext files.
Q: Can I use local models?
A: Yes! You can configure Atlas to use local LLMs (like Ollama) for completely free, private auto-healing.
🗺️ Future Plans
- Docker Support: Automatically generate
Dockerfiles for unknown frameworks. - Rollback Mechanics: Automatically revert to a previous healthy deployment if the post-deployment health check fails.
- More Frameworks: Deep integrations for Django, Spring Boot, and Laravel.
- Multi-Environment Deployments: Native support for staging and production branching.
Directories
¶
| Path | Synopsis |
|---|---|
|
cmd
|
|
|
atlas
command
|
|
|
atlas/cmd
Package cmd wires together all Atlas CLI commands.
|
Package cmd wires together all Atlas CLI commands. |
|
internal
|
|
|
build
Package build provides build-command resolution and execution for Atlas.
|
Package build provides build-command resolution and execution for Atlas. |
|
config
Package config handles loading Atlas configuration from disk.
|
Package config handles loading Atlas configuration from disk. |
|
credentials
Package credentials provides a global, per-user credential store for Atlas.
|
Package credentials provides a global, per-user credential store for Atlas. |
|
llm
Package llm provides multi-provider LLM clients for Atlas, built on GoAI v0.8.6.
|
Package llm provides multi-provider LLM clients for Atlas, built on GoAI v0.8.6. |
|
orchestrator
Package orchestrator owns the planner, project, and deployment context files that live alongside session.json in <workspace>/.atlas/sessions/<id>/.
|
Package orchestrator owns the planner, project, and deployment context files that live alongside session.json in <workspace>/.atlas/sessions/<id>/. |
|
registry
Package registry provides a simple thread-safe tool registry for Atlas.
|
Package registry provides a simple thread-safe tool registry for Atlas. |
|
session
Package session manages Atlas agent sessions.
|
Package session manages Atlas agent sessions. |
|
state
Package state defines the status constants and shared persistence helpers used across Atlas components.
|
Package state defines the status constants and shared persistence helpers used across Atlas components. |
|
tools
Package tools defines the Tool interface and shared result types for Atlas.
|
Package tools defines the Tool interface and shared result types for Atlas. |
|
workspace
Package workspace resolves and describes a project working directory.
|
Package workspace resolves and describes a project working directory. |