> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/feature-management-experimentation/new-to-fme/sdks-and-customer-deployed-components/customer-deployed-components.md). # Customer-deployed Components Learn about the Harness FME components you can deploy within your own environment, including the Split Daemon, Evaluator, Proxy, and Synchronizer. ## Overview Customer-deployed components allow you to run parts of the Harness FME infrastructure within your own environment. This gives you more control over data flow, network latency, and compliance by hosting core services locally or in your private cloud. By deploying one or more of these components, you can: * Meet strict data residency or security requirements * Reduce latency by keeping evaluation close to your users or services * Integrate FME into custom delivery architectures or service meshes * Manage SDK connections and feature flag evaluations without direct client-to-cloud communication ## Run the Split Evaluator, Split Proxy, or Split Synchronizer with Kubernetes Harness FME provides three containerized applications that can be run on your own infrastructure. These apps can handle specific use cases for feature flagging and experimentation with our SDKs and APIs. Go to the [Kubernetes and Split blog post](https://www.harness.io/blog/kubernetes-and-split) for architectural diagrams and sample configuration files to run the Split Evaluator, Split Proxy, and Split Synchronizer in Kubernetes. ## Get started Select a component you want to deploy.
Split Daemon (splitd)Split Daemon (splitd)
Split EvaluatorSplit Evaluator
Split ProxySplit Proxy
Split SynchronizerSplit Synchronizer
Split JavaScript Synchronizer ToolsSplit JavaScript synchronizer tools
Split Synchronizer runbookSplit Synchronizer runbook
Harness ProxyHarness Proxy
{% @harness-feedback/feedback %}