# Kgrid External Runtimes
External runtimes allow the knowledge grid to execute code in a native environment by passing the payload from the knowledge object through the proxy adapter to a remote environment that implements the external runtime API.
# Using an external runtime
Activating a knowledge object that depends on an external runtime:
- Start up the activator
- Start a remote runtime pointed to the activator using the property
- The objects that require that remote runtime will be passed to it and activated in that environment.
The runtimes register themselves with the proxy adapter included in the activator and then assume responsibility of handling execution, storage, and communication for the executable portion (payload) of the knowledge object.
# Developing a new remote runtime
The proxy adapter readme (opens new window) documents the API that a remote runtime must interface with. Using this API you can create an environment that uses the common KGrid activator API but executes objects in any given native environment.