ToolJet

Operator's take

The internal tools problem is real and predictable: your dev team is building product, not the ops dashboard someone needs right now. The usual answer is "just use a spreadsheet" or "we'll get to it," and both answers rot over time. ToolJet is the tool that plugs that gap — you drag components onto a canvas, connect them to whatever your data actually lives in (Postgres, MongoDB, a REST API, Google Sheets), add some conditional logic, and end up with something that works without a sprint ticket. For a non-developer ops lead or a founder who needs internal tooling without burning engineering cycles, that's a genuinely useful proposition.

The AI layer has expanded significantly: you can describe what you want and get a scaffolded app, but ToolJet also now ships a dedicated Agent Builder and visual workflow automation — you're not just generating a UI, you're potentially wiring up multi-step automations and AI agents without leaving the platform. Think "generate me a table view of all open support tickets with a status dropdown" for the app-builder side; "run this API call on a schedule and notify Slack when something breaks" for the workflow side. That framing keeps expectations accurate. What ToolJet actually does well is the connection layer — 80+ native integrations means you're probably not writing a custom connector to hook into your stack, and that alone saves the kind of time that justifies the tool. The self-hosting option adds a meaningful argument for teams in regulated environments where "our data doesn't leave our infra" is a real constraint.

Pricing is transparent and starts free: the Free tier allows 2 builders and up to 2 apps; Pro runs $79/builder/month (up to 5 apps); Team is $199/builder/month (unlimited apps, SSO, custom domain, Git sync); Enterprise starts at $3,000/month for unlimited end users. Annual plans save 20%.

Who it's wrong for: if you need customer-facing apps or serious mobile support, ToolJet isn't designed for that surface. And if your ops team has no tolerance for occasional JavaScript when the visual builder reaches its ceiling, the more opinionated Glide or Softr alternatives will feel less rocky. ToolJet rewards operators who are comfortable tinkering — not quite no-code in the pure sense, but genuinely accessible for anyone who's ever written a formula.

What it's good at

• AI-assisted app generation plus Agent Builder — describe an interface in plain language and get a working scaffold; a separate Agent Builder handles multi-step AI agent workflows.
• 80+ drag-and-drop UI components — tables, charts, forms, kanban boards, maps — assembled visually, no front-end design work required.
• 80+ native data source connectors — Postgres, MongoDB, Stripe, REST APIs, Google Sheets, and more connect without custom code or middleware.
• Escape hatch to JavaScript — when the visual builder can't express your logic, the built-in JS editor handles it without leaving the platform.
• Self-hosting with version control — deploy on your own infrastructure for data residency and compliance requirements; collaborative development via built-in version control.
• Generous open-source base — the core platform is open-source; most teams can get real work done before hitting a paid tier.

What it's not

• Not a customer-facing app builder — the canvas and component set are optimized for internal users, not polished public-facing products; don't reach for it if you need a customer portal.
• Not truly no-code at scale — complex logic requires JavaScript; operators who want zero code involvement will eventually hit that ceiling.
• Not built for mobile-native apps — the canvas is web-first and the marketing pages don't position native mobile app development as a capability; if field teams need a true native mobile app experience, verify the current mobile story before committing.
• Not the right choice for simple database views — if your need is basically "make this Airtable base prettier," Softr or Glide are faster paths with less overhead.