An open-source low-code platform combines a visual app builder with source code distributed under an open-source license. A closed-source platform grants access through its proprietary terms. The practical choice depends on the edition, deployment model, extension options, governance and operating cost, not just whether a repository is public.
For internal apps, evaluate ToolJet or Appsmith; for apps and operational automation, include Budibase and Joget; for database-driven no-code apps, consider Saltcorn; for web and mobile development, assess Convertigo. NocoDB is a related database-workspace option, but its current Sustainable Use License means it should be evaluated separately from open-source licenses.
Scope: This guide compares the licensing and evaluation criteria, then explains seven platform options. Repository and product references were reviewed on October 20, 2026. It is an editorial guide, not a performance benchmark. Existing screenshots are historical illustrations; verify features against the edition you intend to deploy.
What are open-source low-code platforms?
Low-code platforms supply visual components for building interfaces, connecting data and implementing application behavior. In an open-source edition, the license also grants rights to use, modify and redistribute the covered source code. The Open Source Initiative definition requires more than the ability to view code.
Open source, open core and source available
- Open source: The covered code is distributed under a license meeting the open-source definition. Read the actual license and notices for the version you deploy.
- Open core: A product combines an open-source foundation with separately licensed features. A public community edition does not imply that enterprise governance or AI services are free.
- Source available: Code can be inspected, but the license may restrict use or distribution. This is not interchangeable with open source.
- Self-hosted: A deployment option. Both open-source and proprietary products may support it; it does not establish licensing rights by itself.
How an open-source low-code app runs
The builder generally saves application configuration, queries and logic that a platform runtime executes. Access to the platform source does not automatically turn your app into a standalone React application or remove runtime dependencies. Test application export, data export and restore separately.
Why teams consider open-source low-code
Useful reasons include inspecting implementation details, extending connectors, controlling deployment and reducing dependence on a single hosted service. Those benefits require the skills and rights to maintain the relevant code. A fork that nobody can patch or operate is not a practical exit plan.
Examples and edition boundaries
ToolJet, Appsmith, Budibase, Joget, Saltcorn and Convertigo have public codebases with open-source licensing for the scope described below. Commercial features and services can have different terms. Review each package and edition instead of applying one repository label to the entire product.
Open-source vs closed-source low-code: the practical differences
Comparison table
| Decision | Open-source edition | Closed-source offering |
|---|---|---|
| Source rights | Inspect and modify covered code under its license | Use supported APIs, extensions and configuration under vendor terms |
| Customization | Platform changes may be possible, with maintenance costs | Can still support extensive custom logic and integrations |
| Cost | Hosting, support, operations and commercial features may cost money | Subscriptions, usage, implementation and operations determine cost |
| Lock-in | Runtime, data model and app definitions can still create dependencies | Portability depends on export formats, APIs and contract terms |
| Security | Visibility enables inspection; patching and configuration still matter | Assess controls, evidence, patching commitments and your responsibilities |
| Support | Community help and paid vendor support may both exist | Contract scope and service commitments vary |
| Updates | Release cadence and upgrade work depend on the project | Release cadence and upgrade work depend on the vendor and deployment |
Neither model guarantees better security, faster updates or lower total cost. Compare evidence for the exact product and deployment. For an enterprise purchase, the missing feature in a community edition may matter more than the headline license.
What are closed-source low-code platforms?
Closed-source low-code products do not grant general open-source rights to their platform code. They can still offer SDKs, APIs, custom components and deployment options. Restricted platform source access should not be confused with an inability to customize an application.
What to evaluate in a proprietary offering
- Supported extension points and limits on custom code.
- App and data export formats, with a tested restore or migration path.
- Contracted support, security evidence and release responsibilities.
- Seat, environment, API, storage and AI usage charges.
Comparing a proprietary product with an open-source option
Use the same application, user roles, data sources and acceptance criteria in both pilots. For the enterprise form-and-workflow comparison appearing in this topic, see HCL Leap vs ToolJet. Keep platform licensing, application requirements and deployment choices as separate decisions.
Seven platform options and their licensing scope
| Platform | Relevant use case | License or edition checkpoint |
|---|---|---|
| ToolJet | AI-generated internal apps with visual editing | AGPL-3.0 community foundation; confirm paid capabilities |
| Appsmith | Internal tools with JavaScript and connected data | Apache-2.0 repository; verify commercial feature scope |
| Budibase | Apps, automation and AI agents | GPLv3 overall; package-specific licenses and BSL paid features |
| NocoDB | Database workspace with spreadsheet-style interaction | Sustainable Use License; source available, not the same category |
| Joget | Process and workflow applications | GPLv3 Community Edition; commercial editions separately licensed |
| Saltcorn | Database-driven no-code applications | MIT-licensed repository |
| Convertigo | Web and mobile business applications | AGPL-based Community Edition; confirm edition requirements |
1. ToolJet

ToolJet’s public repository provides its AGPL-3.0 foundation. The product supports building internal apps from prompts and refining them in a visual builder, with connected databases, APIs and a built-in database. Consider it for operational interfaces that need controlled access to business data.
Check the Cloud and Self-hosted plans for enterprise features and add-ons. BYOK for LLM keys is an Enterprise add-on on both deployment options. Deploying the AI gateway on your own infrastructure and fully air-gapped operation are Self-hosted Enterprise add-ons. Backend Workflows are a Self-hosted product. Do not assume every capability is included in the community edition.
2. Appsmith

Appsmith is an internal-tool builder with widgets, JavaScript and data integrations. Its public repository identifies an Apache-2.0 license. Pilot a real dashboard or operations app, including query behavior and permissions, then verify the commercial edition requirements for your rollout.
3. Budibase

Budibase covers apps, automations and AI agents. Its licensing guidelines describe GPLv3 overall, package-specific licenses and Business Source License terms for paid features. Review the package and feature boundaries instead of assuming all visible source has identical permissions.
4. NocoDB: a source-available option

NocoDB offers a database workspace with spreadsheet-style interaction. Its current license is the Sustainable Use License and contains use and distribution restrictions. It is included here to clarify a common category confusion, not presented as an open-source equivalent. Review the terms for your intended deployment or service.
5. Joget

Joget combines application development, business process automation and workflow management. Its Community Edition is GPLv3; its repository identifies separate commercial editions. Evaluate a complete process with assignment, exceptions and integrations, then confirm the plugins and edition needed to operate it.
6. Saltcorn

Saltcorn is an MIT-licensed no-code application builder focused on database-backed applications. It is a useful candidate for teams that want a configurable data app and can evaluate its plugin ecosystem. Test authentication, permissions, backups and required integrations before choosing it for a critical workload.
7. Convertigo

Convertigo describes its Community Edition as an AGPL-based platform for web and mobile applications, with frontend and backend tooling. Consider it when mobile delivery is central. Validate the required offline behavior, deployment tooling and commercial feature boundaries in a representative application.
How to choose an open-source low-code platform
Define acceptance criteria before comparing feature lists. A small pilot should prove both the application experience and the way your team will operate it.
Enterprise evaluation checklist
- Application fit: Build one representative workflow with a table, form, validation, an approval and an integration failure. Test mobile behavior if employees use phones.
- License scope: Record the repository version, package licenses and commercial features required. Have the relevant reviewer assess obligations for your intended use.
- Access controls: Test unauthorized record access through UI actions and underlying queries or APIs. Hidden buttons are not a substitute for enforced permissions.
- Deployment: Rehearse installation, backup restoration, upgrades and rollback. List outbound network dependencies, including AI, licensing and monitoring.
- Change management: Separate development, staging and production as required. Validate how app configuration, secrets and database changes move between them.
- Support: Establish who handles incidents, security patches and upgrade conflicts. A public issue tracker does not guarantee an SLA.
- Exit plan: Export app definitions and business data, identify runtime dependencies and test recovery on a clean deployment.
AI evaluation: Separate builder assistance from production agents. Check model-provider support, BYOK availability, what data leaves your environment, permissions, retention and usage charges. Self-hosting the app builder alone does not establish that all AI processing stays on your infrastructure.
Cost evaluation: Add licenses, hosting, backups, monitoring, upgrades, support, implementation and AI usage. Compare the same user population and environments. A free software license does not make infrastructure or engineering time free.
Choose the operating model as well as the builder
Start with the application and governance requirements, shortlist two or three matching platforms, then test the license, deployment and exit assumptions. For ToolJet, review self-hosting options, security controls and AI app generation alongside the plan you intend to buy.









