SoloIgnite Quick Start
Everything you need to run the nine-agent build pipeline locally — set up your data layer, plug in an AI provider, and ship.
Getting Started
Clone the repo, install deps, and run the dev server. The dashboard will run in a safe no-op mode until you wire up Supabase and an AI provider.
git clone https://github.com/AI-GENE/soloignite.git cd soloignite cp .env.local.example .env.local npm install npm run dev
Then open http://localhost:3000.
Set up Supabase
- Create a new project at supabase.com.
- Copy the project URL and anon key into
.env.local. - Run the SQL migrations from the
supabase/folder in the SQL editor. - Enable email auth in Authentication → Providers, and add a redirect URL to
/auth/callback.
Set up an AI Provider
SoloIgnite supports OpenRouter or Alibaba (DashScope) out of the box — pick one.
OpenRouter
Single key unlocks Claude, GPT, Llama, and more. Great for local dev.
AI_PROVIDER=openrouter OPENROUTER_API_KEY=sk-or-...
Alibaba (DashScope)
Use Qwen models through DashScope — best for CN-region deploys.
AI_PROVIDER=alibaba DASHSCOPE_API_KEY=sk-...
Environment Variables
| Key | Purpose |
|---|---|
| NEXT_PUBLIC_SUPABASE_URL | Supabase project URL (client + server). |
| NEXT_PUBLIC_SUPABASE_ANON_KEY | Public anon key for Supabase. |
| SUPABASE_SERVICE_ROLE_KEY | Service-role key for background workers. |
| AI_PROVIDER | 'openrouter' or 'alibaba'. |
| OPENROUTER_API_KEY | Needed when AI_PROVIDER=openrouter. |
| DASHSCOPE_API_KEY | Needed when AI_PROVIDER=alibaba. |
| CRON_SECRET | Shared secret for /api/cron/* endpoints. |
9-Phase Pipeline
Every build flows through up to nine specialist agents. Phases that don't apply to your target platforms are automatically skipped.
- 1
Architect
Translates product briefs into a concrete build plan, scope, and system architecture.
- 2
Database
Designs schemas, migrations, and row-level security for your Supabase project.
- 3
Frontend
Generates the web surface — Next.js app routes, components, and styles.
- 4
Mini-Program
Produces WeChat / Alipay mini-program surface when targeted.
- 5
Mobile
Scaffolds the cross-platform mobile client (React Native / Expo).
- 6
QA
Writes unit, integration, and E2E tests; enforces coverage gates.
- 7
Payments
Wires Stripe / native payment flows, webhooks, and entitlements.
- 8
DevOps
Sets up CI/CD, environments, monitoring, and deploy targets.
- 9
Reviewer
Final cross-phase review, risk surface, and ship/no-ship signal.
API Reference
| Method | Path | Description |
|---|---|---|
| GET | /api/projects | List your projects. |
| POST | /api/projects | Create a new project and enqueue a build. |
| GET | /api/projects/[id] | Fetch a single project with its workflow state. |
| GET | /api/build?projectId=... | Live build data: workflow, logs, artifacts. |
| POST | /api/chat/stream | Streaming chat with the active phase agent (SSE). |
| POST | /api/agent-tasks/process | Advance the next queued agent task. |
| POST | /api/cron/timeout-check | Sweep for stalled builds (cron target). |
| POST | /api/waitlist | Submit a waitlist entry from the landing page. |
FAQ
Do I have to configure Supabase before I can click around?
No. Without env vars the app runs in a safe mock mode — no data will persist, but the UI works so you can explore.
Can I skip phases I do not need?
Yes. Phases are filtered against your selected platforms; a web-only build skips mobile and mini-program.
Where do build logs live?
In the build_logs table (or the mock client). The dashboard polls /api/build and renders them live.
How do I run the timeout sweeper?
Wire /api/cron/timeout-check into your host’s cron (Vercel Cron or similar). Set CRON_SECRET and pass it as a bearer token.