There are some known limitations to the platform. These are the major issues that are faced by our enterprise users at the moment:
a) Limited support for SSO providers - currently supports Google, GitHub and Okta. Other providers are in the roadmap and will be shipped over the coming weeks.
b) Multiple users cannot edit the same app at the same time. We are working on this so that large teams can build apps easily.
c) Multiple organisations per user is not supported. Even though it's not a deal breaker, enterprise users prefers to isolate access for different teams. This feature is in development.
d) Support for multiple pages per app - this is one of the most requested features. Right now the users will have to use the 'tabs' widget as a workaround.
ToolJet was in beta when we first launched on HN in June (https://news.ycombinator.com/item?id=27421408). . Since then, we have grown to 5,000 stars on GitHub, contributions from 100+ developers and hundreds of thousands of docker pulls. Today, we released ToolJet 1.0.
We believe our open-source and plugin-based approach helps the engineering teams to customise our low-code framework as per their requirements.
What is ToolJet?
ToolJet is an open-source low-code framework to build and deploy internal tools quickly without much effort from the engineering teams. You can connect to your data sources, such as databases (like PostgreSQL, MongoDB, MS SQL Server, etc), API endpoints (with support for OAuth2 authorization), and external services ( Stripe, Slack, Google Sheets, Airtable, etc) and use our pre-built UI widgets to build internal tools.
In v1, there are major changes in the architecture of ToolJet ( without affecting backward compatibility ). The changes in v1 are:
1. We ported the ToolJet server from Ruby to JavaScript. Codebase is now 100% JavaScript/TypeScript.
2. We altered the architecture to support extensibility. We built a plugin system so that any JavaScript developer will be able to extend ToolJet easily. For example, a simple plugin for connecting ToolJet with BigQuery can be built in less than 30 minutes.
3. Redesigned the application builder with a focus on usability. Added keyboard shortcuts such as undo, redo, deletion, clone, etc.
4. We built a commandline tool tooljet cli and published it on npmjs. The tool can bootstrap new plugins, add npm packages as dependencies for plugins, run tests for a specific plugin, etc. This tool saves time taken for building and testing plugins.
5. ToolJet was launched with 15 UI widgets. Now there are 35+ widgets including chart, map, QR scanner, list layout, file picker, etc.
6. Integrated with 20+ data sources including cloud storage like S3, GCS & Minio.
7. Added the ability to run JavaScript code snippets from within the client.
8. Added user groups feature and permissions based on user groups.
9. Redesigned the application builder completely. All the panels and tools have been redesigned with a focus on usability.
10. We also added collaboration features so that teams can communicate in real-time. The editor can easily become a collaborative workspace for building internal tools.
11. Added support for deploying ToolJet on more platforms including Azure, GCP, AWS EC2 using AMI.
We are still in our early days ( just 10 months old ) and there is a lot of features to be built and improved in the coming months and years. Feedback from the open-source community helped us get here, any feedback is appreciated and happy to answer any questions.
a) Limited support for SSO providers - currently supports Google, GitHub and Okta. Other providers are in the roadmap and will be shipped over the coming weeks.
b) Multiple users cannot edit the same app at the same time. We are working on this so that large teams can build apps easily.
c) Multiple organisations per user is not supported. Even though it's not a deal breaker, enterprise users prefers to isolate access for different teams. This feature is in development.
d) Support for multiple pages per app - this is one of the most requested features. Right now the users will have to use the 'tabs' widget as a workaround.