# Install appwrite with Homebrew Command-line tool for Appwrite. Version 25.0.0 via Homebrew; verified 2026-08-01. ## Install ```sh sudo av install brew:appwrite ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install appwrite ``` Evidence: local Homebrew formula metadata ## Package facts - **Package key:** brew:appwrite - **Package manager:** Homebrew - **Version:** 25.0.0 - **Source summary:** Command-line tool for Appwrite - **Homepage:** - **Last updated:** 2026-08-01T11:59:29Z - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - appwrite (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 25.0.0 ## Project history and usage Appwrite CLI is the command-line companion to Appwrite, the backend-as-a-service platform. It packages Appwrite account, project, deployment, and Server API workflows into an installable terminal tool. ### Project history The CLI developed as an official Appwrite SDK surface rather than as a separate third-party wrapper. Appwrite's documentation describes it as an application for interacting with Appwrite from a terminal, including project/resource management, function deployment, and API operations. The modern CLI is distributed from the official appwrite/sdk-for-cli repository and is released both as npm package tooling and as standalone binaries. Recent releases show active work around Appwrite Cloud, OAuth/device login flows, generated command coverage, and deployment commands such as init, pull, push, and run. ### Adoption history The CLI is part of Appwrite's official developer workflow: the installation guide documents npm, Homebrew, shell installer, PowerShell, and Scoop paths. In package-manager culture it is notable because the Homebrew formula installs a cloud-platform CLI whose canonical use is project scaffolding and deployment rather than local daemon administration. The supplied package metadata records Homebrew packaging for the brew:appwrite formula. Appwrite's own docs also name Homebrew as an installation path, so the formula is not merely a community convenience; it is one of the documented upstream install methods. ### How it is used Typical use starts with appwrite login, then appwrite init project, which creates appwrite.config.json for project ID, endpoint, and deployable resources. The CLI can then pull or push functions, tables, teams, topics, buckets, and other project resources. For automation, the same executable doubles as a Server SDK-like command surface: Appwrite documents a command for every Server API endpoint and options for JSON output, verbose errors, force mode, and non-interactive operation. ### Why package nerds care For package nerds, Appwrite CLI is a good example of a SaaS platform shipping a first-party CLI through both language-package and OS-package channels. Its formula matters because teams can pin the same Appwrite deployment tool in laptop bootstrap scripts and CI images without pulling in a Node project dependency tree. The config split introduced in CLI 20.0.0 and later is also package-manager-relevant: the CLI's local appwrite.config.json becomes a declarative deployment manifest that lives with source code, much like Terraform files or Kubernetes manifests. ### Timeline - 2025: Appwrite CLI 20.0.0 and later support multi-file project configuration through appwrite.config.json includes. - 2026: Release 22.x continues active CLI development with OAuth, regional endpoint, and deployment workflow changes. ### Related projects - Appwrite server and Appwrite Cloud are the backend targets for the CLI. - The Appwrite Server SDKs are adjacent generated API clients; the CLI exposes similar server-side operations from a terminal. ### Sources - - - - source_facts.package-manager ## Security Notes No matching local secret-handling manifest was found for appwrite. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: appwrite.config.json - Windows: appwrite.config.json ## Credential files - Unix: ~/.appwrite - Windows: %USERPROFILE%\.appwrite ## Combined YAML source View the package source record on GitHub. [combined/appwrite.yml](https://github.com/mxcl/pkgdb/blob/main/combined/appwrite.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph