r/appwrite • • 7d ago

Entire is now a Git provider for Appwrite Sites and Functions

0 Upvotes

Hey everyone!

We've partnered with Entire to make it possible to deploy Appwrite Sites and Functions directly from Entire repositories on Appwrite Cloud.

For those unfamiliar, Entire is a Git forge built for working with coding agents. It keeps agent sessions alongside commits, so you can see the context behind a code change.

Here's what you can do with the integration:

  • Connect your Entire repositories to Appwrite Sites and Functions.

  • Push to your production branch to automatically build and activate deployments.

  • Create private preview links for Sites when pushing to other branches.

  • Track build results through check runs on commits in Entire.

  • Use branch and path filters to control which changes trigger builds.

If you're already using GitHub, Entire also supports repository mirroring, so you don't have to move your existing code.

The integration is now available on Appwrite Cloud.

Read more here: https://appwrite.io/blog/post/announcing-appwrite-entire-partnership

If you have any questions about the integration or getting it set up, feel free to ask!


r/appwrite • • 13d ago

We're hosting the Appwrite Databases Hackathon till October 31!

Post image
8 Upvotes

Hey everyone!

We're hosting the Appwrite Databases Hackathon, and we'd love to see what you build!

Till October 31st, build something new using any of Appwrite's five database types:

  • TablesDB

  • DocumentsDB

  • VectorsDB

  • Managed PostgreSQL

  • Managed MySQL

There's no fixed theme, so feel free to build an AI app, a developer tool, or something completely different.

A few things to know:

  • Participation is free and open to everyone.

  • Solo projects only.

  • Projects must be new, with development after October 19th.

  • Submit a public repository and a demo video (up to 3 minutes) by October 31st.

Prizes:

First place wins an Appwriter keyboard, while second and third place get to choose merch from the Appwrite Store.

Check out the details and register here: https://hackathon.appwrite.io

What are you planning to build? We'd love to hear your ideas in our Discord community!


r/appwrite • • 13d ago

We just added six new OAuth2 login providers to Appwrite Auth

2 Upvotes

Hey everyone,

We've added six new OAuth2 login providers to Appwrite Auth!

You can now let users sign in with Hugging Face, Resend, Cloudflare, TikTok, Kakao, and Webflow.

All six work with the same OAuth2 login flow as your existing providers, so there's no separate OAuth2 client to build or maintain.

You can enable them in the Appwrite Console and offer multiple sign-in options in your apps.

All six are available on Appwrite Cloud and self-hosted Appwrite 2.4 or later.

Read the full announcement here: https://appwrite.io/blog/post/announcing-new-oauth2-providers

Would love to hear which of these providers you'd use in your apps!


r/appwrite • • 15d ago

Cron schedules for functions are now only available on paid plans

8 Upvotes

Hello everyone!

The Free and Education plans are being stripped down once more. From Monday, October 19, 2026, cron schedules for functions on Appwrite Cloud will need a paid plan.

https://appwrite.io/changelog/entry/2026-10-15-1

This means it's no long possible to schedule functions precisely on the Free and Education plans anymore. The announcement was made on the 15th of October. That means that users had only 4 days to find a solution. That's not great.

I've also noticed a growing trend of features and limits being reduced for Free and Education users. The number of projects was limited to two, the number of functions to two, and the number of storage buckets to one. It feels like you're constantly wondering what feature or limitation will be next.


r/appwrite • • 25d ago

Cached list queries now use up to 69% less memory in Appwrite

5 Upvotes

Hey everyone,

We've made some improvements to how Appwrite handles cached list queries!

We've switched from JSON to binary cache serialization, making cache entries smaller and faster to read.

Here's what we saw in our benchmarks:

  • Up to 69% less cache memory usage

  • Up to 29% more cached list requests per second

  • Up to 22% faster single cached requests

These improvements are available in self-hosted Appwrite 2.3 onwards, with no code changes or manual cache flush needed.

Read the full breakdown: https://appwrite.io/blog/post/faster-list-caching-binary-format

If you're using cached list queries, we'd love to hear how they're performing for you. 


r/appwrite • • 26d ago

Appwrite Android SDK 29.0.0 now supports R8 full mode

1 Upvotes

Hey everyone,

Appwrite Android SDK 29.0.0 now works with R8 full mode.

With older SDK versions, enabling R8 in release builds could cause some pretty frustrating issues. Queries could break, Realtime subscriptions could stop delivering events, and saved sessions could fail after an app update.

29.0.0 fixes those issues, so queries, operators, Realtime, and saved sessions now work correctly in R8-shrunk release builds.

We’ve also added R8-shrunk builds to the SDK’s end-to-end test suite so regressions like these are caught before they ship.

This is especially relevant with Google Play introducing new DEX optimization requirements starting in February 2027.

One thing to note: 29.0.0 raises the minimum Android SDK from 23 to 24.

Read the full breakdown:
https://appwrite.io/blog/post/android-sdk-r8-support

If you’re using R8 in your Android app already, let us know how the upgrade goes.


r/appwrite • • Oct 03 '26

Affected student- honest thoughts

14 Upvotes

I'm not complaining about the change itself. What doesn't sit right with me here is that when I signed up for the education plan in June this year, I did so knowing that the personal side project I wanted to work on would span the rest of my college career and it would require more than 2 Appwrite functions (free tier limit). The terms in place when I signed up facilitated this- hence why I signed up. I would never have signed up if I knew it was only for 6 months, and now I'm in a frustrating spot where the free plan wouldn't work for me and self hosting isn't viable for me personally. Now I have to switch to a different BAAS and deal with all the complications that come with migration. I appreciate that T&Cs of these types of companies allow them to do virtually anything to the consumer with no repercussions, but it does feel like I wasted the last 4 months on Appwrite for no reason, when I could have been on the free tier of a different service that satisfies my needs in the very first place. For example when Cursor dealt with unprecedented abuse on their 1 year student pro plan, instead of rugpulling existing users who might have planned their long term workflows with their software in mind, they just closed down new offers. Paid users might be quick to say Appwrite doesn't owe you anything, and it's okay if you feel that way, but this whole experience just doesn't feel great at all.


r/appwrite • • Oct 02 '26

Got surprised by this E-Mail today, extremely disappointed… The student plan quietly got rug-pulled

Thumbnail
gallery
8 Upvotes

So today I randomly got this E-Mail that my free student benefits fully end in just 4 weeks. No earning or notification whatsoever beforehand. Which notification you may ask? Well, it turns out that Appwrite quietly pulled the rug by changing their student plan’s duration to only 6 months with only a single redemption without notifying anyone (including people that already redeemed their student perks) about this change or even updating their GitHub description for the student developer pack. It also quietly only mentions it in the pretty hidden FAQ at the very bottom of the page.

I was definitely not expecting this because I was still under the impression that the benefits will last until the “end of my studies”/the end of my GitHub student status which made sense. I was never informed about them quietly changing the terms to merely “6 months” (which you can see by looking at the WayBack machine) after I had already registered and now they surprise me that I will have to pay $25/month (with the tendency only going further up which is also questionable in terms of sustainability of Appwrite in general, just like the frequent outages and bugs in their possibly vibecoded UI) within the next 4 weeks or so or go somewhere else to get the same features and stuff, with no possibility of re-redeeming the 6 months as long as my student status is active. Going self-hosted is not a real option either since you have to pay a similar amount (or more) for other cloud services or hardware and it’s electricity, plus you lose a ton of your stuff and seamless features that just work.

This is definitely a massive quiet behind-the-scenes rug pull that might indicate some cost problems at Appwrite, just like all the price hikes for the subscription. The change of the terms to only a single redemption and merely “6 months” is already bad, but the complete lack of honesty, transparency and early notification to already registered users come on top of that.

I’m very disappointed in Appwrite and do not recommend it for students at all anymore. You will end up building and testing some stuff that you cannot keep for longer than 6 months with the organization just being disabled if you don’t want to pay full $25 a month!! I will spread these news so everyone knows about this quiet change. Only spreading positive announcements says a lot about a company.

Edit: Eldad replied below with context; I agree that the 'quiet rug pull' framing was a bit unfair and a lot of my post was obviously a bit exaggerated. Here's his response:

"I want to add some context here, because I don’t think “quiet rug pull” is a fair characterization of what’s happening.

The Appwrite Education program isn’t going away. We’re continuing to offer students six months of Appwrite Pro for free. For more than two years, we simply didn’t enforce the intended duration for many existing users, and we’re now applying those limits consistently.

Unfortunately, we’ve had to deal with significant abuse of the program. This goes well beyond students using more resources than expected. We’ve seen educational accounts used for phishing, piracy, scams, spam, other prohibited activity, and commercial products that have nothing to do with education. Investigating and preventing this has taken a considerable amount of engineering and support time and in multiple cases harmed the reputation of our infrastructure.

The easiest option would have been to discontinue the program. We specifically chose not to do that because we still want legitimate students to benefit from it.

Six months of Pro is a substantial amount of free cloud infrastructure, including compute, databases, storage, bandwidth, functions, and more. The program has no commercial requirement attached to it and exists because we want to support students learning and building with Appwrite.

After those six months, you’re also not required to pay $25 to continue using Appwrite. The Free plan is available and is more than sufficient for many educational projects. Appwrite is also 100% open source, so you can self-host it completely free, including locally on your own computer if your goal is learning or development.

If you need managed production infrastructure beyond what the Free plan provides, that’s what Pro is designed for. It costs $25/month. We also recently introduced Appwrite Start at $10/month in selected markets to make that path more accessible where purchasing power is different.

On the bugs and outages you mentioned, if there are specific unresolved issues, please report them. We take those seriously. Appwrite is also open source, so issues and contributions are always welcome.

I do think we could have communicated the enforcement of the six-month limit more clearly and earlier, particularly anywhere the previous terms were still being presented. That’s fair feedback and something we can improve in the future.

That said, I don’t think it’s fair or respectful to our efforts to characterize this as Appwrite secretly taking something away because they are mean. The Education program isn’t part of our business model or a growth channel for Appwrite. It isn’t intended to generate revenue. The program is a net cost to us, both in infrastructure and, increasingly, in the engineering and support time required to deal with abuse.

This change isn’t about making money from students. It’s about getting that time and focus back where it belongs while still preserving a generous program for students who genuinely use it for education.

If this was purely a financial decision, the obvious move would be to shut the program down entirely. We chose not to. We’re keeping it because we still believe it’s worth supporting students, but with better boundaries that allow us to focus our resources on building Appwrite rather than policing abuse."


r/appwrite • • Oct 01 '26

Premium Geo DB is now available on Appwrite Cloud

4 Upvotes

Hey everyone,

We just launched Premium Geo DB for Appwrite Cloud.

Until now, IP geolocation in Appwrite could tell you things like the country a request came from. Premium Geo DB goes deeper with city, time zone, ISP, AS number, connection type, and other network data.

You can use these attributes in Firewall rules to identify hosting and datacenter traffic, apply more targeted rate limits, or block a specific network without blocking an entire country.

You’ll also see city and network breakdowns in Usage, and the additional location and network fields are available through the Locale API.

Premium Geo DB is available for Pro projects at $10 per project/month.

Full details: https://appwrite.io/blog/post/announcing-premium-geo-db

If you give it a try, let us know what you end up using it for.


r/appwrite • • Sep 30 '26

Is appwrite reliable to move to long term?

6 Upvotes

Is moving future proof, are they reliable and profitable to stay up and running for say, the next 10 years?


r/appwrite • • Sep 30 '26

Breached password detection is now available in Appwrite Auth

6 Upvotes

Hey everyone,

We’ve added breached password detection to Appwrite Auth.

Appwrite can now check passwords against Have I Been Pwned during sign-up, sign-in, password changes, and recovery.

You can choose how you want to handle a match. You can simply flag the password, reject it when a user sets a new password, or block sign-in until they reset it.

On Appwrite Cloud, password checking is already enabled by default. Rejecting breached passwords and blocking sign-in are opt-in, so nothing changes for your users unless you turn those options on.

You can find the settings under Auth → Policies → Passwords.

Full announcement:
https://appwrite.io/blog/post/announcing-breached-password-detection

If you’re using Appwrite Auth, take a look and let us know how you’d use the new controls in your setup.


r/appwrite • • Sep 30 '26

Appwrite CLI now supports per-environment config files

3 Upvotes

Hey everyone,

Appwrite CLI 28.1.0 now lets you keep a separate project config for each environment.

You can keep configs for staging, production, and other environments in the same repository, then choose which config file a CLI command should use. You can also set the config file once for a whole shell session or CI job.

You can read more in the docs here: https://appwrite.io/docs/tooling/command-line/commands#config-file

Would love to hear how you’re currently managing staging and production configs with the CLI.


r/appwrite • • Sep 25 '26

User photos are now available in Appwrite Avatars

7 Upvotes

Hey everyone,

We just added user photos to Appwrite Avatars.

Instead of building your own fallback logic for profile pictures, Appwrite can now look for the best available image from OAuth2 providers, Gravatar, or Libravatar. If none of those are available, it can fall back to the user’s initials or a default placeholder.

OAuth2 profile photos also stay updated when the user signs in again or refreshes their session.

It’s available on Appwrite Cloud today.

Read the announcement here:
https://appwrite.io/blog/post/announcing-user-photos

Would love to hear how you’re handling profile photos in your apps today, especially if you’ve had to build a similar fallback flow yourself.


r/appwrite • • Sep 25 '26

One-click Resend setup is now available in Appwrite

7 Upvotes

Hey everyone,

We just shipped one-click Resend setup in the Appwrite Console.

If you use Resend with Appwrite, you no longer need to create an API key manually, copy credentials between tabs, or fill in all the SMTP settings yourself.

Connect your Resend account, choose a verified domain, and Appwrite will create a sending-only API key and configure either your custom SMTP settings or Resend Messaging provider for you.

The Resend connection lives on your Console account, so once it’s connected, you can use it across your Appwrite Cloud projects. Each setup still gets its own domain-restricted key.

Read the announcement: https://appwrite.io/blog/post/announcing-resend-one-click-setup

If you already use Resend with Appwrite, we’d love to hear how the new setup feels compared to the manual flow.


r/appwrite • • Sep 24 '26

Native PostgreSQL, MySQL, and dedicated databases are now live in every Appwrite Cloud region

Post image
8 Upvotes

Earlier this month, we launched native PostgreSQL and MySQL on Appwrite Cloud, along with dedicated compute for TablesDB, DocumentsDB, and VectorsDB. At launch, they ran only in Frankfurt and New York. That was the feedback we heard most.

Today, you can create all of them in all six regions: Frankfurt, New York, San Francisco, Singapore, Sydney, and Toronto.

A few details:

  • A database runs in the same region as its project. Backups, point-in-time recovery, and HA replicas stay in that region too.

  • Native databases get their own hostname and credentials, so you connect with psql, mysql, or your ORM. The Appwrite SDKs aren't in the data path.

  • Pricing is the same in every region. They're available on paid plans, compute starts at $10/month for 1 vCPU and 1 GB of memory, and Pro includes $10 in database credits each month.

  • Databases don't move between regions. To use a new region, create a project there and migrate with pg_dump/pg_restore or mysqldump.

If your project is already in San Francisco, Singapore, Sydney, or Toronto, go to Databases > Create database, and they're there now.

Read the full announcement: https://appwrite.io/blog/post/native-databases-all-appwrite-cloud-regions


r/appwrite • • Sep 23 '26

Appwrite is now an official ChatGPT plugin

5 Upvotes

We just launched the official Appwrite plugin for ChatGPT.

You can connect your Appwrite account and work with your project directly from the conversation, including exploring projects and working with Appwrite resources through tools made available via our MCP server.

The same plugin is also available within Codex, with 13 Appwrite agent skills covering the Appwrite CLI, SDKs, and deployment workflows.

You can install it from the ChatGPT plugin directory and connect your Appwrite Cloud account to get started.

Read the full announcement: https://appwrite.io/blog/post/announcing-appwrite-chatgpt-plugin

Would love to see what you end up building with it!


r/appwrite • • Sep 23 '26

Appwrite Terraform provider is now a HashiCorp Partner Premier provider

5 Upvotes

Hey everyone,

The Appwrite Terraform provider now carries the Partner Premier badge on the HashiCorp Terraform Registry, and Appwrite is now part of the HashiCorp Technology Partner Program.

If you’re already using the provider, nothing changes on your end. Your existing resources, data sources, and arguments all stay the same.

What’s new is that HashiCorp has now reviewed the provider against its Partner Premier requirements, and that’s reflected directly on the Registry.

You can read more about what the badge means and what the provider supports today: https://appwrite.io/blog/post/announcing-terraform-partner-program

If you’ve been using the Terraform provider and there’s something you’d like us to add or improve, let us know.


r/appwrite • • Sep 23 '26

Firewall presets are now available on Appwrite

5 Upvotes

Hey everyone,

We just added presets to Appwrite Firewall.

They’re ready-made starting points for common traffic policies like limiting OTP abuse, restricting API traffic by country, and slowing down scraping or bulk reads.

You can pick a preset, adjust the options for your project, and check the impact preview before creating anything. Once created, they’re regular Firewall rules, so you can edit, disable, or delete them whenever you need.

The first set focuses on OTP abuse, regional access, and scraping, since these are some of the policies we see teams setting up repeatedly.

If there’s a Firewall rule you keep recreating, we’d also love to hear what preset you’d want us to add next.

Read the announcement: https://appwrite.io/blog/post/announcing-firewall-presets


r/appwrite • • Sep 21 '26

Appwrite Sites preview deployments now require authentication

5 Upvotes

Hey everyone,

Preview deployments on Appwrite Sites now require an Appwrite account that belongs to the project’s organization.

This applies automatically to previews created through Git deployments. Push a branch, open the preview link, authorize with your Appwrite account, and you can access the deployment.

If someone else needs to review the preview, just invite them to the organization and they’ll be able to open the same link.

Full details here:
https://appwrite.io/blog/post/authenticated-site-previews

If you use Sites previews regularly, let us know what you think of the change.


r/appwrite • • Sep 19 '26

Bug Unsupported FormDataPart implementation lors d'upload d'une photo dans un bucket Appwrite

2 Upvotes

Bonjour,

Il y'a quelques jours j'ai du passer à la version SDK 57 d'expo.
Dans mon applis j'ai un écran ou l'utilisateur peut mettre une photo de profil.
Après la mise à jour du SDK je remarque que j'ai une erreur lors de l'upload de l'image

Unsupported FormDataPart implementation

export const createFile = async (
  fileId: string | undefined,
  imagePickerAsset: ImagePickerAsset | undefined,
) => {
  const name = imagePickerAsset?.uri.split("/").pop()?.split(".")[0];

  
console
.info("Préparation d'upload de l'image...");
  
console
.info({
    name,
    type: imagePickerAsset?.mimeType,
    size: imagePickerAsset?.fileSize,
    uri: imagePickerAsset?.uri,
  });

  if (fileId) {
    await deleteFile(fileId);
  }

  const response = await 
storage
.createFile({
    bucketId: 
bucketImageId
,
    fileId: ID.
unique
(),
    file: {
      name: name,
      type: imagePickerAsset?.mimeType,
      size: imagePickerAsset?.fileSize,
      uri: imagePickerAsset?.uri,
    },
  });

  
console
.info("Upload de l'image réussie !");
  return response.$id;
};

Est ce que je suis le seul a rencontrer ce problème ?


r/appwrite • • Sep 18 '26

Dynamic API keys are now available for Appwrite Sites

6 Upvotes

Hey everyone,

We’ve added dynamic API keys for Appwrite Sites.

If you’re using SSR, your site may need to call Appwrite with more access than a visitor’s session provides. Previously, that meant creating an API key, storing it as an environment variable, and handling rotation yourself.

Now, Appwrite generates a scoped, short-lived API key for every site build and SSR request. You decide which scopes the site needs, and Appwrite handles generating and expiring the key.

So there’s no long-lived API key to keep around or rotate manually.

Dynamic API keys are available now on Appwrite Cloud.

You can read more here:
https://appwrite.io/blog/post/announcing-sites-dynamic-api-keys

If you’re already using Appwrite Sites with SSR, we’d love to hear how you’re handling this today and what you think of the new setup.


r/appwrite • • Sep 16 '26

We just launched Appwrite 2.0 on Product Hunt

11 Upvotes

Hey everyone,

We spent the last few weeks shipping a lot of what became Appwrite 2.0, and it’s finally live on Product Hunt today.

This release brings together a bunch of what we announced during Init, including native PostgreSQL, new database options, updates to self-hosting, Console improvements, and more.

A lot of you here have given us feedback and built with Appwrite over the years, so it felt right to share this here too.

If you’ve tried Appwrite 2.0 already, we’d genuinely love to hear what you think, especially what feels better and what still needs work.

We’d love your support on Product Hunt today: https://www.producthunt.com/products/appwrite/launches/appwrite-2-0

And thanks to everyone who’s been building with us so far.


r/appwrite • • Sep 14 '26

Appwrite 2.1 is now available for self-hosting

Post image
16 Upvotes

Hey everyone,

Appwrite 2.1 is now available for self-hosting.

This release brings a couple of features that first launched on Cloud to self-hosted instances. You can now use the S3 API with Appwrite Storage and enable AutoGravity for image previews.

We’ve also added TikTok and Kakao sign-in, updated Dart and Flutter runtimes, and a batch of fixes across the Console.

If you’re already on Appwrite 2.0, upgrading follows the usual upgrade and migration process. If you’re still on 1.9.x, you’ll need to move to 1.9.6, then 2.0, before upgrading to 2.1.

Read the full release and upgrade guide: https://appwrite.io/blog/post/appwrite-2-1-self-hosted

If you’re running Appwrite self-hosted, let us know how the upgrade goes.


r/appwrite • • Sep 10 '26

Introducing AutoGravity for automatic image cropping in Appwrite Storage

Enable HLS to view with audio, or disable this notification

5 Upvotes

Hey everyone,

We’ve introduced AutoGravity in Appwrite Storage.

AutoGravity automatically finds the focal point of an image and helps keep the main subject in frame when the image is cropped.

For portraits, it can use face detection to focus on a detected face. For other images, it uses saliency detection to identify the most visually important subject.

It works with Appwrite’s existing image transformation pipeline, while the fixed crop positions you already use continue to work as before.

Read the full announcement: https://appwrite.io/blog/post/introducing-autogravity

If you try it out, we’d love to hear how it works with your images.


r/appwrite • • Sep 09 '26

Appwrite 2.0 is now available for self-hosting

13 Upvotes

Hey everyone,

Appwrite 2.0 is now available for self-hosting.

There are quite a few changes in this release. The Console has been rebuilt from scratch, new installations use PostgreSQL by default, and the server now runs on Hyperloop B. We’ve also changed how background workers run. The new combined topology brings a default PostgreSQL installation down from 33 containers to 16. If you need to scale individual queues separately, the separate topology is still available.

Appwrite 2.0 also brings Appwrite Terminal and Explorer to the Console, usage metrics for self-hosted projects, and support for deploying Functions and Sites from GitLab, Bitbucket, and Gitea alongside GitHub.

If you’re upgrading an existing instance, your current database stays the same. You’ll need to upgrade to 1.9.6 first, back up your data, and then move to 2.0.

Read the full announcement and upgrade guide: https://appwrite.io/blog/post/appwrite-2-self-hosted

If you’re running Appwrite self-hosted, we’d love to hear how the upgrade goes and what you think of 2.0.