Build anything. Own everything.
Open source, unlimited scope — own the agent platform that does everything AI can.
22+ AI providers, 8 built-in skills and 114 design systems,, and 13 starter templates — all running on infrastructure you own.
features
An AI agent platform that belongs to you.
Self-hosted, MIT-licensed, and built around the LLMs you already pay for — own the platform, the data, and the deployment.
Integrations
Works with any LLM you choose.
22+ providers, one chat surface. Bring the API keys you already have — OpenAI, Anthropic, Google, Groq, DeepSeek, Ollama, and more — and switch models mid-conversation without losing context.
22+ cloud + local providers, plus custom endpoints
Swap LLMs mid-chat, conversation history preserved
Your API keys never touch our servers
Metrics
One platform beats five separate ones.
Stop renting ChatGPT for chat, Cursor for editing, Bolt for sandboxed builds, and a separate vector DB for memory — and the provider's own platform for using your API key. Amplify ships all of it under your own domain, with every LLM you already have access to, free of per-seat SaaS fees.
LLM Providers
One platform covers every model you already pay for — no more juggling ChatGPT, Claude.ai, Gemini, and Groq Studio tabs.
SaaS Tools Replaced
Chat, IDE, sandbox, vector DB, and the provider's own console — all replaced by a single self-hosted install.
Composite Score
Open-source capability score across 15 surveyed AI platforms — 33 points ahead of the next-best tool.
Vendor Lock-in
MIT-licensed, self-hosted, your API keys never touch our servers. Fork it, audit it, leave any time.
How it works
Host, configure, then start building.
Self-host in minutes, point it at the LLMs you already pay for, and ship your first prompt the same day — no engineering review required.
Host
Deploy Amplify on Docker, Cloudflare Pages, Electron, or bare metal. One command pulls the image, exposes port 5173, and you're live on your own domain — no SaaS account, no per-seat fee.
Configure
Pick any of the 22+ providers from the model selector and paste the API key you already have. Keys persist in your browser's localStorage and go straight to the provider — never through our servers.
Start building
Open a chat, pick a starter template, and watch your LLM build and run real code in a browser-native WebContainer sandbox. Switch models mid-conversation whenever the task changes.
FAQ.
Got questions? We've got answers. Here's everything you need to know about Amplify, our 22+ provider integrations, and how self-hosting actually works.
Amplify is a free, open-source, self-hostable AI coding assistant that runs entirely in your browser. It combines a full IDE-like environment (code editor, terminal, file explorer, live preview) with an AI assistant that can read files, write code, search the web, and execute commands — all powered by your own LLM API keys.
Amplify supports 22+ providers out of the box, including OpenAI, Anthropic, Google Gemini, Hugging Face, Mistral, DeepSeek, xAI, Groq, Cohere, Fireworks AI, Perplexity, OpenRouter, Together AI, Cerebras, Moonshot, Hyperbolic, Z.ai, GitHub Models, AWS Bedrock, Ollama, LM Studio, and any custom OpenAI-compatible endpoint. You can switch between them mid-conversation without losing context.
No. Amplify is MIT-licensed and self-hosted. Your API keys go directly from your browser to the provider's API — they never pass through Amplify's servers because there are no Amplify servers. You only pay the provider you already use, at their normal rates. There is no per-seat SaaS fee and no markup.
Each provider's own platform is locked to that one vendor's models, has no real code execution sandbox, has no MCP or Skills extensibility, and stores your conversation history on their cloud. Amplify unifies 22+ providers behind one chat surface, runs real Node.js in a browser-native WebContainer, supports 8 built-in skills and 114 design systems, and any MCP server, and keeps every chat, file, and snapshot in IndexedDB on your own machine.
Yes. Conversations are stored independently of providers. When you switch models, only the API endpoint changes — the new provider picks up the existing conversation as context. You can use Claude for hard reasoning, switch to Groq for fast boilerplate, and finish with a local Ollama model for sensitive code, all in the same chat.
Six deployment methods are documented: Docker (production, development, or prebuilt image from GitHub Container Registry), Cloudflare Pages (edge-hosted with COEP/COOP headers), Coolify, an Electron desktop app (macOS, Windows, Linux), native bare-metal on Node.js 18.18+, or behind a reverse proxy (nginx or Caddy) for SSL. Memory requirement is 4GB minimum, 8GB recommended.
Everything stays on your machine. Chat history, file snapshots, project commits, and screenshots live in an IndexedDB database called amplifyHistory. The BM25 vector store (used for cross-session memory) lives in a separate IndexedDB database called amplify_vector_stores. Nothing is uploaded to a vendor cloud unless you explicitly connect a cloud integration like Supabase, Vercel, or Netlify.
Yes, Amplify is MIT-licensed and fully open source — fork it, audit it, modify it, commercialize it. One caveat: the WebContainer sandbox runtime (used for in-browser code execution) is proprietary to StackBlitz and requires a commercial license for production use. If you migrate the sandbox layer to your own Docker container or any other container runtime, the entire stack is yours to commercialize under the MIT license.
Tools like Bolt, v0, and Lovable run everything in one long chat, so the context window grows linearly and the AI gets slower and noisier over time. Amplify uses sub-chat workers (each task gets its own isolated context), reusable memory (key info is extracted to vector stores after each chat), and summarization at the 70% threshold. New chats start fresh with only ~1500 tokens of targeted context injected — not the full baggage of every previous message.
No. Amplify does not rate-limit you, throttle your requests, or set ceilings below what your provider allows. It reads the per-provider RPM/TPM/RPD limits you've configured in Settings and adapts via a Pre-Flight Check, RPM Throttling, and Auto-Shrink-to-TPM to avoid triggering 429 errors from your provider.
Yes. Ollama (default http://127.0.0.1:11434) and LM Studio (default http://127.0.0.1:1234) are first-class providers with unlimited rate limits. Use 127.0.0.1 instead of localhost to avoid IPv6 resolution issues. If you run Amplify in Docker, set RUNNING_IN_DOCKER=true so localhost is rewritten to host.docker.internal automatically.