Appwrite Self-Hosted
Self-hosted backend services for authentication, databases, storage, functions and messaging.
12 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Appwrite container security maintenance
Appwrite 2.7.3 refreshes its base and executor images after the 2.7.2 security update.
Scope: Self-hosted Appwrite 2.7.3, appwrite/base 2.2.12 and openruntimes/executor 1.3.5; not Appwrite Cloud.
Container dependency findings depend on the actual deployed images. The release is not proof that every image or integration is vulnerability-free.
Action: Back up and use the normal upgrade/migrate procedure; the release says moving from 2.7.2 introduces no schema changes.
Primary source · Reviewed 2026-11-17
What lands where
Supplied by
Vendor or project
Docker installer or official Kubernetes Helm chart
Runs in
Documented customer environment
Customer-operated container services, database and storage
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- DigitalOcean: Customer cloud account
- AWS
- Azure
- Google Cloud
- DigitalOcean
Servers / containers
Operated by
Your team
Customer configures the environment and handles software updates, scaling, security and backups.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Appwrite self-hosting on AWS ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Appwrite self-hosting on Azure ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Appwrite self-hosting on google-cloud ↗ · Source checked 2026-11-12
- DigitalOcean: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Appwrite self-hosting on digitalocean ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Docker installer or official Kubernetes Helm chart |
|---|---|
| Infrastructure | Servers / containers Appwrite runs as persistent Docker services or an official Helm deployment on Kubernetes. The function feature does not make the complete backend a serverless deployment. |
| Licensing model | Open Source / Open Core This classification covers the public Appwrite self-hosted distribution under BSD-3-Clause. Appwrite separately markets a premium enterprise self-hosted edition; its additional tooling and terms are outside this classification and should not be assumed to inherit the public core license. |
| License | BSD-3-Clause core; enterprise services and feature terms should be confirmed separately |
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.
5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
Appwrite documents OAuth2 identity providers for users of applications you build. Separately, the vendor advertises centralized Console SSO in its premium Enterprise platform, available as self-hosted or Cloud. Do not treat core application-user OAuth as administrator SAML: confirm the chosen self-hosted Enterprise package, IdP/protocol and organization policy for Console SSO.
Application-user OAuth versus premium self-hosted Console identity; product/edition boundaries apply · Source ↗ · Application-user OAuth2 flow and provider setup ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The official installer generates a Compose stack and environment/configuration files. Replace encryption/executor secrets, retain all required files and select the worker/database configuration; a Kubernetes Helm option is separate.
Upstream self-hosted deployment; not a provider support or production-readiness certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The current installation guide requires at least 2 CPU cores, 4 GB RAM and 2 GB swap on a Docker-capable host. Models, functions, worker topology and workload can raise requirements.
Appwrite installation baseline; not every production workload · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The reviewed upstream application uses BSD 3-Clause licence. Review the licence and bundled-component notices for your use and distribution. Hosting, databases, delivery services, commercial support and any separately licensed additions have their own costs and terms; no hosted-plan price is treated as a self-hosted quote.
Appwrite 2.7.3 upstream core; not Cloud or Enterprise entitlements; software terms only, excluding infrastructure and operations · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The reviewed upstream release is 2.7.3, published 2026-11-17. This is a dated release snapshot, not a support designation, a future cadence promise or approval to replace a provider package.
Upstream appwrite/appwrite release record; commercial editions, LTS branches and provider packages can differ · Source ↗ · Reviewed 2026-11-17
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
Scope & considerations
This entry covers self-hosting rather than Appwrite Cloud. Official deployment guides document EC2/EKS, Azure VMs/AKS and Google Compute Engine/GKE. Configure external email, SMS and other integrations deliberately; enterprise support and compliance offerings have separate terms. Appwrite 2.7.3 includes the 2.7.2 security fixes across authentication, abuse limits, storage, realtime, messaging, functions, VCS, proxy handling, and vulnerable base-image packages. It additionally rebuilds appwrite/base and openruntimes/executor to clear remaining image vulnerability findings. Upgrading from 2.7.2 requires no schema changes; use the normal upgrade command and migration step.
Category fit
- Backend platforms
- Application backend APIs for authentication, databases, storage, functions, messaging and realtime, deployed on customer infrastructure.
Compare within Backend platforms
- Gravitee API Management Self-HostedOpen-source and commercial self-hosted API management platform with documented EKS, AKS and GKE deployment paths.
- AWS
- Azure
- Google Cloud
- HashiCorp Consul EnterpriseCommercial service networking, discovery and service-mesh platform deployed into customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- Hasura GraphQL Engine v2GraphQL API engine that exposes connected databases through permission-aware application APIs.
- Azure
- Google Cloud
- KeystoneJS (Keystone 6)Self-hosted content backend with a configurable GraphQL API and administration interface.
- Northflank
- Kong Gateway Self-ManagedOpen-source and commercial self-managed API gateway with supported AWS, Azure and Google Cloud deployment platforms.
- AWS
- Azure
- Google Cloud
- Medplum Self-HostedOpen-source FHIR healthcare backend, clinical application and automation platform deployed in customer cloud infrastructure.
- AWS
- Azure
- Google Cloud
- Parse ServerNode.js application backend for data APIs, users, permissions and server-side application logic.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Heroku
- Red Hat OpenShift Container PlatformCommercial self-managed Kubernetes application platform installed and operated in customer cloud accounts.
- AWS
- Azure
- Google Cloud
- Alibaba Cloud
- IBM Cloud
Showing 8 of 11 other listings in Backend platforms. These products address related workflows; read their category-fit notes before comparing scope. See all of Backend platforms →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Backend capabilities ↗appwrite.io
- Self-hosting responsibilities ↗appwrite.io
- Docker installation ↗appwrite.io
- AWS deployment ↗appwrite.io
- Azure deployment ↗appwrite.io
- Google Cloud deployment ↗appwrite.io
- Core license ↗raw.githubusercontent.com
- Licensing and edition terms ↗appwrite.io
- Infrastructure deployment documentation ↗appwrite.io
- Appwrite self-hosting on digitalocean ↗appwrite.io
- Appwrite 2.7.2 security patch ↗github.com
- Appwrite 2.7.3 image security update ↗github.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Appwrite self-hosting on AWS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
- Appwrite self-hosting on Azure ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
- Appwrite self-hosting on google-cloud ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
- Appwrite self-hosting on digitalocean ↗ · DigitalOcean
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The upstream guide provisions the application in the customer cloud environment and follows the self-hosted installation workflow. This covers Appwrite server deployment, not merely an SDK integration or the vendor-operated Appwrite Cloud; maintain the compatible server version, persistent data and backups.
- Appwrite self-hosting on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked