Mercek

What it does

Mercek is a desktop application that provides a unified interface for managing Amazon ECS container services and deployments. It runs locally and connects to AWS accounts using existing credentials stored on the machine. The tool displays clusters, services, and tasks across multiple AWS accounts and regions simultaneously in a single tree view. It tracks deployment rollouts, shows service metrics, estimates costs, provides log tailing, enables shell access to running containers, and builds a dependency graph of services.

Who it is for

The tool targets engineers and operators who manage ECS infrastructure. It addresses the friction of repeatedly switching between the AWS console and Kubernetes management tools like Lens. Teams running ECS across multiple accounts or regions would benefit from the centralized view. Organizations with Fargate workloads may find the cost estimation and right-sizing analysis useful.

Pricing

The site does not show prices.

How it stands out

Mercek emphasizes local execution and data privacy by never storing user data on external servers and running read-only by default until a change is explicitly approved. It integrates directly with AWS credentials already on a machine—including SSO, assume-role, and MFA setups—without requiring a separate authentication layer. The tool pulls metrics from Container Insights with fallback to standard ECS metrics, shows deployment state including circuit breaker status, and provides cost estimates alongside usage metrics on a single screen. It offers interactive shell access to containers via ECS Exec and masks secrets as ARNs in the UI. The project is open source.

What a founder should check

First, assess the competitive landscape: Lens dominates Kubernetes management, but the ECS tooling ecosystem is less consolidated. Verify whether Pulumi, Copilot, or CloudFormation tooling has already captured demand for ECS deployment workflows.

Second, investigate switching costs and the moat. ECS users today move between the AWS console and a mix of CI/CD platforms and infrastructure-as-code tools. Understand whether Mercek's value proposition is sticky enough to become a daily habit, or if users revert to console and scripting for complex operations.

Third, test the actual pain points: How often do engineers really alternate between multiple accounts and regions in a single session? Whether cost estimation alone justifies adoption should be validated with target users.