// the take
ILLA Builder is an open-source Retool alternative for building internal tools via a drag-and-drop UI, with connectors for 20+ databases and APIs. It targets developers who want to spin up CRUD apps, dashboards, and admin panels without writing frontend code. The cloud version is available, and self-hosting via Docker/k8s is supported.
- Broad connector coverage out of the box: PostgreSQL, MySQL, MongoDB, Redis, Supabase, REST, GraphQL, Hugging Face, MSSQL — covers most real-world internal tool data sources without needing custom work.
- Real-time collaboration is built in at the WebSocket/protobuf layer (see illa_binary_ws.ts and ILLA_PROTO.proto), not bolted on as an afterthought, which is a meaningful differentiator over simpler open-source alternatives.
- The component library is genuinely wide — 50+ widgets including event calendar, JSON schema form, signature, QR code, code scanner — most competitors ship a fraction of this at the same maturity level.
- Self-hosting story is solid: single Docker image, docker-compose, and k8s configs all present, and the default root credentials are clearly documented so first-run setup isn't a mystery.
- The backend (illa-builder-backend) is a separate repo not included here — this is frontend-only. Self-hosting requires finding and coordinating separate backend, supervisor, and gateway repos, which is a real operational burden the README glosses over.
- No visible test coverage in the source tree. A codebase of this scale with zero apparent unit or integration tests is a red flag for anyone planning to fork or extend it.
- Heavy reliance on ILLA Cloud infrastructure for features like AI agents and ILLA Drive — these reference cloud endpoints in the .env.cloud config and portions won't work at all in a self-hosted setup, which isn't clearly disclosed.
- Commit activity and issue response have slowed noticeably; several open issues cite broken self-hosted deployments with no maintainer responses. For a tool you'd run in production for internal apps, the bus factor and maintenance trajectory are real concerns.
We read the README, the directory tree and a key source file in June 2026. Nobody pays to be listed. How we judge →