Zelaxy

The open-source visual platform for building, running & shipping AI agents and workflows.
_{Drag blocks onto a canvas → wire agents, tools & logic → run with live streaming. No code required — fully extensible when you need it.}

Website · Docs · Quickstart · Why Zelaxy · Issues · Contributing

⭐ If Zelaxy is useful to you, star the repo — it genuinely helps the project reach more builders.

What is Zelaxy?

Zelaxy is a visual operating system for AI work. You compose workflows on a canvas out of
blocks — AI agents, integrations, logic, loops, sub-workflows — connect them, and a real
execution engine runs the graph with token-by-token LLM streaming.

It looks like a flow builder. Under the hood it's a topological execution engine with parallel
branches, loops, conditional routing, sub-workflows, built-in vector search (RAG), and
multi-provider AI orchestration — the kind of thing you'd otherwise stitch together from a dozen
scripts and services.

Build workflows, not glue code. Drag three blocks onto the canvas, connect them, hit run.

Table of Contents

• Why Zelaxy
• Features
• How it works
• Blocks & integrations
• Quickstart
• Configuration
• Development
• Deployment
• Tech stack
• Project structure
• Contributing
• Sponsors
• License

✨ Why Zelaxy

Most automation tools make you choose: great integrations or real AI or open-source & self-host.
Zelaxy is built to give you all three on one canvas.

Zelaxy is right for you if you want to:

• ⚡ Automate complex AI processes without writing a custom backend
• 🔀 Chain multiple LLM providers (OpenAI, Claude, Gemini, Groq, DeepSeek, Grok, Mistral, Ollama…) in one pipeline
• 🔍 Visually debug — see exactly which block produced which output, and how long it took
• 📚 Build RAG pipelines with vector search built in — upload, embed, and query from any block
• 🪝 Trigger from Slack, GitHub, Gmail, Stripe, Telegram, webhooks, or cron
• 🏠 Self-host an open-source platform you can extend with your own blocks and tools

🚀 Features

🛠 How it works

🧩 Blocks & integrations

Full, searchable reference at docs.zelaxy.in.

⚡ Quickstart

Open source. Self-hosted. No account required.

git clone https://github.com/manu14357/Zelaxy.git
cd Zelaxy
bun install
cp apps/zelaxy/.env.example apps/zelaxy/.env.local
# Edit .env.local — set DATABASE_URL, auth secrets, and at least one LLM API key
cd apps/zelaxy && bunx drizzle-kit migrate && cd ../..
bun run dev:full

App runs at http://localhost:3000, docs at http://localhost:3001.

Prefer hosted? Try zelaxy.in · Docs: docs.zelaxy.in

Requirements: Bun ≥ 1.2 · PostgreSQL 17 with pgvector · at least one LLM API key.

🔧 Configuration

LLM providers (add any): OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, GROQ_API_KEY, DEEPSEEK_API_KEY, XAI_API_KEY, CEREBRAS_API_KEY, NVIDIA_API_KEY, MISTRAL_API_KEY, OPENROUTER_API_KEY

Local models: OLLAMA_URL (default http://localhost:11434), LM_STUDIO_URL (default http://localhost:1234)

💻 Development

bun run dev:full          # Full dev (app + websocket + docs)
bun run dev               # App only
bun run dev:sockets       # WebSocket server only
bun run build             # Build all
bun run test              # Run tests (~900 unit tests)
bun run lint              # Lint and auto-fix (Biome)
bun run type-check        # Type check (0 errors)

cd apps/zelaxy && bunx drizzle-kit studio    # Database GUI
cd apps/zelaxy && bunx drizzle-kit migrate   # Run migrations
bun run start:worker                          # Background job worker (requires REDIS_URL)

🌐 Deployment

The Next.js app deploys to Vercel. Two long-running services run on Railway:

Set NEXT_PUBLIC_SOCKET_URL and SOCKET_SERVER_URL on Vercel to your Railway socket URL. Background
jobs use BullMQ backed by Redis (Upstash recommended) — set REDIS_URL on both Vercel and the
Railway worker.

🧰 Tech stack

📁 Project structure

Zelaxy/
├── apps/
│   ├── zelaxy/           # Main Next.js 15 application (the product)
│   │   ├── app/          # App Router — pages (/arena/**), API routes (/api/**)
│   │   ├── blocks/       # 264 block definitions + registry
│   │   ├── tools/        # 240+ integrations (880+ actions) + registry
│   │   ├── executor/     # Workflow execution engine (dag, resolver, handlers)
│   │   ├── providers/    # 21 LLM providers
│   │   ├── triggers/     # Webhook / schedule / event triggers
│   │   ├── serializer/   # Editor graph → executable workflow
│   │   ├── db/           # Drizzle ORM schema + queries
│   │   ├── stores/       # Zustand state
│   │   ├── socket-server/# Socket.IO realtime collaboration server
│   │   └── worker/       # Background jobs
│   ├── docs/             # Documentation site (Fumadocs)
│   └── core/             # Shared core
├── packages/             # CLI · TypeScript SDK · Python SDK
├── LICENSE               # MIT
└── package.json          # Monorepo root

Working in the codebase? Start with CLAUDE.md and CONTRIBUTING.md.

🤝 Contributing

Contributions are welcome — blocks, integrations, bug fixes, docs, all of it.

1. Fork the repository
2. Create a feature branch (git checkout -b feat/your-feature)
3. Make your changes
4. Run bun run test, bun run lint, and bun run type-check
5. Open a pull request

New here? Look for good first issue and read CONTRIBUTING.md.

💖 Sponsors

Zelaxy is free and open source. Sponsors keep it that way.

Your logo here — become a sponsor

📄 License

MIT © 2025 Zelaxy — see LICENSE.

⭐ Star Zelaxy to follow along — new blocks, integrations, and features ship constantly.

_{Built for people who want to automate with AI — not write glue code.}