Open Source App Cloud Marketplace

Webhooks, cron schedules, and app events trigger chains of nodes that fetch, transform, and route data: n8n is a workflow automation platform built around a visual, node-based editor. It ships with 400+ built-in integrations covering databases like Postgres, SaaS tools like Slack and HubSpot, and every major AI provider. When a pre-built node does not exist, the HTTP Request node calls any REST API, and the Code node runs JavaScript or Python inline, so you are never blocked by a missing connector. Workflows execute as directed graphs with branching, loops, error handling, and sub-workflows, and every run is logged for inspection and replay during debugging. It also includes LangChain-based nodes for building AI agents with tool calling and memory. Self-hosting on RepoCloud gives you unlimited workflow executions with no per-task pricing, and all data stays on your instance. Runs on Node.js with SQLite by default; add Postgres and Redis queue mode when you need to scale workers horizontally.

Drag nodes onto a canvas and ship an LLM app: Flowise is an open-source visual builder for AI agents and LLM applications, written in Node.js on LangChain.js and licensed Apache-2.0. You assemble flows by dragging nodes onto a canvas: models, prompts, memory, vector stores, retrievers, and tools, then wire them together and test in the built-in chat panel. Three builder types cover increasing complexity: Assistant for simple RAG chat over uploaded files, Chatflow for single-agent systems with techniques like rerankers and Graph RAG, and Agentflow for multi-agent orchestration with branching, looping, shared flow state, and human-in-the-loop checkpoints. Over 100 integrations connect data sources, vector databases, and both proprietary and open-source models, plus MCP client and server nodes for standard tool interop. Finished flows are exposed as REST APIs, embedded chat widgets, or via JS and Python SDKs - each flow gets an endpoint the moment it is saved, removing the deployment gap between a working prototype and something your application can call. Execution logs, visual step debugging, and external log streaming trace behavior, while input moderation and rate limiting act as guardrails; RBAC, SSO, and workspaces cover team deployments. Self-hosting keeps prompts, encrypted credentials, and conversation data on your own instance, which matters when flows handle internal documents or customer data - and wiring a model, prompt, memory, and vector store on the canvas replaces the boilerplate a hand-coded LangChain project would need.

Roughly 40 integrated business apps forming a full ERP: Odoo's open-source suite runs companies end to end. The Community Edition, licensed LGPL-3.0, ships roughly 40 apps covering CRM, sales, invoicing, basic accounting (journals, chart of accounts, taxes, reconciliation), inventory and warehouse management with multi-step routes, manufacturing with BOMs and work orders, purchasing, project management, timesheets, HR, a website builder, and eCommerce. Each app works standalone, but they share one PostgreSQL database and one data model, so a confirmed sale updates stock, triggers procurement, and posts invoices without integration glue. The modular design means you enable only the apps you need and extend with 40,000+ community modules from the Odoo app store covering nearly any vertical requirement. Inventory supports multi-warehouse stock, reordering rules, and lot and serial tracking with barcode-ready operations; manufacturing ties BOMs, work orders, and work-center routing directly to sales demand and stock levels; and the website builder sells straight from your product catalog with payment provider integrations. You can start with just CRM and invoicing on day one and switch on inventory or eCommerce later - new apps integrate with existing data instantly because the schema is shared. The server is Python with an XML/JavaScript view layer, and because data lives in plain PostgreSQL there is no proprietary format: you can query, back up, migrate, and extend business data directly, with unlimited users and no per-seat licensing - where enterprise ERP pricing is per user per month, headcount here costs nothing.

Prototype multi-agent AI systems without writing orchestration code: AutoGen Studio is Microsoft's low-code interface over the AutoGen AgentChat framework. You compose teams of LLM-powered agents in a visual Team Builder, either by drag-and-drop from a component library or by editing the declarative JSON specification directly. Each agent gets a model, a prompt, tools (Python functions), and the team gets termination conditions and an orchestration pattern, sequential or LLM-driven. The Playground runs teams interactively with live message streaming between agents, a visual control-transition graph, tool-call and code-execution tracking, and pause/stop controls, which makes it a practical debugger for agent behavior. Finished teams export as JSON for use in any Python application via the TeamManager class, or serve as an API endpoint. Any OpenAI-compatible model endpoint works, including local servers like Ollama or vLLM. Microsoft labels it a research prototype: use it for prototyping and evaluation, and build production systems on the underlying AutoGen framework.

Admin panels, database GUIs, dashboards, approval flows, customer support consoles - Appsmith builds the internal tools your team keeps postponing, on an open-source low-code platform. The UI assembles from 45+ drag-and-drop widgets - tables with server-side pagination and inline editing, charts, forms, lists, buttons - which bind to data through {{ }} JavaScript expressions anywhere in the editor. Datasources cover PostgreSQL, MySQL, MongoDB, MS SQL, Redis, Snowflake, and more, plus any REST or GraphQL API, with SaaS integrations and AI query support for prompt-based steps inside apps. When the widget library falls short, custom widgets are plain JavaScript, HTML, and CSS, and external JS libraries can be imported, which keeps the platform extensible where pure no-code tools hit walls. Git-based version control enables branch-based collaboration, review, and rollback of app definitions. Queries and JS objects hold the business logic layer between datasources and UI. Self-hosted via Docker or Kubernetes, with role-based access control for published apps.

Retool's job, self-hosted: ToolJet is an open-source low-code platform for building internal tools, dashboards, and admin panels. Apps are assembled in a drag-and-drop visual builder with 60+ responsive components, including tables, charts, forms, and lists, and connected to 80+ data sources: PostgreSQL, MySQL, MongoDB, REST and GraphQL APIs, cloud storage, and common SaaS tools. When visual configuration is not enough, you can run JavaScript or Python inline for queries and transformations. A built-in no-code database (ToolJet Database) covers apps that need their own tables without provisioning an external database, Workflows add node-based automation for background jobs with dedicated worker containers and a Redis-backed queue, and multi-page apps with multiplayer editing, inline comments, and mentions support team development. Security is designed for internal data: credentials are AES-256-GCM encrypted, data flows proxy-only through your server so database contents never reach a third-party cloud, and granular per-app access control plus SSO gate each tool. Where Retool-style platforms bill per builder and sometimes per end user, the self-hosted Community Edition serves unlimited builders and users at hosting cost, and full source availability means the platform itself can be forked, audited, and extended. The stack is Node.js and React on PostgreSQL, deployed via Docker.

Seven million emails from a single binary peaking at 57 MB of RAM: listmonk is a high-performance newsletter and mailing list manager in Go with PostgreSQL as its only dependency - no Redis, no worker processes, no message broker. The project's own production benchmark sent 7+ million emails with the binary peaking around 57 MB of RAM, and throughput exceeds 100K emails per hour on modest hardware. Campaigns run through a multi-threaded, multi-SMTP queue with round-robin delivery, per-server concurrency, retries, and sliding-window rate limiting across providers like Amazon SES, SendGrid, Mailgun, or your own Postfix relay. Subscribers carry custom JSON attributes and are segmented with raw SQL queries, so any audience Postgres can express, listmonk can target. Templates use Go template syntax with 100+ functions for dynamic per-subscriber content, and the Vue dashboard reports opens, clicks, bounces, and unsubscribes with automated bounce processing. A REST API handles transactional email and programmatic control, a built-in media library hosts campaign assets, and CSV or API import migrates lists from hosted platforms. The economics are the headline: where Mailchimp pricing scales with list size, listmonk plus Amazon SES sends the same volume for hosting cost plus roughly $0.10 per thousand emails - commonly a 95% reduction - and your email list, a core business asset, stays on your own infrastructure. AGPLv3-licensed; bring your own SMTP provider for delivery.

In-app, website, link, and email surveys feed one open-source experience management platform: Formbricks. Its distinguishing strength is targeted in-app research: a JavaScript SDK triggers surveys on user events and attributes, with segmentation rules like "power users who have not seen a survey in 10 days," so questions reach the right cohort at the right moment instead of a mass email blast. The no-code editor offers 20+ question types including NPS, CSAT, CES, matrix, ranking, and file upload, with skip logic, conditional branching, best-practice templates, and full brand theming. Responses feed built-in analytics with summaries and CSV/JSON export, and integrations push data to Slack, Notion, Google Sheets, Airtable, Zapier, and n8n, with webhooks and an open API on every tier. Because self-hosted surveys load from your own domain rather than a blacklisted third-party script host, ad blockers do not suppress them - in-app surveys reach users that Hotjar-style tools silently miss, which measurably raises response rates. Self-hosting also removes the third-party sub-processor from your privacy policy entirely: survey responses often contain PII, and keeping them on your own server matters for GDPR-sensitive and regulated industries. The Community Edition has no response caps or tier-gated features, so core functionality and your data stay accessible regardless of any subscription. Next.js on PostgreSQL, AGPLv3.

A private ChatGPT built with Next.js: Lobe Chat is the open-source AI chat interface teams self-host instead. Its main advantage is provider breadth: one interface connects to 40+ model providers, including OpenAI, Anthropic Claude, Google Gemini, Mistral, Groq, AWS Bedrock, Azure, and local models served through Ollama, so you can switch models per conversation and compare outputs. It handles multi-modal work: image recognition, image generation, text-to-speech, and speech-to-text. A plugin system based on function calling and the Model Context Protocol (MCP) adds external tools like web search and code execution. Run it in standalone mode as a single container with settings in browser storage, or in database mode with PostgreSQL and S3-compatible storage for persistent history, multi-user auth, and RAG knowledge bases built from uploaded documents with pgvector retrieval. Because tools arrive through function calling and MCP rather than a proprietary plugin format, custom internal tools can be exposed to the assistant with a standard server over STDIO or HTTP. Hundreds of pre-configured assistant roles import from the community marketplace. For teams the cost model matters: provider API keys billed per token typically undercut a ChatGPT Plus seat per person, and self-hosting keeps API keys, uploaded files, embeddings, and conversation history entirely on your own server.

Run a Stack Overflow of your own: Apache Answer brings the question-and-answer format in-house, maintained under the Apache Software Foundation with an Apache-2.0 license. You use it to run a community forum, product help center, or internal knowledge base where content lives as questions and answers rather than wiki pages. It ships the mechanics that make that format work: voting, accepted answers, a reputation system with privilege levels, tagging, full-text search with filters, revision history on every edit, and admin/moderator/user roles. Content is written in Markdown with real-time preview and code syntax highlighting. A plugin system covers OAuth login (Google, GitHub), S3 storage, external search backends like Algolia, and Akismet anti-spam, and a REST API exposes platform data for integration. The backend is Go, the frontend React, and it runs against SQLite, MySQL, or PostgreSQL. Self-hosting replaces per-seat tools like Stack Overflow for Teams with a flat-cost instance where you own all the content.

Large language models get a polished front end that can run fully offline: Open WebUI is the self-hosted front end of choice. It talks to local model runners, primarily Ollama, and to any OpenAI-compatible API, so LM Studio, vLLM, Groq, Mistral, OpenRouter, and cloud providers all plug into the same chat interface and can be mixed per conversation. RAG is built in: upload files to knowledge bases or reference them in chat with the # command, backed by a choice of nine vector databases (ChromaDB and PGVector officially maintained) and multiple extraction engines including Tika and Docling, with hybrid BM25-plus-vector search and cross-encoder reranking. Web search results from providers like SearXNG, Brave, and Tavily inject directly into conversations. Extensibility comes from Python tools and functions that run inside the chat, a Pipelines plugin framework, and native MCP support. Multi-user features include RBAC, SSO, and group permissions, and the instance itself exposes an OpenAI-compatible API your own apps can call.

Any existing relational database becomes a collaborative, Airtable-style smart spreadsheet under NocoDB. It connects to PostgreSQL, MySQL, MariaDB, SQL Server, or SQLite, introspects the schema - tables, relationships, indexes - and renders it as interactive Grid, Gallery, Kanban, Calendar, and Form views without migrating a single row. Your business data stays in your database; NocoDB keeps only its own metadata (view configs, permissions, webhooks) in a separate store. Every connected table automatically gets REST APIs with Swagger documentation, effectively turning legacy databases into modern backends. The spreadsheet layer adds 20+ field types including formulas, lookups, rollups, links, attachments, and currency, plus sorting, filtering, grouping, and multi-field editing. Views can be locked or shared publicly with password protection, role-based access control scopes permissions per user, and webhooks plus CSV, Excel, and Airtable import round out integration. An ERD view visualizes the schema. Built with Node.js and Vue, deployed via Docker, handling millions of rows.

Roughly $1M of development work, open-sourced: Maybe Finance began as a $249/year commercial personal finance product before the company released it all. It aggregates bank accounts, credit cards, loans, investments, crypto, and real estate into a single net worth dashboard with historical trend charts - replacing the spreadsheet that usually glues a whole portfolio together. Transactions are categorized and tagged with rules, with merchant tracking and search across imported or synced activity; budgets track spending by category against plan; and the investment view follows holdings, cost basis, and returns across brokerage accounts. Multi-currency support converts accounts held in different currencies into a single reporting currency, bank synchronization works through Plaid where supported, and manual CSV import covers any institution. An optional AI assistant answers questions grounded in your own financial data. Because the app was built as a paid product with professional design before being open-sourced, its interface quality exceeds most community finance tools - and self-hosting means your balances and transactions are not monetized by a free app or gated behind an annual subscription. The stack is Ruby on Rails with Hotwire on PostgreSQL, licensed AGPL-3.0 and deployed via Docker. The original repository is archived; development continues in the community fork Sure, compatible with the same self-hosted setup.

Perplexity's search experience without Perplexity: Vane deploys Perplexica, an open-source AI answer engine built as the self-hosted alternative. Instead of returning a page of links, it reads your question, searches the live web through the SearxNG metasearch engine, and composes a direct answer with cited sources. Retrieval quality comes from embeddings and similarity search: fetched pages are re-ranked against the query so the model answers from the most relevant passages rather than whatever ranked first. Two query modes cover different needs - Normal mode runs a straightforward web search, while Copilot mode generates multiple reformulated queries and actively pulls content from top matches for harder questions. Focus modes specialize retrieval for academic papers, YouTube, Reddit discussions, Wolfram Alpha calculations, or the general web. The answering model is your choice: OpenAI-compatible APIs or fully local LLMs such as Llama 3 and Mixtral through Ollama, which keeps queries entirely on your infrastructure. Because SearxNG pulls live results, answers reflect current information, and no search history is tracked.

Your own Heroku or Vercel on a single server - Dokploy is the open-source, self-hosted Platform-as-a-Service that makes the swap. You point it at a Git repository or a Docker image, and it builds and deploys the application using Dockerfiles, Nixpacks, or Heroku/Paketo buildpacks. Traefik is integrated as the reverse proxy, handling routing, load balancing, automatic Let's Encrypt SSL certificates, and HTTP/3. It also provisions and manages databases (MySQL, PostgreSQL, MongoDB, MariaDB, Redis) with automated backups to external storage. Complex multi-service applications deploy through native Docker Compose support, and multi-node scaling uses Docker Swarm. The web UI covers environment variables, volumes, resource limits, real-time CPU/memory/network monitoring, and deployment logs, with a CLI and API for automation. Deployment notifications go to Slack, Discord, Telegram, or email. One-click templates install common open-source tools, and a single Dokploy control plane can manage deployments across multiple remote servers. Because everything is standard Docker under the hood, there is no lock-in: your Dockerfiles, Compose files, and data volumes work anywhere else Docker runs. You get the Heroku-style push-to-deploy workflow without operating a Kubernetes cluster, and the total cost is the server it runs on - no per-app, per-environment, or per-seat platform fees regardless of how many applications you deploy.

An Airtable-style spreadsheet interface directly on PostgreSQL: Teable is an open-source no-code database where every table is a real Postgres table. Unlike tools that store records in a metadata abstraction layer, every Teable table is a real Postgres table with standard column types, so filtering, sorting, and grouping run at database speed, million-row tables answer complex filters in roughly 200 milliseconds without index tuning, and any PostgreSQL-compatible tool - psql, BI dashboards, ETL pipelines - can query the same data directly. The interface offers Grid, Kanban, Gallery, Calendar, and Form views as non-destructive overlays with their own filters and hidden fields, plus 20+ field types, formulas, comments, attachments, batch editing, undo/redo, and edit history. Collaboration is real-time with live cursors and instant sync across views, backed by Redis, and a REST API is auto-generated per table, largely compatible with Airtable API clients - alongside native SQL access for BI tools, analytics pipelines, and your own applications to JOIN and query directly, with no exports, API rate limits, or sync jobs. Global search spans all records, chart plugins handle quick visualization, and CSV and Excel import/export cover migrations. Where Airtable caps paid plans at 100K-500K rows and charges roughly $20 per user per month, a self-hosted Teable instance has neither limit: the Postgres database itself is the export if you ever leave. Built in TypeScript with NestJS, deployed via Docker with PostgreSQL and Redis, and licensed AGPL-3.0.

Typeform's conversational format, self-hosted: HeyForm is the open-source form builder that presents one question at a time. Forms present one question at a time, which measurably improves completion rates compared to long static pages. It supports 40+ field types, from text, email, and phone inputs to picture choices, date pickers, star ratings, signatures, and file uploads. Conditional logic shows or hides questions based on earlier answers, routes respondents to different endings, and redirects to URLs, so a single form can serve multiple flows. Completed submissions land in a results dashboard with drop-off and completion analytics, and connect outward through webhooks or integrations with Zapier, Make, Google Sheets, Notion, Airtable, and Slack. Theming covers fonts, colors, backgrounds, and custom CSS, so embedded forms look native to your site rather than like a third-party widget; the JavaScript embed library renders them inline, as popups, or full-page, with shareable standalone links as the default. Team workspaces and projects with member management let multiple teams share one instance without mixing data. Self-hosting removes per-response pricing entirely - unlimited forms and submissions for flat hosting cost - and keeps lead data, feedback, and quiz answers in your own MongoDB, simplifying GDPR compliance. The stack is a NestJS server and React webapp backed by MongoDB and KeyDB, distributed under GPLv3 as a Docker image.

Build, deploy, and monitor chatbots and LLM-powered agents on one open-source conversational AI platform: Botpress. Its Studio is a visual development environment: a drag-and-drop canvas arranges conversation logic with nodes for messages, questions, choices, and actions, while a built-in emulator simulates conversations for debugging before anything goes live. Agents ground their answers in a knowledge base assembled from uploaded documents, ingested websites, and past conversations via retrieval-augmented generation, and the LLM layer connects to multiple model providers - GPT-4, Claude, Mistral - with a configurable model strategy. An autonomous engine handles reasoning, tool orchestration, persistent memory across sessions, and sandboxed code execution, and custom code actions in TypeScript extend agents past prebuilt workflows. Over 100 integrations deploy the same bot to WhatsApp, Telegram, Slack, Microsoft Teams, and web chat, and connect it to HubSpot, Zendesk, Zapier, and arbitrary APIs and webhooks. Human handoff, conversation analytics, and quality monitoring cover production operation. Originating in 2017 from a Montreal team, the community edition is developed openly on GitHub.