-
illa-builder
Low-code platform allows you to build business apps, enables you to quickly create internal tools such as dashboard, crud app, admin panel, crm, cms, etc. Supports PostgreSQL, MySQL, Supabase, GraphQL, MongoDB, MSSQL, Rest API, Hugging Face, Redis, etc. Automate workflows with schedule or webhook. Open source Retool.
-
Refine
A React Framework for building internal tools, admin panels, dashboards & B2B apps with unmatched flexibility.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
deploy-illa-manually
Deploy illa utils manually. Docker, docker compose and k8s are all avaliable in this repo.
-
ToolJet
Low-code platform for building business applications. Connect to databases, cloud storages, GraphQL, API endpoints, Airtable, Google sheets, OpenAI, etc and build apps using drag and drop application builder. Built using JavaScript/TypeScript. 🚀
-
Congrats!
Contributing to an open-source ecosystem with alternative tools is a great approach. I hope you guys will grow rapidly.
We are running an open-source project too. It’s a React-based headless framework for building CRUD apps.
As being an open source project, we would like to get feedbacks:)
Repo:https://github.com/refinedev/refine
We are not offering drag-and-drop building blocks. However, you can build complete CRUD apps without needing to lock into the tool.
Not OP but Authentication is easy, authorization is a cross-cutting concern that often requires custom code. E.g., there are people and teams, both of which can have different kinds of access to something (read/write). Sometimes teams have sub-teams. Do the sub-teams have access to the parent teams' resources and/or vice versa? Also what kind of sharing are you going to support? Do people have to have an account to view stuff shared to them or can you just send a link? There are some efforts to make custom DSLs for describing authorization policies, to avoid cross-cutting code[1].
Computed fields require different treatment at every level of the stack. This isn't inherently hard, but it is an extra feature these low-code/no-code platforms need. Where things get difficult is inn migrations. It's common for a field that is computed at the beginning to become customizable, or for the computation to change. When that happens, what should the value be for old columns? Computed fields also often pull data from multiple other tables, which may require some combination of custom queries and database optimization.
[1] https://github.com/osohq/oso
If you are not into CLI, you can try this repo out: https://github.com/illacloud/deploy-illa-manually
