EOL.WikiEOL.Wiki
← ← Back to all products

Appwrite

Active
Server SoftwareLatest Version: 1.9.0Latest Release: Apr 1, 2026

Appwrite is an open-source backend-as-a-service platform providing auth, databases, storage, and functions.

Support summary

Appwrite currently has supported cycles. Track the next EOL date and validate upgrades before your change window.

What do EOL and support statuses mean?

Next EOL

No announced EOL date is currently listed.

Supported cycles

10

0 lts

Versions

10

Latest Version

1.9.0

Active Support

10

EOL

0

Lifecycle Timeline

Today
1.9
1.9
1.8
1.8
1.7
1.7
1.6
1.6
1.5
1.5
1.4
1.4
1.3
1.3
1.2
1.2
1.1
1.1
1.0
1.0
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
1.9Apr 1, 2026YesNo1.9.0No
Active
1.8Oct 21, 2025YesNo1.8.1No
Active
1.7May 18, 2025YesNo1.7.5No
Active
1.6Sep 18, 2024NoNo1.6.2No
Active
1.5Mar 8, 2024NoNo1.5.11No
Active
1.4Aug 30, 2023NoNo1.4.14No
Active
1.3Apr 12, 2023NoNo1.3.8No
Active
1.2Dec 27, 2022NoNo1.2.1No
Active
1.1Nov 16, 2022NoNo1.1.2No
Active
1.0Sep 14, 2022NoNo1.0.3No
Active

Data sources

Last verified

Jun 24, 2026

Community-maintained lifecycle data. Verify against official release notes before production migration.

Frequently Asked Questions

Is it safe to continue using Appwrite 1.0?
Appwrite 1.0 is currently supported and receiving updates. You can continue using it safely until its end-of-life date.
What is the latest version of Appwrite?
The latest version of Appwrite is 1.9.0, released in the 1.9 release cycle.
How many versions of Appwrite are currently supported?
Appwrite currently has 10 actively supported version(s): 1.9, 1.8, 1.7, 1.6, 1.5, 1.4, 1.3, 1.2, 1.1, 1.0.
When does Appwrite 1.9 reach end of life?
Appwrite 1.9 does not have a specific end-of-life date announced yet.
What should I do when Appwrite reaches end of life?
When a Appwrite version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.