Appsmith Self-Hosted

Build internal applications with visual widgets, queries and JavaScript on customer-operated infrastructure.

7 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Appsmith 2.7.0 access and datasource hardening

The release adds missing app-access checks and extends restricted-host rules to S3-compatible and DynamoDB datasources.

Scope: Upstream Appsmith 2.7.0 release; Airgapped Edition packaging follows its separate update policy.

Applicability depends on custom JS-library access, fork permissions and configured datasource endpoints; no complete affected range is asserted.

Action: Review the security changes and Helm probe defaults before applying a compatible update.

Primary source · Reviewed 2026-11-17

What lands where

  1. Supplied by

    Vendor or project

    Docker Compose or Kubernetes; documented cloud VM/managed-container installation guides

  2. Operated by

    Your team

    Customer manages deployment, persistent databases, backups, networking and upgrades; confirm edition-specific vendor connectivity.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodDocker Compose or Kubernetes; documented cloud VM/managed-container installation guides
InfrastructureServers / containers
Classified as servers under this directory convention: the application is a long-running container/service. Official Fargate/Cloud Run paths reduce host management but retain application, database and persistence operations. For Helm upgrades, partial probe overrides now inherit new 10-second period and 5-second timeout defaults; invalid probe values fail installation or upgrade. Review custom probe settings before rollout.
Licensing modelOpen Source / Open Core
The broad self-hosted listing spans Apache-2.0 Community code and commercially licensed Enterprise functionality requiring an enterprise key. Match the selected image and plan to these terms.
LicenseApache-2.0 Community core; commercial edition and plan-dependent features

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

7 of 12 fields researched (58%) · 7 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

The self-hosting authentication guides document SAML and OIDC SSO as Enterprise features. SAML can migrate from the bundled Keycloak broker to native server handling starting in v2.7; configure the provider and migration for the selected release.

Self-hosted Enterprise user login; Google/GitHub login and enterprise federation are different options · Source ↗ · Enterprise OIDC SSO ↗ · Reviewed 2026-11-20

Edition-dependent · Editor reviewed.

SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning

Self-hosted Enterprise documents SCIM v2 user and group provisioning. The identity provider must reach the instance SCIM endpoint over HTTPS.

Self-hosted Enterprise; identity-provider and network requirements apply · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation

A separate Airgapped Edition is obtained through sales. Offline operation limits templates, SaaS integrations and third-party libraries; disabling telemetry alone is not air-gapped deployment.

Separately arranged Airgapped Edition, not every Appsmith installation · Source ↗ · Reviewed 2026-11-14

Edition-dependent · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official Docker guide supplies run and Compose configurations using an Appsmith image and persistent /appsmith-stacks storage. Choose the Community or commercial image deliberately, pin the intended release and configure the host, secrets, HTTPS and backups.

Official all-in-one installation example; choose the edition and a compatible pinned container release · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The all-in-one Docker installation guidance calls for at least 8 GB host RAM because supporting services run inside the container. Externalized services require a different capacity plan.

All-in-one Docker host; not a universal per-application requirement · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The v2.7.0 core is Apache-2.0. The vendor distinguishes free Community from paid Business and Enterprise plans; SAML/OIDC, provisioning and air-gapped add-ons have separate commercial entitlements. Confirm self-hosted feature, user and support terms with the vendor.

Versioned core versus commercially licensed features; displayed Cloud limits and prices are not applied as a self-hosted quote · Source ↗ · Edition and feature pricing ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The Airgapped Edition documentation specifies quarterly packaged updates transferred manually into the isolated environment. This is separate from the normal upstream release stream.

Airgapped Edition update policy; not the cadence of all Appsmith editions · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Show all fields (5 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Community and commercial images differ. Documentation requires outbound HTTPS to cs.appsmith.com for self-hosted license/template services and describes separate air-gapped arrangements. Official setup guides name AWS, Azure and Google Cloud. Fargate and Cloud Run are long-running container hosting options, not evidence that the entire stack is function-based. Appsmith v2.7.0 fixes app and datasource authorization issues, extends restricted-host enforcement to S3-compatible and DynamoDB sources, and updates vulnerable dependencies.

Category fit

Internal tools
Low-code development of dashboards, admin panels and internal apps connected to databases/APIs; not a turnkey business application.

Compare within Internal tools

  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Budibase Self-HostedBuild operational apps and automations on customer-hosted infrastructure.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
    • AWS
    • Azure
    Customer-operated · Commercial Only
  • CortezaLow-code platform for business records, workflows and configurable CRM applications.
    • Hostinger
    Customer-operated · Open Source / Open Core
  • Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Grist Self-HostedRelational spreadsheet platform for collaborative business data and configurable operational applications.
    • AWS
    • Azure
    Customer-operated · Open Source / Open Core
  • Mendix on KubernetesCommercial low-code application runtime operated in customer Kubernetes infrastructure.
    • AWS
    • Azure
    • Google Cloud
    • STACKIT
    Customer-operated · vendor control plane · Commercial Only
  • NocoDB Self-HostedSpreadsheet-style database platform with linked records, views and optional licensed internal app interfaces.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Railway
    Customer-operated · Source Available

Showing 8 of 10 other listings in Internal tools. These products address related workflows; read their category-fit notes before comparing scope. See all of Internal tools →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Appsmith provider-specific installation index ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor documents AWS AMI and ECS, Azure Container Instances and Google Cloud Run installation of the application. These are self-hosted installations, with edition-specific licensing and vendor connectivity requirements described separately.

    • Appsmith on a customer DigitalOcean Droplet ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.

      The vendor walks through choosing the Appsmith Marketplace image, creating a Droplet in the customer account and registering its application administrator. Free and licensed features have separate entitlements; configure domain, TLS, email and recovery for production.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory