Yes, the Ory Permission Language (OPL) is supported in self-hosted solutions. The Ory Permission Language is part of Ory Keto, which is the open-source project that powers Ory Permissions. According to the [Ory Keto documentation](https://www.ory.sh/docs/keto), Ory Permissions is based on the open-source Ory Keto Permission Server. This means that when you self-host Ory Keto, you have access to the Ory Permission Language functionality. However, it's important to note that while the core functionality is available in the self-hosted version, some features and conveniences might be exclusive to the Ory Network (the commercial offering). For example, the [Ory Console](https://www.ory.sh/docs/keto) for easy configuration of permission rules through a user interface is mentioned as part of the Ory Network. When self-hosting, you would typically configure the Ory Permission Language rules directly in your configuration files or through the API, rather than using a graphical interface like the Ory Console. If you're considering self-hosting, keep in mind that you'll be responsible for setting up, maintaining, and securing your own infrastructure, as outlined in the [Ory Network or self-hosted comparison](https://www.ory.sh/blog/ory-network-or-self-hosting-explained-use-cases/).

I apologize for any confusion in my previous answer. Let me clarify this for you. You can indeed apply the Ory Permission Language (OPL) to your local, self-hosted Keto instance. The OPL is a core feature of Ory Keto, which is available both in the Ory Network and in self-hosted deployments. According to the [Ory Keto documentation](https://www.ory.sh/docs/keto), Ory Keto is the open-source implementation that powers Ory Permissions, and it includes the Ory Permission Language functionality. For self-hosted solutions, you can configure and apply OPL to your local Keto instance. The [Ory CLI documentation](https://www.ory.sh/docs/guides/cli/configure-permission-service) provides instructions on how to work with Ory Permissions configuration, including exporting and importing configurations. This can be particularly useful when moving between local setups and Ory Network, or when testing different settings in your local development environment. Here's an example of how you can export a configuration from Ory Network and apply it to your local Keto instance: 1. Export the configuration:

ory get permission-config --project <project-id> --workspace <workspace-id> --format yaml > permission-config.yaml

2. Use this configuration file with your self-hosted Keto instance. Additionally, you can create and edit OPL rules directly in your configuration files for your local Keto instance. So, to answer your question directly: Yes, it is possible to apply OPL to your local, self-hosted Keto instance. The OPL is an integral part of Keto, regardless of whether you're using Ory Network or self-hosting.

To use the generated

permission-config.yaml

in your local Ory Keto instance, you can follow these steps: 1. First, ensure that you have exported the configuration from Ory Network as mentioned in the [Ory CLI documentation](https://www.ory.sh/docs/guides/cli/configure-permission-service):

ory get permission-config --project <project-id> --workspace <workspace-id> --format yaml > permission-config.yaml

2. Once you have the

permission-config.yaml

file, you need to incorporate it into your local Keto configuration. According to the [Keto configuration documentation](https://www.ory.sh/docs/keto/reference/configuration), Keto can load configuration from a file using the

-c

or

--config

flag. 3. Rename your

permission-config.yaml

to

keto.yaml

or whatever name you prefer for your Keto configuration file. 4. Start your local Keto instance with the configuration file:

keto serve -c path/to/keto.yaml

Replace

path/to/keto.yaml

with the actual path to your configuration file. 5. Keto will now use the permissions configuration you exported from Ory Network. It's important to note that the exported configuration might need some adjustments to work in a self-hosted environment. For example, you might need to modify database connection strings or other environment-specific settings. Also, keep in mind that Keto supports various configuration formats including JSON, YAML, and TOML. You can choose the format that best suits your needs. If you need to make changes to the configuration, you can edit the YAML file directly. For more advanced usage and configuration options, refer to the [Keto configuration reference](https://www.ory.sh/docs/keto/reference/configuration). Remember that when self-hosting, you're responsible for managing the configuration and ensuring it's properly set up for your environment.