Local Development and Debugging
Connect your local service to a remote Kubernetes cluster and test end-to-end flows instantly. No mocking, no image builds, no waiting for CI. You and your teammates can run changes locally and test together.
Trusted by
How It Works
Set up local testing in minutes. Connect to your cluster, define a sandbox, and start testing against real dependencies while collaborating with teammates running their own local changes.
1
Connect to Your Cluster
Run signadot local connect to establish a secure tunnel between your machine and the cluster. Access cluster services via their DNS names locally.
2
Define Your Sandbox
Define a simple YAML config that maps traffic from a remote Kubernetes deployment port to your local service port.
3
Start Your Service Locally
Run your microservice locally using your preferred setup—Docker, IDE, or native execution. Signadot automatically routes cluster traffic to your local instance.
4
Test End-to-End Flows
Select your sandbox using the Chrome extension to test end-to-end flows from your web frontend. Requests with the routing header automatically route to your local workstation.
Common Use Cases
Debug Live Issues
Reproduce and debug staging issues on your local machine with full access to logs, debugger, and breakpoints against live data.
Test Database Migrations
Run schema changes locally while connecting to real downstream services to catch integration issues before deployment.
Cross-Team Development
Frontend developers can test against your local backend changes instantly—no deployments or coordination needed.
Plug Into Your Existing Dev Workflow
Signadot Local Testing works with your existing Kubernetes clusters and integrates seamlessly with your IDE, debugger, and local development tools for fast integration testing.
read docs
