For developers choosing a low-code platform, compare what your team builds, which runtime executes it and what can move when requirements change. ToolJet combines AI generation, visual editing and custom queries with customer-operated deployment options. Retool offers developer-led internal apps, while Appsmith and Budibase provide open-source approaches. Mendix and OutSystems address broader app portfolios, and Power Apps fits Microsoft environments. A local source file, an exported app definition and an independently runnable application are different artifacts.
This guide compares 10 platforms through runtime ownership, extension, integrations, deployment and migration. Use the vendor sections to shortlist candidates, then test one app through an edit, export/import and release cycle. For a wider scan by workload, use the 25-platform use-case directory. For buying-team requirements, use the enterprise comparison.
How to Evaluate Runtime, Extension and Exit Paths
This guide is published by ToolJet. Its order is an editorial selection, not an independent ranking or a standardized benchmark. Selected pricing, deployment, app-export and coding-agent claims were checked against primary sources on October 4 and 5, 2026. This does not verify every capability or contract term. Check ToolJet pricing and each vendor’s current documentation before purchasing.
Start with five engineering questions:
- Runtime and artifacts: What files or app definitions can you inspect, version and export? Which services are still required to run the app?
- Extension: Can you express the required logic, add a custom interface and manage its dependencies? Check where browser code, server queries and background work execute.
- Integrations: Test the exact query, write and authentication your app needs. A connector name does not establish support for every operation.
- Deployment: Identify who operates the editor, runtime, databases and AI services. Test the same edition and deployment boundary you intend to use.
- Migration and cost: Move a representative app, reconnect its data and record what must be recreated. Include licensing, infrastructure and maintenance in the comparison.
The List at a Glance
| Platform | Best For | Free Tier | Entry Pricing | Self-Hosting | App Artifact / Exit Check |
| Retool | Internal tools, admin panels | Up to 5 users; 250 pooled AI credits/month on Cloud | $10/builder + $5/internal user/mo (Team, annual billing) | Docker, Kubernetes, Helm; confirm Enterprise terms | Local Retool-native React files or classic JSON/Toolscript; publish to Retool |
| Appsmith | Open-source internal tools | 5 users on Free Cloud; free Community self-hosting, check limits | $15/user/mo (Business); Enterprise $2,500/mo for 100 users | Cloud or Self-hosted; check the selected edition’s commercial terms | Community source: Apache 2.0. Which app definitions export, and which runtime and resource settings remain necessary? |
| Budibase | Budget CRUD, forms, approvals | Free self-hosted: unlimited users/apps, 1 workspace | Cloud creators, end users and usage; confirm billing interval and allowances | Yes, unlimited users free | App templates import into Budibase; full installation backups are separate |
| ToolJet | AI-generated, visually editable internal apps and coding-agent builds | Free: 2 builders, 50 end users, 10 apps | Paid builder plans; AI credit allowances and Enterprise quote vary by plan | Customer-operated self-hosting (Free, Team, Enterprise) or managed Cloud | JSON app definitions import into ToolJet; Community runtime source is open |
| Superblocks | Governed AI app building with enterprise deployment options | 14-day trial; confirm evaluation allowances | Teams $125/mo monthly or $100/mo annual; up to 15 builders and GAU usage | Hybrid data plane or full-platform AWS Cloud-Prem managed by Superblocks | Which generated files, source-control features and runtime dependencies apply to the chosen edition? |
| Mendix | Governed enterprise app portfolios | Free plan; check evaluation/user limits | Standard from €918/mo One App in EUR view; compute resources extra | Yes (Mendix Cloud, on-prem, SAP BTP) | Which models and resources export, and which runtime rights are needed to operate them? |
| OutSystems | Complex, mission-critical enterprise apps | Free Personal Edition for evaluation and learning | Quote-based; confirm edition, capacity and deployment | Yes | Which source artifacts, modules and runtime rights does the selected product and contract include? |
| Microsoft Power Apps | Microsoft 365 / Dataverse shops | Free Developer Plan for non-production; limited Microsoft 365 rights vary | $20/user/mo paid yearly (Premium, US view); verify region | Data gateway only; application service runs in Microsoft cloud | Solution ZIP packages deploy to Power Platform environments; check dependencies |
| Appian | Case management, process automation | Free Community Edition for learning/evaluation | Production priced per user/month/app; obtain scope-specific quote | Yes (Appian Cloud or Kubernetes) | Application/package ZIP files deploy to Appian; check version compatibility |
| Bubble | Customer-facing MVPs, product validation | Free development version; paid plan for launch | Paid tiers by project, workload and web/mobile scope | No (managed hosting only) | User data exports as CSV or through APIs; applications run on Bubble |
1. Retool
Developer-led internal apps over databases and APIs, with Cloud and Enterprise deployment options.
Retool combines data connections, queries, interface components, workflows and mobile apps for internal software. Its public-beta CLI lets developers edit Retool-native React apps locally, then preview and publish them to Retool. Classic apps export as JSON or Toolscript; their data resources must be configured separately after import. Test the artifact and deployment path for the builder you will use, rather than treating local files as proof of platform-independent execution.
Best For
- Teams building internal apps over databases and APIs that accept a proprietary application runtime
- Ops-heavy organizations where one tool sprawls into twenty, because the ecosystem depth keeps paying off
- Small teams that fit the 5-user free tier or the $10/$5 Team tier
Not For
- Organizations with a hard open-source requirement or an exit-path policy for core tooling
- Large deployments where per-user pricing across hundreds of internal users breaks the budget
- Teams that need advanced self-hosted features without an Enterprise contract
Why it fits: Retool centers on data connections, queries, components, and operational interfaces. A support dashboard can read customer records from PostgreSQL, call a billing API, and expose controlled actions to authorized staff.
What to check: Separate builder, internal-user, and external-user requirements. Features such as richer permissions, audit logs, source control, and self-hosting depend on the plan and deployment model, so the trial should use the controls required in production.
| LICENSE | PRICING MODEL |
| Proprietary; cloud and self-hosted | Separate builder and end-user seats, not flat per-user |
| ENTERPRISE | SELF-HOSTING |
| Custom; adds SSO, source control, advanced self-hosting | Docker, Kubernetes, Helm; advanced features need Enterprise |
PRICING Retool Free includes up to 5 users and 250 pooled AI credits/month. Annual Team pricing is $10/builder plus $5/internal user/month; Business is $50/builder plus $15/internal user/month. Enterprise is custom. Review current plan details for governance, deployment and usage limits.
2. Appsmith
The open-source counterweight: Apache 2.0, free to self-host, and the simplest pricing model in the category when you go commercial.
Appsmith is worth evaluating when an open-source Community runtime and developer-controlled queries are requirements. Compare its widgets, JavaScript logic and release workflow using the same application as the other candidates. For commercial editions, estimate the cost of builders, regular users and occasional viewers under the current user-counting rules; interface polish and development speed should be established in your pilot.
Best For
- Open-source-first organizations that want a real self-hosted deployment with no license fee
- Teams that want flat, predictable per-user pricing without builder and end-user seat classes
- Teams that need Enterprise SCIM/SAML controls, with the air-gapped edition quoted separately as an add-on
Not For
- Teams whose required interface or editing workflow does not fit Appsmith; compare the same app in a pilot instead of assuming one builder is fastest
- Deployments with hundreds of read-only users, where flat per-user pricing penalizes viewers
Why it fits: Appsmith provides a drag-and-drop canvas, JS-backed logic, and native connectors to databases and APIs, all self-hostable under Apache 2.0. A support-ticket triage app can query Postgres directly, run custom validation logic, and stay entirely on infrastructure your team controls.
What to check: Count the users who build, edit or use applications under the current billing terms. Appsmith treats developers as standard users, with no additional developer-seat surcharge. Test the supported self-hosted deployment and confirm the governance edition needed before connecting production data.
| LICENSE | GITHUB |
| Apache 2.0 (Community Edition) | 40k+ stars (verified July 2026) |
| PRICING MODEL | ENTERPRISE |
| Flat $15/user/month Business; no separate builder seat price | $2,500/month for 100 users; SAML, SCIM; air-gapped add-on |
| SELF-HOSTING |
| All tiers; Community Edition free |
PRICING Appsmith pricing lists Free Cloud for up to 5 users and a free open-source Community platform. Business is $15/user/month for up to 99 users; Enterprise is $2,500/month for 100 users. Confirm user counting, contract billing and any deployment add-ons for the edition you will operate.
3. Budibase
The budget workhorse for CRUD, forms, and approvals: unlimited apps and users on the free self-hosted edition.
Budibase is the value pick when the tools you need are data tables, forms, approval chains, and notifications rather than dense custom UIs. It ships its own built-in Budibase DB (built on CouchDB) alongside connectors for external databases, spreadsheets, and business systems, so small teams can skip standing up a database entirely. The limits are real, though: for complex, code-heavy tools the ceiling arrives sooner than on Retool or Appsmith.
Best For
- Simple CRUD apps, forms, and approval workflows shipped by small teams on small budgets
- Self-hosters who want unlimited users for free and can live within one workspace
- Teams without an existing database who benefit from the built-in Budibase DB
Not For
- Complex, JavaScript-heavy internal tools with dense custom interfaces
- Automation-heavy cloud workloads that will blow through metered action allowances
- Legal teams that need a single clean open-source license across the whole product
Why it fits: Budibase pairs a built-in database with a drag-and-drop UI builder and visual automations, so a small ops team can go from “we need a form” to a working approval flow without provisioning a database first.
What to check: Confirm your automation-run volume against the metered allowances on paid cloud tiers, and decide up front whether the free self-hosted edition’s single-workspace limit fits your team structure.
| LICENSE | GITHUB |
| GPL v3 core, MPL client libraries; paid features under a Business Source License | 28k+ stars (verified July 2026) |
| PRICING MODEL | ENTERPRISE |
| Per-creator + per-end-user on Cloud; free unlimited on self-hosted | Custom; adds SCIM and audit logs with 365-day retention |
| SELF-HOSTING |
| Free, open-source, unlimited users within one workspace |
PRICING Budibase’s free self-hosted Open-source edition includes one workspace with unlimited apps and users. Cloud plans combine creators, optional end users and usage allowances; Pro and Premium include one creator, and Business includes three. Check the selected billing interval, usage and add-ons before quoting a total. Enterprise has custom terms.
4. ToolJet
AI-assisted internal apps with visual editing, custom code and a platform you can operate on your own infrastructure.
ToolJet pairs an AI app builder with a visual editor and 100+ integrations. Its MCP server lets Claude Code, Codex and other coding agents build and maintain native ToolJet apps that remain editable visually. Building through your coding agent consumes no ToolJet AI credits; your agent subscription or model-provider charges still apply.
Best for: Teams building internal dashboards, CRUD apps and operational tools that need a mix of AI generation, visual editing and JavaScript, Python queries or custom React components. Choose managed Cloud or self-host the open-source Community Edition or a commercial plan. ToolJet Academy provides hands-on courses and certifications.
What to check: Team includes SSO, audit logs and Git sync; Enterprise adds SCIM and further lifecycle and deployment controls. Private AI requires the Self-hosted Enterprise gateway add-on and a supported local model. Enterprise BYOK is available on both ToolJet Cloud and Self-hosted deployments. Air-gapped operation is a separate Self-hosted Enterprise add-on; BYOK alone does not keep requests to an external provider on your infrastructure. Workflows and Agent Builder are available on self-hosted deployments, not Cloud.
Trade-offs: Cloud end-user allowances are 50 on Free, Basic and Pro, and 100 on Team; Enterprise includes unlimited end users. Advanced logic needs technical skills. Self-hosting requires infrastructure and operational ownership, and the Community Edition uses AGPL-3.0. Evaluate governance and commercial licensing requirements before production deployment.
Customer evidence: FalconX reported an 85% reduction in internal tool development time. Validate the same app, data access rules and release process for your organization rather than treating one customer’s result as a universal benchmark.
| LICENSE | DEPLOYMENT |
| AGPL-3.0 Community Edition; commercial editions have separate terms | Managed Cloud or customer-operated self-hosting; air-gapped deployment is a Self-hosted Enterprise add-on |
Pricing: ToolJet Free includes 2 builders, up to 50 end users and 10 apps. Cloud Basic, Pro and Team are paid builder plans; Basic and Pro include 2,000 AI credits per builder/month, and Team includes 3,000. Enterprise has custom pricing. Review the current Cloud and Self-hosted tables with the intended billing interval for features, user limits, credit allowances and add-ons.
5. Superblocks
AI-generated internal apps with Cloud, Hybrid and full-platform AWS Cloud-Prem deployment options.
Superblocks’ Clark AI agent generates internal apps under organization governance. Its deployment documentation distinguishes Cloud from Hybrid, where production execution stays in the customer VPC while Clark uses non-production data in Superblocks Cloud, and Cloud-Prem, where the full platform and AI inference run in a customer AWS account managed by Superblocks. Confirm the selected architecture before making a data-residency claim.
Best For
- Enterprises where production data must stay inside the corporate network without self-hosting the whole platform
- Organizations rolling out AI-assisted app building to business teams and needing centralized guardrails
- Teams with unlimited end users against a small builder group, which its seat model prices well
Not For
- Teams that require a permanent free tier rather than the current 14-day trial
- More than 15 builders without going to Enterprise
- Teams that require an open-source platform they can operate independently of the vendor
Why it fits: Superblocks combines Clark app generation with governed resources and Enterprise controls. Choose Hybrid for an in-VPC production data plane with cloud-managed development, or AWS Cloud-Prem when the full platform and inference must run inside the customer account.
What to check: Superblocks now prices Teams as a flat pack with up to 15 builders, rather than a charge per AI builder. Check the current pricing and GAU allowances. Its deployment documentation distinguishes Hybrid from full-platform Cloud-Prem in the customer’s AWS account, managed by Superblocks.
| LICENSE | PRICING MODEL |
| Proprietary; no open-source edition | Flat Teams pack with up to 15 builders; AI usage metered in Governed Agent Units |
| ENTERPRISE | SELF-HOSTING |
| Custom; VPC deployment, SSO/SAML/OIDC, audit logs, Clark policy layer | Hybrid: data plane in your VPC. Cloud-Prem: full platform including AI inference in your AWS account, managed by Superblocks. Confirm Enterprise requirements. |
PRICING Superblocks Teams is $125/month billed monthly or $100/month billed annually. The published scope includes up to 15 builders, unlimited end users, 1 hosted app and 100 Governed Agent Units/month. Additional hosted apps and GAU packs affect the total. Enterprise is custom.
6. Mendix
Governed enterprise application portfolios: model-driven development with agile collaboration built in.
Mendix uses Studio Pro to model application data, pages, microflows and workflows. Its current Maia documentation describes AI assistance that creates and updates those model documents, which developers can inspect and edit in Studio Pro. Evaluate the Studio Pro version, deployment and AI capabilities you intend to use rather than relying on the older Studio versus Studio Pro split. Check where AI requests are processed and which features are generally available or in beta.
Best For
- Enterprise teams building a portfolio of applications who need centralized governance
- Organizations willing to invest in the Studio Pro learning curve for long-term payoff
- Teams needing deep SAP integration alongside a low-code front end
Not For
- Small teams or one-off builds, the licensing model and learning curve are heavy for anything short-lived
- Teams that need a fast, lightweight build experience over governed, model-driven structure
Why it fits: Mendix represents application logic, data, workflow, and interfaces through model-driven development. A supplier-onboarding app can let procurement review the process while developers connect identity, ERP, and document services.
What to check: Decide whether the target is one application or a portfolio. Mendix’s “One App” vs. “Unlimited Apps” pricing differs by commercial model rather than platform capability, “Unlimited Apps” does not mean unlimited users, infrastructure, or total cost, and Mendix lists a separate commercial model for ISVs.
| LICENSE | PRICING MODEL |
| Proprietary; Free plan available for evaluation | Per-app; “One App” vs. “Unlimited Apps” are different commercial models |
| ENTERPRISE | SELF-HOSTING |
| Custom; ISVs priced under a separate commercial model | Mendix Cloud (AWS), private Kubernetes, on-premises, or SAP BTP |
PRICING Mendix lists Free, Standard and quote-based Premium. Standard currently starts at €918/month for One App or €2,295/month for Unlimited Apps in the EUR view. User entitlements and cloud compute affect the total; confirm the currency and full deployment quote.
7. OutSystems
Enterprise-scale, mission-critical applications with genuine DevOps tooling built into the IDE.
OutSystems provides visual application development, integrations and lifecycle tooling, but OutSystems 11 and OutSystems Developer Cloud (ODC) have different extension and deployment paths. For example, ODC documents external libraries written in C#. Evaluate the selected product’s custom-code support, dependency management, monitoring and release workflow. Do not assume an extension written for a historical runtime or another OutSystems product will run unchanged.
Best For
- Enterprise IT departments modernizing legacy systems
- Customer-facing apps that need scale and performance guarantees
- Teams that want automatic dependency management across a large module portfolio
Not For
- Teams that want to move fast on day one, initial environment setup and the learning curve are longer than SaaS-first tools on this list
- Teams without an agreed exit path for platform-specific models, integrations and runtime dependencies; confirm migration rights and effort for the selected product
Why it fits: OutSystems combines visual development with enterprise integrations, lifecycle tooling, governance, DevSecOps, and monitoring. It can suit a customer portal that must connect with legacy services and move through controlled releases.
What to check: Confirm which capabilities apply to the selected product, edition, deployment model, and contract, do not assume every governance, observability, integration, or hosting option is included in the same commercial scope.
| LICENSE | PRICING MODEL |
| Proprietary | Quote-based, sized by app capacity and environments |
| ENTERPRISE | SELF-HOSTING |
| No distinct published tier, all production pricing is negotiated per account | OutSystems Cloud (SaaS), managed PaaS, or your own on-premises/private cloud |
PRICING OutSystems offers a free Personal Edition for evaluation and learning. Production pricing depends on users, features, support, hosting and application requirements; request a scoped quote using its current pricing guidance.
8. Microsoft Power Apps
The default choice when the real decision is Microsoft 365, not the low-code platform itself.
Power Apps is relevant when applications need to work with Microsoft 365, Teams, SharePoint or Dataverse. Canvas apps support interface-driven design, while model-driven apps center on the data model. Microsoft also documents connectors for non-Microsoft services and databases. Integrations still require authentication, permissions and licensing checks. An on-premises data gateway connects supported internal data sources to the cloud service; it does not self-host the application platform.
Best For
- Organizations already committed to the Microsoft ecosystem needing internal forms, approvals, and team workflows
- Teams with Excel power users who can pick up Power Fx quickly
- Orgs that want apps to feel like a natural extension of Teams and SharePoint
Not For
- Organizations outside Microsoft 365, integration speed and flexibility drop sharply once you’re not in that ecosystem
- Anyone evaluating it as a standalone platform rather than an ecosystem decision
Why it fits: Power Apps works closely with Teams, SharePoint, Dataverse, and Power Automate. A practical scenario is an employee leave-request app that stores records in Dataverse and routes approval through Power Automate.
What to check: Map every connector and user type before estimating cost. Microsoft’s licensing guidance for premium features states that premium connectors, custom APIs, and on-premises gateways can require premium entitlements, gateway access also depends on the supported connector, license, and tenant configuration.
| LICENSE | PRICING MODEL |
| Proprietary; bundled with Microsoft 365/Azure licensing | Per-user or per-app, or pay-as-you-go; premium connectors may need added entitlements |
| ENTERPRISE | SELF-HOSTING |
| Negotiated via a Microsoft account team, not a separate published tier | On-premises data gateway for internal data only, not full app hosting |
PRICING Microsoft lists a free Developer Plan for non-production building and testing. In the US pricing view, Premium is $20/user/month paid yearly, or $12/user/month with a 2,000-seat minimum. Limited Microsoft 365 use rights do not establish entitlement for every app, connector or deployment; confirm the production license for each user and workload.
9. Appian
Process-first, not screen-first: automation and case management for regulated, high-stakes workflows.
Appian’s strength is modeling an entire business process visually, swimlanes per role, decision gateways, escalation timers, rather than modeling a single screen or form, backed by a unified data layer that aggregates records from multiple sources into one view. Its Case Designer and Decision Management tools let business users build rules without developer involvement, and RPA bots handle legacy systems with no API.
Best For
- Large organizations automating complex, regulated processes, claims handling, onboarding, compliance workflows
- Teams where audit trails and case management matter as much as build speed
- Public-sector and regulated deployments needing FedRAMP/DoD certification
Not For
- Teams wanting flexible, highly-branded custom UI; Appian’s interface is functional but not built for pixel-perfect design work
- Business users expecting to be productive without training or certification
Why it fits: Appian combines low-code application development with process automation and a data fabric. A claims or exception process can move through intake, evidence review, approval, and audit steps in one governed workflow.
What to check: Match the required process and case features to the contracted tier. Appian’s Standard, Advanced, and Premium capability matrix shows tier differences for data scale, portals, automation, case management, and AI features.
| LICENSE | PRICING MODEL |
| Proprietary | Per-user, per-month, per-app, across Standard/Advanced/Premium tiers |
| ENTERPRISE | SELF-HOSTING |
| Premium is the top published tier; very large rollouts are custom-negotiated on top of it | On-premises, Appian Cloud (including FedRAMP High), or hybrid |
PRICING Community Edition offers free learning/evaluation access. Production Appian tiers are priced per user, per month, per app, with Standard, Advanced and Premium capability differences. Obtain the scope-specific production quote.
10. Bubble
Customer-facing MVPs and product validation, the picture is a real app, not an internal tool.
Bubble is the pick when the goal is validating a customer-facing product idea, not building an internal tool. Its visual editor, built-in database, API connector, plugin ecosystem, and workflow engine let a team test registration, listings, payments, and admin flows before committing to custom architecture. Per its own application and data-ownership documentation, user-created data can be exported, but the application itself cannot be exported as a conventional, portable codebase; it has to keep running on Bubble’s infrastructure.
Best For
- Founders and product teams validating an MVP or early-stage SaaS product
- Teams that want a real, testable product surface before committing to custom architecture
Not For
- Long-term production systems where code ownership matters
- Teams that need to understand workload-based cost behavior (traffic, database size) before it’s clear what the bill will look like at scale
Why it fits: Bubble provides a visual editor, database, workflows, API connections, plugins, and managed hosting. A booking marketplace can test registration, listings, transactions, and admin operations before the product team commits to a custom architecture.
What to check: Test workload behavior and migration boundaries before traction grows. Bubble’s application and data ownership documentation says user-created data can be exported, while the application cannot be exported as a conventional codebase and must run on Bubble.
| LICENSE | PRICING MODEL |
| Proprietary; managed hosting only | Project/workload-based (compute and capacity usage), not flat per-seat |
| ENTERPRISE | SELF-HOSTING |
| No sourced detail on a distinct tier, confirm directly with Bubble | Not offered |
PRICING Bubble has a free development plan; launching requires the appropriate paid tier. Compare the web, mobile and combined plan options, workload allowances, editors and any overages for your intended application.
Test the Exit Path Before You Commit
Use one small application to expose the difference between development convenience and long-term control. Include an ERP read and write if that is your target workload, with authorization, pagination, retries and an audit trail. For security requirements, request evidence for the exact service, edition and deployment: a vendor badge alone does not establish your application’s compliance. For a federal-cloud requirement, check the specific offering and current status in the FedRAMP Marketplace. Keep customer configuration and operating responsibilities in the evaluation. Record the result of each step:
- Inspect: Save the application artifact, queries and custom logic in the form the platform supports. List the runtime, packages and external services it depends on.
- Extend: Make a representative change that the visual editor alone cannot express, then test how your team reviews and maintains it.
- Move: Export or clone the app and import it into a clean supported workspace or instance. Reconnect resources, credentials and permissions rather than assuming they travel with the artifact.
- Exit: Identify which data, code and configuration remain usable if the platform is removed, and what would need conversion or rebuilding.
- Decide: Compare the observed migration and operating work with the alternative of maintaining a custom app. Do not infer portability from open-source licensing, a Git repository or a download button alone.
For ToolJet, app exports are JSON definitions that can include versions, modules and ToolJet Database schemas for import into ToolJet. That is different from exporting a standalone app with no ToolJet runtime. Use the reliability evaluation for release and recovery questions, and the enterprise procurement guide for commercial and operating responsibilities.
