BYOAIK (Bring Your Own AI Key) is a directory of AI tools that run on your own API key.
LlamaCoder
Open v0 alternative that builds a React app from a prompt, on a key you provide.
- Category:
- App Builders
- Maintenance:
- Actively developed (last commit 14 days ago)
- Pricing:
- Open Source
- Open source:
- Yes (MIT)
- Self-hostable:
- Yes
- Local-first:
- No
- Platforms:
- Web, Self-hosted, Local-only, Docker
- AI providers (bring your own key):
- Together AI, Custom / OpenAI-compatible
- API key storage:
- User controls deployment
- Key risk level:
- LOW
- Trust score:
- 85/100
LlamaCoder turns a prompt into a working React application with live preview, an open alternative to v0 and Claude Artifacts built on open models. The key is the operator's: TOGETHER_API_KEY in the environment, with the app running wherever you run it, so neither the prompts nor the generated code need pass through a product you do not control. MIT.
How this tool was scored
Key handling 80/100 (where your key rests and who sees it, comparable across any licence) and verifiability 90/100 (how much of that BYOAIK could confirm, lower for closed source). Neither contains a popularity signal.
- Key Safety 21/25: The key lives in a deployment you run yourself.
- Request Routing 17/20: Requests go straight from you to the AI provider.
- Transparency 20/20: Source is public under MIT, so anyone can check how the key is handled. Key handling was located in the published source.
- Privacy 10/15: Can be self-hosted, so the data path stays inside infrastructure you control.
- Maintenance 10/10: Actively developed, with commits within the last three months.
- Verification Confidence 7/10: Key handling was found in the published source by BYOAIK's scanner.
What was checked
Verification tier SOURCE_VERIFIED, derived from the evidence below and not set by hand.
- [REPORTED · RESEARCH] This listing was compiled by an AI-assisted research pass over the tool's public website, README and documentation. No person independently confirmed it.
- [STRONG · SOURCE_SCAN] The user supplies their own Together AI key: the project references its API key variable. source
- [CONFIRMED · SOURCE_SCAN] Most recent commit 2026-09-15, about 0 month(s) ago. source
How your API key is handled
You self-host the app, so your API key lives in your own deployment. Requests are sent directly to the AI provider. Because it can be self-hosted, your key never has to touch a third-party backend.
Setup
Deploy it (Docker/compose), add your provider API key in the admin or environment config, then select models.