Open Source Superblocks Alternatives

ToolJet builds the operational software that never quite justifies a full project. Admin panels, dashboards and internal apps sit on the databases, APIs and SaaS systems a company already runs, and the visual builder does the assembly work that would otherwise become a bespoke frontend nobody wants to maintain.

Apps can also be produced by prompting. ToolJet AI turns a description into pages, queries and components, and a Model Context Protocol server lets an existing coding agent do the same. Agents build against real component and data contracts, so what comes out is an app the team keeps editing in the visual builder under the same permissions, environments and version history as everything else.

The community edition carries the parts most internal tools need.

• Visual builder: more than 80 responsive components covering tables, charts, forms, lists and progress bars.
• Built in database: a no-code ToolJet Database for application data.
• Data sources: more than 90 connectors to databases, APIs, cloud storage and SaaS tools.
• Collaboration: multiplayer editing, inline comments, mentions and granular access control.
• Code anywhere: JavaScript and Python run inside apps, and a CLI creates custom plugins and connectors.
• Security: AES-256-GCM encryption, proxy only data flow and SSO support.

A single Docker command runs it locally, and deployment guides cover Kubernetes, AWS EC2 and ECS, GCP, Azure, DigitalOcean, OpenShift and Helm, with the LTS image recommended over latest for production. Enterprise tiers add workflows, an agent builder, multi environment management, GitSync and row level access control. The MCP server is currently in beta.

Organizations build dashboards, admin panels, customer 360 screens, IT automation and service management tools so their teams work more efficiently, and each one turns into a small bespoke application somebody has to keep alive. Appsmith is an open-source low-code platform that takes on the development, deployment and maintenance of exactly that class of software.

Appsmith Agents extends the same idea into agentic AI, connecting current models to private and proprietary data inside the systems teams already use every day. It targets knowledge workers in sales, support, customer success and human resources, who can ask questions and configure automations for their own business without model fine-tuning or a retrieval pipeline to build first.

Around the builder sits the material that gets a team productive.

• Templates: a library of prebuilt applications to start from instead of an empty canvas.
• Docker install: the recommended self-hosted route, documented end to end.
• Kubernetes and AWS: guides for a cluster deployment or an AWS machine image, with further options in the installation docs.
• Documentation and tutorials: setup guides, step-by-step tutorials and a video channel.
• Community support: a Discord server, a community portal and a support address for questions.

Two starting points exist, a signup on the hosted cloud or an install on your own machine, and a local development setup is documented for anyone who wants to contribute code. Appsmith fits teams that keep writing the same internal admin screens and would rather run one platform than a pile of one-off apps.

Refine Core is a React meta-framework for CRUD heavy applications, positioned between a low code builder and starting from an empty folder. Its hooks and components supply the parts every internal tool needs anyway, authentication, access control, routing, networking, state management and internationalization, so none of those are rebuilt per project.

The architecture is headless, decoupling business logic from the interface and the router. That leaves the design open to Tailwind or any custom styling while keeping built in support for Ant Design, Material UI, Mantine and Chakra UI, and it lets the same application run on Next.js, Remix, React Native or Electron through one routing interface.

Several pieces come ready to use.

• Data connectors: more than 15 backends including REST, GraphQL, NestJS CRUD, Supabase, Hasura, Appwrite, Firebase, Strapi, Sanity and Directus.
• Generated CRUD screens: interfaces derived from the data structure your API already exposes.
• State and mutations: handled through React Query rather than a bespoke layer.
• Live applications: real time behavior supported out of the box, alongside audit logs and document versioning.
• Devtools: a companion tool for inspecting what the application is doing.

A project starts from a single create command or from a browser playground, under an MIT license. The framework is aimed at data intensive B2B work such as admin panels, dashboards and internal tools, though server side rendering also makes customer facing storefronts practical.

Reflex takes JavaScript out of the equation for Python developers building web apps. Frontend and backend are written in one language, in one file for a small app, so there is no separate client project, no API contract to keep in sync between halves, and no build toolchain to learn first.

The model is state plus events. A class inherits from the framework's state object and holds the app's data as typed attributes, event handlers mutate that state, and components declared as Python function calls re-render when it changes. An async handler can yield partway through to update the interface while slower work continues, which is how a loading state appears without extra plumbing.

Getting an app running takes a handful of commands.

• Project setup: create a directory, add reflex with uv, then run init and run.
• Local server: the development app serves on port 3000 straight away.
• Fast refresh: saved changes show up immediately, with no manual restart.
• Python components: headings, inputs, buttons and images are function calls, not templates.
• Room to grow: the framework stays approachable for a first app while scaling to complex ones.

Around the open source library the maintainers offer an AI builder that generates full-stack apps, an agent toolkit that connects MCP and skills to a coding assistant, and a hosting service for deployment and app management. A published architecture write-up explains what happens under the hood for anyone who wants the details first.

Every company accumulates the same pile of requests: employees asking questions, requesting approvals and reporting issues. The tooling that answers them usually gets stitched together from several separate products. Budibase puts the apps, the automations and the agents on one platform instead.

Its agents do more than reply. They run workflows across the business, creating records, routing approvals, updating apps and notifying teams, wired into the databases, AI models and business systems already in use.

The platform covers the parts an internal tool normally needs.

• Apps and automations: build the interfaces and the workflows behind them without assembling separate builders.
• Data connections: integrate databases, AI models and business apps so agents and automations can act across operations.
• Public API: use Budibase as a backend, with an API key, a published spec and interactive reference documentation for building integrations on top.
• User management: manage users, onboarding, SMTP, apps, groups and theming globally, then hand group administration to a group manager.
• Self-hosting: deploy with Docker, Docker Compose, Kubernetes, DigitalOcean or Portainer on infrastructure you already own.

A single ARM compatible Docker image covers the simplest install, and Budibase Cloud exists for teams that would rather not run anything. It suits engineering teams tired of building the same approval flow and admin panel from scratch, and the documentation and GitHub discussions carry the rest.

Windmill turns scripts into internal tooling. You write a small script that does one job, and the platform parses its parameters, generates a form for it, and makes it callable as an API, a scheduled job or a step inside a larger flow.

The backend is Rust, running stateless API servers and workers that pull jobs from a Postgres queue, with a Svelte front end above them. Jobs are sandboxed with nsjail and PID namespace isolation, and once a job starts there is no overhead beyond roughly 50 milliseconds of queue latency.

Languages and triggers are deliberately wide.

• Runtimes: TypeScript on Bun or Deno, Python with uv, plus Go, Bash, PowerShell, PHP, Rust, C#, Java and Ansible.
• Flows and apps: chain scripts into flows, or assemble richer interfaces in the low-code app editor.
• Triggers: schedules, webhooks, HTTP routes, Kafka, WebSockets and inbound email.
• Local development: a CLI, a VS Code extension and two-way Git sync between your repository and the instance.
• Secrets: one encryption key per workspace for credentials kept in the platform's key-value store.

The Community Edition is free to use internally, while reselling it or serving it as a managed offering needs a commercial agreement. Self-hosting is three files and a Docker Compose command, or a Helm chart on Kubernetes, and it runs on AWS, GCP, Azure, Fly.io, Hetzner and others at roughly one worker per vCPU.