ToolJet at the Start of 2026: From Low-Code to an AI-Native Enterprise Platform

2025 was a defining year for ToolJet.

Not because of a single feature launch – but because it forced us to answer a harder question:

What should an internal tools platform look like in a world where AI exists, but enterprises still need control?

This post is a recap of how ToolJet evolved through 2025, and why we’re confident about the direction we’re taking as 2026 begins.

Across customers and prospects, the pattern was consistent:

• Legacy low-code platforms are powerful, but slow, complex, and increasingly hard to adopt.
• AI app generators are fast, but fragile – great for demos, risky for production.
• Enterprises want AI, but not at the cost of governance, security, or reliability.

Most tools force a tradeoff between speed and control.

ToolJet is built to remove that tradeoff.

In 2025, we invested heavily in the platform layer – not flashy UI, but fundamentals that matter when hundreds or thousands of users depend on internal tools.

We launched ToolJet’s AI app builder in early 2025 as an experiment — and learned quickly where AI helps and where it doesn’t.

The conclusion was clear:

AI works best when it accelerates development, not when it replaces structure.

By the end of 2025, ToolJet AI can:

• Generate multi-page applications with real navigation
• Create valid data bindings between UI and backend queries
• Understand existing APIs from their specifications
• Apply bulk changes through natural language
• Help debug and auto-fix component errors inline

This is not prompt-to-app magic.
Every generated app is meant to be inspected, edited, extended, and governed.

We removed stateless interactions.

ToolJet AI now retains conversational context, allowing teams to iterate naturally without repeating themselves. Builders can also reference specific components directly, ensuring precise changes instead of guesswork.

This makes AI usable in real projects, not just first drafts.

We have moved authentication and provisioning to the instance level, rather than workspace-by-workspace.

This allows enterprises to:

• Configure SSO once for the entire ToolJet instance
• Synchronise users and groups automatically using SCIM
• Maintain consistent access controls across teams
• Reduce operational overhead in self-hosted environments

This shift was driven by how real enterprises operate – not by ease of implementation.

Internal tools are software. They need the same discipline as production systems.

In 2025, we introduced and expanded:

• Promote and release permissions across environments
• Role-based access for workflows
• Fine-grained RBAC at query, component, and page levels
• Clear separation between Development, Staging, and Production access

This lets teams ship faster without risking production data or workflows.

As ToolJet adoption grows inside companies, manual processes stop scaling.

To address this, we added:

• CI/CD integrations for automated deployments
• APIs for importing and exporting applications across instances
• Credential rotation via environment variables
• Cleaner Git integration without custom firewall or port workarounds

The goal is simple: ToolJet should fit naturally into existing DevOps and security practices.

Internal tools often fail quietly – until they impact operations.

In 2025, we added production observability through OpenTelemetry, enabling teams to:

• Track query execution times and failures
• Monitor app usage patterns
• Integrate with Grafana, Datadog, or New Relic
• Detect issues early instead of reacting late

This turns internal apps into observable systems, not blind spots.

As ToolJet matured, teams started building larger, more complex systems. 2025 was about supporting that scale.

We introduced Modules so teams can:

• Build reusable UI and logic blocks once
• Share functionality across multiple apps
• Maintain consistency across large internal platforms

This is essential for multi-team environments.

We significantly upgraded debugging capabilities:

• Centralised debugger with event-level errors
• Custom error handling in JavaScript and Python
• Improved Inspector UI for state visibility

These changes reduce time-to-fix and make ToolJet viable for mission-critical internal systems.

Internal tools still need to be usable.

In 2025, we focused on removing friction from UI building:

• Auto-generated forms from data sources
• Rich input components (currency, email, phone, validation)
• Responsive layouts with dynamic sizing
• Custom themes for consistent branding
• Precise layout tools with snapping and alignment

The goal is not pixel perfection – it’s clarity and reliability for end users.

We introduced theming in 2025. It is now easier to set brand and other guidelines for workspaces. This helps builders create UIs without having to change every style property for every new component.

Workflows moved from “nice-to-have” to core capability.

ToolJet workflows now support:

• Role-based permissions
• Scheduled and event-driven execution
• Execution control and cancellation
• Import/export for backup and migration
• External NPM libraries
• 80+ integrations across SaaS, cloud, logistics, finance, and AI

This allows teams to automate real operational processes – safely.

We changed our pricing model in 2025 to charge only based on the number of builders, not end users.

In large organizations, internal tools are used by hundreds or thousands of employees. Pricing that scales with end users creates friction where it shouldn’t exist – discouraging adoption, limiting rollout, and forcing teams to make artificial tradeoffs about who can access internal systems.

Builder-based pricing aligns with how enterprises actually work:

• Builders are the constrained resource, not end users
• Internal tools should be shared freely once built
• Adoption should not require renegotiation or license counting

This model removes the “tax on usage” that slows down internal tool adoption and encourages teams to deploy applications broadly across the organization without worrying about incremental cost.

It also simplifies procurement and budgeting. Enterprises can forecast costs based on the size of the development team, not unpredictable usage patterns across departments.

As ToolJet becomes more AI-assisted, this model becomes even more important. AI helps builders move faster, but it shouldn’t penalize organizations as usage grows. Pricing by builders keeps incentives aligned: we succeed when teams build more and ship faster, not when they restrict access.

Builder-based pricing is common in developer tooling. It’s also the model that best reflects ToolJet’s role as a platform for building internal software, not a per-seat business application.

This change reinforces what ToolJet is built for: enterprise-wide internal tools, deployed broadly,

ToolJet today is:

• An enterprise-ready internal tools platform
• AI-native, but not AI-dependent
• Designed for self-hosted, security-sensitive environments
• Built to evolve as AI improves – without breaking existing systems

We’re early in this transition. AI will keep getting better. Visual builders will matter less over time. Governance and reliability will always matter.

ToolJet is positioned for that reality.

As 2026 begins, our focus is clear:

• Go deeper on AI-assisted development
• Keep raising the bar on enterprise readiness

Internal tools are being rebuilt. This time, teams expect speed and control. ToolJet sits in between; AI-native by design, but grounded in the realities of enterprise software. Our focus going forward is simple: keep making it easier to build reliable internal applications faster, without forcing teams to compromise on how they operate. That is the direction we committed to in 2025, and it is the foundation we are building on as we move through 2026.