Mercek Review (2026): Pricing, Features & Honest Verdict

TLDR

Mercek is a free, open-source desktop IDE for Amazon ECS. It uses your existing AWS credentials to show every service across all accounts and regions, with log tailing, container shell access, and a diff-based approval workflow. Best for: DevOps engineers who live in ECS and are tired of the AWS console. Price: free and open source. Rating: 6.9/10.

What is Mercek?

Mercek is a desktop application for working with Amazon ECS, the maker describes it as a local-first IDE for ECS. It uses the AWS credentials already on your machine and shows your services across every account and region in one window. It is read-only until you approve a change, talks to AWS directly with no server in between, and sends no telemetry. The whole thing is open source and free.

It was built by a solo developer (GitHub user utibeabasi6) and launched on Hacker News as “a Desktop IDE for AWS ECS,” explicitly inspired by Lens, the popular Kubernetes desktop tool. The backend is written in Rust and the frontend uses React 19 with TypeScript, packaged with Tauri rather than Electron, which is why it stays light. We dug into the project and the appeal is obvious to anyone who has clicked endlessly through the ECS console: one fast local view of everything you run. A former AWS engineer commenting on the launch summed up the demand, saying they could not count the times they wished someone had built this.

What Are Mercek’s Key Features?

Multi-account, multi-region discovery

Mercek reads your ~/.aws profiles, including SSO, assume-role, MFA, and static keys, and discovers ECS clusters across every account and region you grant it. Scopes are opt-in per profile. The home view shows service health, failed, degraded, deploying, or healthy, across all active scopes, plus a “needs attention” list. For teams juggling several AWS accounts, this single pane is the headline benefit over the console, which forces you to switch accounts and regions constantly.

Live deployment tracking and rollback

The app tracks deployments live and supports rollback, so you can watch a new task definition roll out and reverse it if something breaks. Combined with the diff-based approval workflow, where every infrastructure change is shown as a diff you explicitly approve, this gives you a safer, more deliberate way to ship than firing commands blind. It is read-only by default, which is a sensible guardrail.

Log tailing and container shell access

Mercek tails CloudWatch logs with filtering and highlighting, and it gives you interactive shell access into running containers via ECS Exec. These are the two things engineers do most when debugging, and having them a click away instead of buried in the console or a CLI invocation is the kind of small win that adds up across a day. Performance metrics like CPU, memory, and traffic are available through Container Insights integration.

Cost estimation and Sentinel monitoring

Beyond day-to-day operations, Mercek does cost estimation and right-sizing analysis to flag overprovisioned services, and it has a background “Sentinel” mode that watches for service health anomalies. There is also read-only AI agent integration via the Agent Client Protocol and automatic service dependency mapping. These extras are nice, though as early features they are where you should expect the most rough edges.

Native performance without Electron

One of the most praised aspects on the Hacker News launch was that Mercek is not an Electron app. The backend is Rust and the whole thing is packaged with Tauri, which keeps the memory footprint tiny, one commenter measured just over 30 MB on an M2 MacBook. That matters more than it sounds. Developer tools that sit open all day next to your editor, terminal, and browser quickly add up, and a heavy Electron app that eats hundreds of megabytes is a real annoyance. Mercek staying lightweight means you can leave it running as a dashboard without thinking about it. The non-Electron choice also gives it a snappier, more native feel than many cross-platform tools.

How Much Does Mercek Cost?

Mercek is free. It is open source, with no paid tier, no subscription, and no telemetry collection. You can download a prebuilt binary for macOS (Apple Silicon or Intel) or Linux (.deb or .AppImage), or clone the repository and build it yourself. Windows support is planned but not shipped at the time we looked.

That pricing is hard to argue with, especially against the alternatives. The AWS Management Console is also free but slow and account-scoped. Commercial cloud management suites that cover ECS often run into real money per seat. Mercek gives you a focused, native tool at zero cost, with the source available so you can verify exactly what it does with your credentials, which matters when a tool touches production AWS.

The real cost is not money, it is risk. A free tool from a single maintainer can go quiet, and you are trusting community-maintained code with access to your infrastructure. The open-source code mitigates the trust concern, and the read-only-by-default design limits the blast radius. But factor in the bus-factor before you make it central to your workflow.

There is also a security angle worth thinking through, and it cuts in Mercek’s favor. Because it runs locally, talks to AWS directly with no server in between, and collects no telemetry, your credentials and infrastructure data never pass through a third party. That is a genuinely better posture than many SaaS cloud dashboards, which proxy your AWS access through their own backend. For security-conscious teams, a local, open-source, no-telemetry tool can clear internal review more easily than a hosted product, even if the hosted product is more polished.

Who is Mercek Best For?

Use Mercek if you run containers on Amazon ECS or Fargate and spend meaningful time in the ECS console every week. If you manage services across multiple AWS accounts and regions, the unified view alone can justify installing it. It suits DevOps engineers, backend developers, and small platform teams who want speed without paying for a heavyweight platform.

Skip Mercek if your infrastructure is not on ECS, if you need a tool that covers your whole AWS surface rather than one service, or if you cannot accept depending on early software from a solo developer for production work. Teams on Kubernetes should look at Lens instead, and Windows users have to wait.

• Good fit: ECS and Fargate users, multi-account AWS setups, console-fatigued engineers
• Poor fit: non-ECS workloads, Windows-only teams, organizations needing vendor support guarantees

The sweet spot is a startup or small platform team that has standardized on ECS and Fargate and feels the pain of the console every single day. For them the unified, multi-account view is not a nice-to-have, it is a daily time saver, and the zero price plus open-source transparency make it an easy tool to adopt without a procurement process. Larger enterprises with strict vendor requirements will struggle to justify a solo-maintained project for production, even though the code being open mitigates much of that concern.

Best Mercek Alternatives

e1s

e1s is a terminal-based ECS manager that several Hacker News commenters mentioned alongside Mercek. It lives in your terminal rather than a GUI, which some engineers prefer, and it is also free and open source. Mercek’s advantage is visual debugging across clusters and a friendlier interface, but if you are a keyboard-first terminal person, e1s may suit you better.

Lens

Lens is the desktop IDE for Kubernetes that directly inspired Mercek. If your workloads run on EKS or any Kubernetes cluster rather than plain ECS, Lens is the mature, polished equivalent, with a large user base and a personal tier that is free. It does not manage ECS, so it is an alternative only in the sense of being the right tool for a different orchestrator.

AWS Management Console

The AWS Console is the official, free, built-in way to manage ECS. It covers every AWS service, not just ECS, and needs no install. The downside is exactly what Mercek fixes: it is slow, it scopes you to one account and region at a time, and routine tasks take many clicks. If you only touch ECS occasionally, the console is fine and you may not need Mercek at all.

Final Verdict: Is Mercek Worth It?

Mercek is a sharp, well-targeted tool. For anyone who manages Amazon ECS daily, a fast, local, native app that shows every service across accounts and regions, tails logs, and drops you into a container shell is a clear upgrade over the AWS console. It is free, open source, lightweight thanks to Rust and Tauri, and built with sensible guardrails like read-only-by-default and diff-based approvals. The demand for exactly this has been obvious for years.

The 6.9 reflects the caveats rather than the quality of the idea. It is early-stage, ECS-only, maintained by one developer, and missing a Windows build. Those are real limits for teams that need broad coverage and guaranteed support. Our recommendation: if you live in ECS, install it today, it costs nothing and will likely save you time immediately. Just keep your CLI and console skills sharp and do not make a solo-maintained tool the single point of failure for production changes.