Retool's pricing calculator made you close the tab. Appsmith and ToolJet are on your short list, but you also want real-time co-editing and workflows that fire on a webhook without duct-taping Zapier in front of prod.
ILLA Builder (illacloud/illa-builder) markets itself as open-source Retool. ~12.3k GitHub stars, Apache 2.0, drag-and-drop internal apps wired to Postgres, MySQL, MongoDB, Redis, GraphQL, REST, Supabase, MSSQL, Hugging Face, and more. Dashboards, CRUD screens, admin panels, lightweight CRMs — the stuff engineering keeps deprioritizing.
What it actually does
ILLA is a low-code builder for internal tools. Connect a data source, drop components on a canvas (tables, forms, charts, inputs from the ILLA Design system), bind fields to queries, publish an app your team opens in the browser.
Real-time collaboration. Multiple editors on the same app at once, Figma-ish multiplayer energy applied to "fix the support lookup screen before Monday."
Automations. Schedule jobs or trigger flows from webhooks — useful when an internal tool should nudge Slack, run a follow-up query, or sync a row without you writing a cron script by hand.
Broad connectors. The README still undersells the list; the project page and docs cover the usual databases plus API connectors. If your stack is Postgres plus a few REST services, you are in the sweet spot. AI/Hugging Face hooks matter if you are experimenting with model-backed internal tools (keep API keys server-side).
Self-host path. Official route is the ILLA CLI plus Docker or docker-compose (Kubernetes if you are that team). Cloud hosting exists at illacloud.com; self-hosting keeps credentials and query traffic on your metal.
ILLA vs Appsmith vs ToolJet
We have posts on Appsmith and ToolJet. All three solve "internal tools without a six-week sprint."
- ILLA Builder — strong real-time co-editing, automation/webhook story, Apache 2.0, polished component library (ILLA Design). Good when ops and devs pair-build live.
- Appsmith — mature ecosystem, Git-friendly workflows, Mongo-backed platform DB. Good when you already standardized on it.
- ToolJet — built-in database, Python in apps, huge connector catalog (AGPL CE). Good when you want an all-in-one with a different UI feel.
Run one platform, not three. Spin up ILLA on a staging VPS, rebuild one painful spreadsheet workflow, and see if the editor clicks.
Why self-host?
Internal tools touch production data. Customer records, invoices, support notes — low-code apps run SQL and API calls with stored credentials. Self-hosted on a Canadian VPS beats multi-tenant SaaS in another jurisdiction when auditors ask where admin panels live.
Per-seat math. Commercial low-code bills per builder and sometimes per end user. Self-hosting trades license fees for RAM, backups, and someone who owns Docker updates.
Webhook and schedule automations stay inside your network. Flows that react to internal events do not need a third party listening on the same webhooks.
What running it takes
Follow the self-hosted deployment guide — ILLA CLI is the fast path. Docker Compose is the usual shape: platform services plus databases/redis depending on the template you choose.
Plan 4–8 GB RAM for a comfortable small-team install (similar class to other low-code stacks). Pin image tags, put HTTPS in front, change the default root login after first boot (docs ship a known password for initial access — rotate it immediately).
Use read-only DB users where you can. The whole point is querying prod; least privilege still beats handing every app editor write access to billing tables.
Who it's for (and who should skip it)
Good fit: agencies building client ops consoles, startups before they hire a frontend team for admin UI, support leads who need a searchable order tool this week, teams that want Retool-like UX without Retool invoices.
Maybe skip it: you need pixel-perfect customer-facing product UI, you already live in Appsmith or ToolJet happily, or nobody will maintain Docker and backups for the platform database.
Hosting it in Canada
ILLA fits our Docker hosting lane: one VM, compose file, nightly backups on volumes and metadata DB.
Tell us how many builders and apps you expect — we will size RAM and disk before you import a hundred-row spreadsheet into a CRUD screen.
