Based on the available knowledge sources, it is technically possible to use a self-hosted Ory Keto instance for permission checks while using Ory Network for other services. The Ory Keto SDK and configuration guides explicitly support integration with self-hosted Keto servers, and you can export/import permission configurations between Ory Network and self-hosted Keto using the Ory CLI. This allows you to align your permission models and rules across both environments, which could help you avoid Ory Network's rate limits on permission checks by directing those requests to your self-hosted Keto instance instead [Configure Ory Permissions](https://www.ory.sh/docs/guides/cli/configure-permission-service) [Ory Keto SDK Overview](https://www.ory.sh/docs/keto/sdk/overview). However, the knowledge sources do not provide explicit guidance or official support for this hybrid approach as a recommended or documented solution to rate limiting. There may be operational or architectural considerations (such as consistency, latency, or support boundaries) that are not covered in the documentation. In summary: You can technically mix a self-hosted Ory Keto with Ory Network by syncing configuration and directing permission checks to your self-hosted Keto, but this is not explicitly documented as a supported method for avoiding Ory Network rate limits. Proceed with caution and consider reaching out to Ory support or the community for further guidance.