I had the opportunity to work with Typesense in a setup where the instance was running inside a private Kubernetes cluster. Since the instance wasn’t publicly accessible, the only way to manage Typesense collections was by port-forwarding its service to my local machine and using the default static dashboard tools.

This project aims to eliminate that need for port-forwarding. By leveraging Next.js as a full-stack framework, the dashboard accesses the Typesense instance directly from server components—essentially shifting the "localhost" context to the Kubernetes environment. This allows internal communication with exposed services inside the cluster over the internal K8s DNS.

The dashboard itself is designed to run as a deployment within the same Kubernetes cluster, providing seamless access to the Typesense instance without exposing its port externally.

This was my use case, its however not limited to k8s, the dashboard's image can be deployed anywhere and is available here.

WIP