Skip to content

Add version compatibility matrix to SDKs docs #2993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
atharvadeosthale wants to merge 3 commits into
base: main
Choose a base branch
from
+170 −0
Open

Add version compatibility matrix to SDKs docs #2993

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1d172a8
Add version compatibility matrix to SDKs docs
atharvadeosthale May 11, 2026
316ae3a
Verify SDK compatibility matrix against Appwrite specs
atharvadeosthale May 12, 2026
c19bbbc
Restore SDK matrix prose, keep only verified version updates
atharvadeosthale May 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
170 changes: 170 additions & 0 deletions src/routes/docs/sdks/+page.markdoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,6 +122,176 @@ Server libraries for integrating with Appwrite to build server side integrations

If you would like to help us extend our platforms and SDKs stack, you are more than welcome to contact us or contribute to the [Appwrite SDK Generator](https://github.com/appwrite/sdk-generator) project GitHub repository and read our contribution guide.

# Version compatibility {% #version-compatibility %}

The tables below map each released self-hosted Appwrite version to the SDK versions that were current at the time of that release. Use this to pin your SDK to a version known to work with your server. The latest stable self-hosted Appwrite release is `1.9.0`.

If you are running Appwrite Cloud, use the latest published SDK for your platform. Cloud rolls forward ahead of self-hosted releases.

## Client SDKs {% #client-compatibility %}

{% table %}
* Appwrite {% width=120 %}
* Web
* Flutter
* React Native
* Apple
* Android
---
* `1.7.0`
* `18.0.0`
* `16.0.0`
* `0.9.0`
* `10.0.0`
* `8.0.0`
---
* `1.7.1` to `1.7.3`
* `18.0.0`
* `16.0.0`
* `0.9.0`
* `10.0.0`
* `8.0.0`
---
* `1.7.4`
* `18.1.1`
* `17.0.0`
* `0.10.0`
* `10.0.0`
* `8.0.0`
---
* `1.8.0`
* `21.4.0`
* `20.3.0`
* `0.18.0`
* `13.3.0`
* `11.3.0`
---
* `1.7.5`
* `18.1.1`
* `17.0.0`
* `0.10.0`
* `10.0.0`
* `8.0.0`
---
* `1.8.1`
* `21.4.0`
* `20.3.0`
* `0.18.0`
* `13.3.0`
* `11.3.0`
---
* `1.9.0`
* `24.2.0`
* `23.0.0`
* `0.27.1`
* `16.0.0`
* `14.1.0`
{% /table %}

## Server SDKs {% #server-compatibility %}

{% table %}
* Appwrite {% width=120 %}
* Node.js
* Python
* PHP
* Dart
* Ruby
* .NET
* Go
* Swift
* Kotlin
* CLI
---
* `1.7.0`
* `17.0.0`
* `11.0.0`
* `15.0.0`
* `16.0.0`
* `16.0.0`
* `0.13.0`
* `v0.7.0`
* `10.0.0`
* `9.0.0`
* `6.2.3`
---
* `1.7.1` to `1.7.3`
* `17.0.0`
* `11.0.0`
* `15.0.0`
* `16.0.0`
* `16.0.0`
* `0.13.0`
* `v0.7.0`
* `10.0.0`
* `9.0.0`
* `6.2.3`
---
* `1.7.4`
* `17.1.0`
* `11.0.0`
* `15.0.0`
* `16.1.0`
* `16.0.0`
* `0.13.0`
* `v0.7.0`
* `10.0.0`
* `9.0.0`
* `12.0.1`
---
* `1.8.0`
* `20.2.1`
* `13.4.1`
* `17.5.0`
* `19.3.0`
* `19.3.0`
* `0.22.0`
* `v0.13.1`
* `13.2.2`
* `12.3.0`
* `12.0.1`
---
* `1.7.5`
* `17.1.0`
* `11.0.0`
* `15.0.0`
* `16.1.0`
* `16.0.0`
* `0.13.0`
* `v0.7.0`
* `10.0.0`
* `9.0.0`
* `12.0.1`
---
* `1.8.1`
* `20.3.0`
* `13.6.1`
* `18.0.1`
* `19.3.0`
* `19.3.0`
* `0.22.0`
* `v0.14.0`
* `13.3.0`
* `12.3.0`
* `17.2.1`
---
* `1.9.0`
* `22.0.0`
* `15.0.0`
* `20.0.0`
* `21.0.0`
* `21.0.0`
* `0.24.0`
* `v2.0.0`
* `15.0.0`
* `14.0.0`
* `17.3.0`
{% /table %}

The Rust SDK is available from Appwrite `1.8.1` onwards, pinned at `0.2.0` for both `1.8.1` and `1.9.0`.

Appwrite `1.7.5` was released as a backport patch on 2025-11-06, after `1.8.0` had shipped. The SDK versions in its row are the latest at that publish date and target the `1.8.x` line, so they may not be fully compatible with the `1.7.x` API. If you run a `1.7.x` self-hosted server, prefer the SDKs listed in the `1.7.4` row.
Copy link
Copy Markdown
Contributor

@greptile-apps greptile-apps Bot May 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Footnote claim contradicts the actual data in the 1.7.5 row

The footnote states "The SDK versions in its row are the latest at that publish date and target the 1.8.x line, so they may not be fully compatible with the 1.7.x API." However, the data in the 1.7.5 rows (both Client and Server tables) is identical to the 1.7.4 rows — pre-1.8.0 SDK versions — not the 1.8.x-era versions that appear in the 1.8.0 row. The PR description also says "its row reflects 1.8.x-targeted SDKs" which likewise does not match the tabulated data.

As a result, the closing advice — "prefer the SDKs listed in the 1.7.4 row" — is a no-op: both rows carry exactly the same pins. A reader trying to decide which SDKs to install for their 1.7.5 server will be told these versions may break compatibility, then discover the "safer" alternative is identical. Either the 1.7.5 matrix data should be updated to show the actual 1.8.x-era SDK versions that were current when 1.7.5 shipped, or the footnote text needs to be corrected to accurately describe what the row contains.


# Protocols {% #protocols %}
We are always looking to add new SDKs to our platform. If the SDK you are looking for is still missing, labeled as beta or experimental, or you simply do not want to integrate with an SDK, you can always integrate with Appwrite directly using any standard HTTP, GraphQL, or WebSocket clients and the relevant Appwrite protocol.

Expand Down
Loading