Feedback and Deployment Challenges with FastAPI on Appwrite

Hello world!, I've been developing a project using FastAPI in Python, and I was considering deploying it through Appwrite Functions.

However, I encountered a few challenges during deployment:

• The SDK feels quite limited for complex or large-scale Python projects.
• Type hints are incomplete, making development less predictable in typed environments.
• Hot reload often breaks or becomes unstable during active development.
• Restart times for larger projects can take 1–3 minutes, which significantly slows down iteration.
• Overall, it seems difficult to scale or maintain larger backends within this setup.

I also tried to deploy using a Docker container, but noticed that Appwrite Functions currently don’t seem to support that option either.

Could you please confirm whether there’s a recommended way to deploy a standalone FastAPI app — perhaps via containers or an upcoming feature?

Additionally, I believe Appwrite could greatly benefit from focusing on hosting and orchestration, while letting developers integrate their own frameworks and SDKs. This approach would make the platform more flexible and attractive to developers who already rely on well-established Python ecosystems.

I really appreciate the work you’re doing, and I’d love to keep exploring Appwrite as a backend option — I think it has great potential if it becomes more open and framework-agnostic.

Appwrite functions has a serverless function architecture and requires implementing the interface described in the documentation.

Most people have their client-side apps communicate directly with Appwrite and only use functions for specific business logic they need by having individual functions