Changelog_

Users can now sign up and sign in with a passkey instead of a password, using Face ID, Touch ID, a fingerprint, or the device PIN. Turn on Passkey in your project's Auth settings and pick your app's domain. The same passkey works on your website and in your Android and iOS apps, and a passkey session also satisfies MFA.

Android apps sign in by their signing certificate: add the SHA-256 fingerprints of your keys to the Android platform.

Passkeys are available on Appwrite Cloud and in self-hosted Appwrite 2.5.

From Monday, October 19, 2026, cron schedules for functions on Appwrite Cloud will need a paid plan. Functions on the Free and Education plans run on an interval of 60 minutes or longer, and their existing cron schedules become intervals close to how often they run today. For example, */5 * * * * becomes every 60 minutes.

To keep cron, upgrade to a paid plan before October 19. To choose the interval yourself, select Interval in your function's Settings > Executions > Schedule, or replace schedule with interval in your SDK calls, CLI config, or Terraform resource.

Self-hosted Appwrite now has an official Helm chart. It installs the API, console, realtime, workers, and schedulers on your own Kubernetes cluster from oci://ghcr.io/appwrite/charts/appwrite, and runs Appwrite's data migration as part of helm upgrade.

A plain install includes built-in PostgreSQL, Redis, ClickHouse, and S3-compatible object storage, and runs Functions and Sites in the cluster, with builds as Kubernetes Jobs and the executor in a namespace of its own. For production, switch each service to a managed one on its own and route traffic through an ingress controller or the Gateway API. Chart 2.0.0 deploys Appwrite 2.5.0.

helm install appwrite oci://ghcr.io/appwrite/charts/appwrite \
  --namespace appwrite --create-namespace \
  -f values.yaml --wait --timeout 15m

Appwrite 2.5 is now available for self-hosting.

This release includes:

• Passkeys for your projects, enabled with a domain picked from your web platforms, and in Android apps by their signing certificate
• Interval schedules for functions, so a function can run every few minutes instead of on a cron expression, spread across the interval
• Function runtimes that no longer crash-loop after the executor restarts, with the executor moving to 1.1.2
• Batched usage writes, so the bundled ClickHouse does far less work under load
• An installer that keeps your docker-compose.override.yml, custom ports and HTTPS setting on upgrade, and binds ports to one interface such as 127.0.0.1:80
• Appwrite Console 1.2.74, with project passkeys, function intervals and Android signing certificates. Signing in to a self-hosted Console is now email and password only

See the migration guide to upgrade your instance.

For the complete list of updates and fixes, check out the release notes on GitHub.

Functions can now run on an interval as well as a cron expression. An interval works like cron where Appwrite picks the time for you: an hourly interval runs at the same point in every hour, such as 37 minutes and 21 seconds past, chosen for your function, so functions with the same interval no longer all start at the same moment.

• Interval: every N minutes, for work that needs to run regularly but not at an exact time.
• Cron: the times in a cron expression, for work tied to the clock, such as a report at 09:00 on Mondays.

Choose Interval in your function's Settings > Executions > Schedule, or pass interval (in minutes) to functions.create and functions.update in the latest Server SDKs and CLI (--interval). On Appwrite Cloud, intervals start at 1 minute on paid plans and 60 minutes on the Free and Education plans. Cron expressions are unchanged on every plan. Run times are fixed to the UTC clock, so the first run after you set an interval can be up to one full interval away.