Alternatives

A ToolJet alternative for apps built with your AI coding tools

ToolJet is an open-source internal tool builder that generates screens and queries with AI, lets builders refine them on a visual canvas, and can be self-hosted. Diakrin lets employees build internal apps with coding agents such as Claude Code, Cursor or Codex and deploys each app as its own service and database in the company's AWS or Google Cloud account. The key difference is the output: ToolJet produces ToolJet apps on a ToolJet server, while Diakrin governs standard web apps released into your cloud through IT-approved plans.

Last reviewed

ToolJet suits teams that want an open-source internal tool builder with AI generation and a visual canvas, which they can run themselves. Diakrin suits companies whose employees already build with Claude Code, Cursor or Codex and need those apps to run in the company's own AWS or Google Cloud account, with IT approving access, cost and production releases under its approval policy.

What is ToolJet good at?

ToolJet calls itself an AI app builder and an open-source internal tool builder. Its pitch is to generate screens and queries, refine them visually and configure access before rollout.

  • AI generation from a plain-language description, producing components wired to queries that you refine on the canvas.
  • An MCP plugin so coding agents can build native ToolJet apps.
  • An Agent Builder for automating multi-step processes.
  • A self-hosted Community Edition, with deployment guides for Docker, Kubernetes, AWS, Google Cloud Run, Azure and more.
  • SAML, OIDC and LDAP SSO, audit logs, Git sync and multiple environments on paid plans, SCIM on Enterprise, and an air-gapped add-on for self-hosted Enterprise.

Where does ToolJet stop for IT-governed AI apps?

ToolJet apps are ToolJet apps: they are built in ToolJet and run on a ToolJet server, whether cloud or self-hosted. Even when a coding agent does the work, it builds inside ToolJet. That is a good model if ToolJet is your standard runtime.

If your company wants each AI-built app to be a standard web app with its own database in your cloud account, Diakrin is designed for that. The builder's agent writes the code; the Diakrin runner builds and scans it in your account; and the release is a plan with the exact image, environment, cost estimate and access implications that an eligible reviewer approves.

ToolJet vs Diakrin at a glance

ToolJetDiakrin
Who buildsBuilders in ToolJet, with AI helpEmployees with the coding tool they already use
How apps are builtAI generation, visual canvas, MCP plugin for coding agentsClaude Code, Cursor, Codex and other MCP tools, or the Diakrin CLI
Where apps runOn ToolJet Cloud or your ToolJet serverEach app's own service and database in your AWS or Google Cloud account
Self-hostingCommunity Edition free; Team and Enterprise paidSelf-hosted install in your AWS account
Identity and SSOSAML, OIDC and LDAP on paid plans; SCIM on EnterpriseSAML SSO with SCIM provisioning; OIDC on self-hosted
IT approval before productionRelease management and multiple environments on higher plansCapability approvals, budgets and a reviewed release plan
Pricing modelPer builder per month; Enterprise by quoteNot published

When to choose ToolJet

  • You want an open-source builder that you can self-host for free.
  • Your builders like a visual canvas with AI to get a first draft.
  • You need to deploy on infrastructure Diakrin does not support today, such as Azure or Kubernetes you run yourself.
  • You want AI agents for back-office automation in the same product.

When to choose Diakrin

  • Employees are already using Claude Code, Cursor or Codex, and you want to keep those tools.
  • You want each app to run in your own AWS or Google Cloud account, next to the data it may use.
  • IT needs named, scoped data grants, per-app budget ceilings checked before deployment, and, where policy requires it, an approver who is not the requester.
  • You want app data, files and secrets to stay in your account, with only metadata reported back.

Diakrin does not yet offer scheduled jobs or general internet access from apps. See what each cloud provides today.

How to move from ToolJet to Diakrin

There is no import from ToolJet. Rebuild one app first and learn from it.

  1. Choose an app with a clear owner, such as a request tracker, and list its screens, queries and users.
  2. IT connects your cloud account and creates a setup. See Set up your company cloud.
  3. The builder creates the app in Diakrin and describes it. See Create your first app.
  4. The builder connects their coding tool and pastes the guided brief. See Connect your coding tool.
  5. Request access to the data sources the app needs; IT approves them as scoped grants.
  6. Preview with a few users, send the release plan for approval, then retire the ToolJet app.

Frequently asked questions

Is ToolJet open source?

Yes. The ToolJet repository is released under the GNU Affero General Public License v3.0, and the self-hosted Community Edition is free. Paid Team and Enterprise plans add features such as SAML and OIDC SSO, audit logs and Git sync.

Can coding agents build ToolJet apps?

Yes. ToolJet describes an MCP plugin that connects coding agents to build native, governed ToolJet apps.

Where do Diakrin apps run?

In your company's cloud account. Each app gets its own service, database, file storage and secrets on AWS or Google Cloud, with Azure coming soon.

Can I self-host Diakrin like ToolJet?

Yes, on AWS. The Diakrin CLI installs the console, API and worker in your AWS account, and you can also keep the console with Diakrin and only run apps in your cloud (BYOC).

How is ToolJet priced?

ToolJet publishes per-builder prices for its cloud and self-hosted plans, with Enterprise by quote and AI credits sold separately. Check the ToolJet pricing page for current figures.

Sources

Facts about other products come from their public pages, checked on the dates shown. Products change; tell us if something is out of date.

See Diakrin with your own cloud

Let your team build internal apps with the AI tools they already use, while IT keeps control of identity, data, approvals and spend.