# Overview

> Explore how to self-host Opik on your infrastructure with full feature access, including tracing and evaluation, without user management.

You can use Opik through [Comet's Managed Cloud offering](https://comet.com/site) or you can self-host Opik on your own infrastructure. When choosing to self-host Opik, you get access to all Opik features including tracing, evaluation, etc but without user management features.

If you choose to self-host Opik, you can choose between two deployment options:

1. [Local installation](/self-host/local_deployment): Perfect to get started but not production-ready.
2. [Kubernetes installation](/self-host/kubernetes): Production ready Opik platform that runs on a Kubernetes cluster.

## Getting started

If you would like to try out Opik locally, we recommend using our Local installation
script. Assuming you have `git` and `docker` installed, you can get started with
just one line of code:

<Tabs>
  <Tab value="Linux / Mac" title="Linux / Mac">
    ```bash
    # Clone the Opik repository
    git clone https://github.com/comet-ml/opik.git

    # Navigate to the opik folder

    cd opik

    # Start the Opik platform

    ./opik.sh

    ```
  </Tab>

  <Tab value="Windows" title="Windows">
    ```powershell
    # Clone the Opik repository
    git clone https://github.com/comet-ml/opik.git

    # Navigate to the opik folder
    cd opik

    # Start the Opik platform
    powershell -ExecutionPolicy ByPass -c ".\opik.ps1"
    ```
  </Tab>
</Tabs>

Opik will now be available at

<a href="http://localhost:5173" target="_blank">
  [http://localhost:5173](http://localhost:5173)
</a>

and all traces logged from your local machine will be logged to this local Opik instance. In order for traces and other data
to be logged to your Opik instance, you need to make sure that the Opik Python SDK is configured to point to the Opik server
you just started. You can do this by running the following command:

```bash