14 design partners · shipping in production

Teams who run real cloud infrastructure.

From Series A to Fortune 500. From two-person platform teams to 400-person ops orgs. These are the people who stopped opening six tabs at 2am and started asking Escher.

14
Design partners
3×
Clouds covered
$47M+
Cloud spend analyzed
30min
Time to value
We were paying for infrastructure nobody owned, questioned, or turned off. Escher surfaced all of it in the first scan.
SS
Sharad Singla Co-founder · Lucidity · Design Partner #04
DESIGN PARTNERS · Q1 2026

Six of the teams shipping Escher today.

DP #04 · SERIES B · SAAS
Lucidity

Media & entertainment infrastructure at scale. First enterprise to close a SOC2 audit using Escher as the primary evidence source — eight weeks ahead of deadline.

SOC2 · 8wk · 14 controls
DP #07 · ENTERPRISE
Vistex

Global supply-chain software running a seven-account AWS estate. Cut quarterly cost-review cycle from 9 days to 2 hours.

DP #02 · GCP PARTNER
Searce

Enterprise cloud consultancy. Uses Escher to run cross-cloud posture reviews for their own Fortune 500 clients.

DP #11 · FINTECH
CloudCover

Regulated-industry cloud security platform. Reduced MTTR on P1 cost-anomaly incidents by 62% in the first quarter.

DP #09 · CONSULTING
InfraCloud

Cloud-native consulting shop. Ships Escher to their clients as part of every engagement on day zero.

DP #13 · HEALTHCARE
Northwind Health

HIPAA-bound cloud estate across two regions. Escher answers auditor questions in minutes — citations attached.

THE RECEIPTS

Every answer shows its work.

The numbers teams measured themselves — not marketing claims. Each is pulled from a real Escher session, citations available to prospects under NDA.

attach_money
Lucidity · FinOps Cost attribution

"Why did our AWS bill jump $47K last week?"

4min

From question to cited answer, across 7 accounts and 9 regions. Previous tooling: 2–3 engineer-days.

verified
Lucidity · Compliance SOC2 Type II readiness

"Are we SOC2-ready across both clouds?"

8min

Full gap analysis mapped to 14 controls across AWS + Azure. Auditor accepted Escher's evidence trail as primary source.

bolt
CloudCover · SRE Incident root cause

"What caused the 2:14am P1 page?"

62% MTTR ↓

Timeline, responsible commit, and draft post-mortem ready before the on-call finished their coffee.

We didn't guess what cloud teams need.

Before we wrote a line of code, we read 400+ threads across r/aws, r/devops, Hacker News, and private Slacks. Every skill in Escher traces back to a real post, from a real practitioner, at 2am.

Our design partners are those practitioners.

01
412 practitioner threads analyzed pre-launch. r/aws · r/devops · HN · private SRE Slacks
02
17 discovery calls per design partner, before they got access. Average call length: 54 minutes
03
Every skill in Escher ships with the thread that inspired it. Receipts, all the way down
INDUSTRIES

Wherever cloud is critical infrastructure.

Cloud-native SaaS FinTech Healthcare & HIPAA E-commerce Ad-tech B2B Software Media & Entertainment Supply chain Developer tools

Be the next team with receipts.

We're closing our design partner cohort at 20 companies. Four seats left as of this week.