Appwrite shipped managed Postgres and MySQL (real engines, not our document API)
Appwrite shipped managed Postgres and MySQL, according to a DEV Community post titled "Appwrite shipped managed Postgres and MySQL (real engines, not our document API)." The title explicitly separates the new managed relational database services from Appwrite's document API, indicating that the offering uses the actual Postgres and MySQL engines rather than Appwrite's own document data model. The post is published on DEV Community and carries the 418 Challenge article tag. The supplied source text does not include the article body. What follows the title in the provided content is stylesheet code for the 418 Challenge presentation layer, including theme rules for light and dark modes, card borders, typography, and background animations. That code contains no product announcements, engine versions, region availability, pricing, migration tooling, or launch dates. As a result, the only verifiable claims are the two named managed database engines and the stated contrast with Appwrite's document API. Any further specifics about how the managed Postgres and MySQL services are configured, billed, or operated are absent from the source and are not reported here.
Developers using Appwrite can now see managed Postgres and MySQL positioned as real engines separate from its document API, per the source title.