1. Deployment Method: Hasura provides a hosted service for easy deployment, while PostGraphile and Prisma need to be self-hosted.
2. Data Sources: Hasura supports multiple data sources like SQL databases, GraphQL APIs, and REST endpoints out of the box, whereas PostGraphile and Prisma primarily work with SQL databases.
3. Real-time capabilities: Hasura has built-in support for real-time GraphQL subscriptions, while PostGraphile and Prisma require additional setup for real-time data updates.
4. Permissions and Authorization: Hasura has a robust Role-Based Access Control (RBAC) system for configuring permissions at a granular level, whereas PostGraphile and Prisma require more manual configuration for access control.
5. Automatic Schema Stitching: PostGraphile has automatic schema stitching capabilities that allow for combining multiple GraphQL schemas easily, which is not available in Hasura and Prisma.
6. Community and Documentation: Prisma has a comprehensive and well-maintained documentation, while Hasura and PostGraphile may lack extensive community support and documentation.

In Summary, Hasura, PostGraphile, and Prisma have differences in deployment methods, data sources, real-time capabilities, permissions and authorization, automatic schema stitching, and community support and documentation.