What Escher Is For
Context for what kinds of problems Escher addresses — and how it sits relative to the rest of the Tessell portfolio.
Escher's domain
Escher is the agentic reasoning layer for cloud operations. It works on the questions that fall between dashboards and engineers — the ones that today eat an afternoon, a Slack thread, and three console tabs:
- Why did our cloud bill spike?
- Are we ready for a SOC 2 audit?
- What changed before this incident?
- Who has admin access in production right now?
- Where's our biggest waste / posture risk / compliance gap?
The common thread: a question whose answer requires reading across multiple cloud accounts, correlating signals, and producing evidence — not just dashboards or alerts.
How to think about scope
Escher works well when:
- The question has a definite answer that lives somewhere in your cloud configuration, billing, IAM, or events
- You want that answer with citations rather than a directional dashboard
- A senior engineer could in principle answer it — given enough time
Escher works less well when:
- The question requires real-time / live-streaming data (Escher reasons over a recent map, not a live event firehose)
- The answer requires custom code Escher hasn't been taught (it can compose what it knows; it doesn't invent capabilities)
- The question is purely subjective ("is our architecture good?") — Escher can describe the estate but it's not a strategy consultant
Where Escher sits relative to Tessell
INFO
Escher is one product in the Tessell portfolio. It is not Tessell's database / data-management product. Conversations about provisioning databases, managing replicas, or tuning DB performance belong elsewhere in Tessell — Escher reasons across your cloud estate, including how databases are configured and accessed, but it isn't the system that operates them.
If a question is fundamentally about what's happening across your cloud — cost, security, compliance, IAM, reliability, ops — Escher is the right place.
If a question is fundamentally about running a specific database workload — backup orchestration, snapshot scheduling, replica failover — that's another Tessell product.
The two products coexist cleanly. Escher's Data Ops skill (Advanced) reasons about database posture from the cloud's perspective; the database-management product runs the database itself.
We're deliberately not seeding a use-case list
Customers find Escher most useful for whichever questions are most painful in their environment. We've seen FinOps shops use it almost entirely for cost; security teams use it almost entirely for posture; platform teams use it across all seven skills.
Rather than tell you what to use it for, this page is here to tell you what kind of tool it is. Bring your hardest cloud question and try it — that's the most reliable way to find out where it fits for you.
What's next
- How Escher Works — the mental model
- Asking Questions — phrasing tips
- Skills Overview — the seven domains