Hyper

June 24, 2026

Public disclaimer: This is an independent public teardown based solely on publicly available information retrieved on 2026-06-24. It is research support, not investment, legal, tax, or financial advice. Company-provided statements are labeled as claims, not verified facts. Hyper did not participate in or review this report. Errors and omissions are possible; final decisions remain with the reader.

Every AI coding agent forgets. Hyper's pitch is that your company should not have to keep reminding it. One always-on memory layer, the company says, can feed Claude, Cursor, and Codex the same institutional context a senior engineer carries in their head. Two Berkeley builders shipped it inside a single Y Combinator batch and say teams are already paying. The category they are chasing is one of the most contested corners of AI right now, and the upside, if the context truly compounds, is the kind no single model vendor could rebuild from inside its own walls. But the entire investment case turns on one fact the company has not put on the table, and a far larger, better-funded competitor already got curtailed for getting that fact wrong. Read the teardown before the first call turns batch momentum into conviction.

What The Company Does

Hyper markets a "self-driving company brain" for AI coding agents: an always-on memory layer that ingests a team's communications, documents, and developer tools, resolves them into a single organizational context, and feeds that context into agents such as Claude, Cursor, and Codex through the Model Context Protocol, plus automations and a developer-machine hook (Hyper homepage; Hyper FAQ) company claim. The company positions itself explicitly as neither an enterprise search tool like Glean nor a personal or session memory store like Mem0, but as invisible context infrastructure that agents act through (Hyper FAQ) company claim.

The buyer and user, on the company's own pages, are small AI-forward teams, founders, and engineering groups; the product is distributed where agentic coding already happens rather than sold top-down (Hyper homepage; Y Combinator profile) company claim. Pricing is a token-based utility model with a short trial and seat tiers shown on the pricing page; there is no public enterprise price list (Hyper pricing) company claim.

The operating legal entity named on the company's policies is The Soda Machine Co. (Hyper terms; Hyper privacy policy) source-backed fact for the entity name on company-controlled pages. The company is a Y Combinator Spring 2026 (P26) member (Y Combinator profile) source-backed fact. Every revenue, customer, and performance figure below the product description is reported by the company and is not independently corroborated.

Key Takeaways

Investor reaction
Hyper earns a first call because the prize is genuinely large and the two-person team ships fast, but the public record makes the case unusually dependent on claims the company has not validated outside its own surfaces, and its flagship connectors collide with platform terms that already curtailed a far larger peer.
Current verdict
hold with medium confidence. The right action is one time-boxed, proof-gated founder call, not a check and not an open-ended watch.
Why investors might lean in
Hyper is an MCP-native context layer timed to mainstream agentic coding, with a plausible path to becoming the cross-tool context system of record across a company's agent fleet, a substrate that, if it compounds, no single model or IDE vendor can rebuild from inside its own walls.
Why investors might pull back
Effectively all traction is company-reported and partly self-contradicted; the flagship Slack and Gmail connectors run into primary-source platform terms; an identical same-batch competitor exists; and founder build depth for the hardest system is unverified.
Highest-leverage fix
Produce one package that pairs a compliant, ideally first-party and portable connector data-flow architecture with an independently verifiable revenue-and-retention bridge on real paying teams.
Best next move
Take a single, time-boxed first call contingent on that proof package, with a pre-committed pass-by date of 2026-09-24.

What Makes This Potentially Fundable

The fundable version of Hyper is not a better memory widget. It is the persistent cross-tool context system of record across a company's agent fleet: a customer-fed, portable organizational-context graph that sits above any single connector, accrues proprietary context as more agents depend on it, and raises switching costs over time. On that read, the recent wave of platform-data restrictions stops being only a risk and becomes a barrier to entry that favors a layer companies deliberately feed and own.

The attraction is real because the category ceiling is real. Analyst coverage treats enterprise AI search and the agent-memory layer as a forming category (Gartner Market Guide for Enterprise AI Search) source-backed fact for category recognition, and the broader AI-platforms software market is forecast on a path toward roughly $153 billion by 2028 (IDC via HPCwire) inference when applied to Hyper's narrower slice. Those figures size the prize, not Hyper's claim on it.

The honest gap is equally large. There is no independent evidence that any compounding context asset is accruing, that the memory is at or above state-of-the-art, or that the connectors are compliant and portable. Until retention on paying teams and a portable capture architecture exist, the upside is a category option, not an underwritten company outcome.

The Four Holes To Close Before Fundraising

Hole	Investor Fear	What To Bring
The flagship Slack and Gmail connectors may conflict with platform terms as designed.	The product's most differentiating surface depends on the discretion of a hostile platform that can revoke access.	A compliant or first-party data-flow architecture, a Slack or Salesforce partner-or-exemption status, and a Google security-assessment status.
Effectively all traction is company-reported and partly self-contradicted.	Revenue and validation cannot be underwritten, and the inconsistencies read as careless.	An independent revenue-and-retention bridge, a seat ledger, cohort retention, and named customer references.
There is no independent evidence the context asset compounds.	The product reads as a feature, not a fund-returning substrate.	Cohort retention or net revenue retention showing stickiness rises with account tenure.
Founder build depth for org-scale memory infrastructure is unverified.	A two-person team may not be able to build and operate the technical core.	Manager and colleague references plus one verifiable shipped retrieval or infrastructure artifact for each founder.

Decision Snapshot

One-sentence company description: Hyper is a Y Combinator Spring 2026 startup building an org-wide memory and context layer that feeds AI coding agents through the Model Context Protocol.
Screen: hold.
Confidence: medium.
Suggested next action: One tightly scoped founder call, pre-committed to kill criteria, gated on a pre-supplied proof package covering connector compliance, paying-customer retention, and founder build verification.
Why this matters now: Agentic coding is going mainstream while platforms are tightening data-access terms, so the window to verify a compliant, compounding context layer is open but narrowing.
Investor-readiness diagnosis: Hyper has enough category and team signal to earn a call, but not enough independent proof to earn diligence momentum or a check.
Best founder use of this report: Treat it as a proof-package checklist before investor enthusiasm turns into a connector-compliance, revenue, and founder-history interrogation.

IC Disagreement Map

The evidence was reviewed independently across five partner lenses working from the same public record: the power-law lens tested fund-returning upside, the prepared-mind lens tested category timing and product insight, the founder-jockey lens tested team fit and execution, the risk-reduction lens tested critical flaws and value capture, and the long-horizon lens tested portfolio fit and durability.

Power-law partner
holdmedium confidence
The category ceiling is large enough that a reflexive pass would risk an omission error, but no independent evidence shows the context asset compounding, so this is a staged option rather than a check.
Would flip on
An independent retention or agent-dependency cohort plus a connector-agnostic architecture that degrades gracefully without Slack would move them toward pursue; confirmation that the graph collapses when a connector is removed would move them toward pass.
Prepared-mind partner
holdmedium confidence
The timing is live, but the thesis is generic, an identical same-batch peer exists, and the state-of-the-art memory claim has no independent evaluation.
Would flip on
Usage and retention split by surface showing that removing Hyper breaks agent workflows, plus a named evaluation-backed insight, would move them toward pursue; a generic restatement of the company-brain pitch would move them toward pass.
Founder-jockey partner
holdmedium confidence
The early-builder history and unusually aggressive founder-led go-to-market are corroborated, but the load-bearing claims about senior autonomy and machine-learning roles are entirely uncorroborated.
Would flip on
Manager or colleague references confirming the prior roles plus one verifiable shipped retrieval or infrastructure artifact each would move them toward pursue; an inability to name scope or colleagues would move them toward pass.
Risk-reduction partner
holdmedium-high confidence
No single flaw is confirmed fatal, but the Slack and Gmail platform-terms conflict on a fully company-claimed traction base means the cheap, decisive tests must precede any deep diligence time.
Would flip on
A compliant or partnered connector path would move them toward pursue; confirmation that the flagship connectors persistently store and process platform data with no exemption and no fallback would move them to a fast pass on hostile-platform dependence.
Long-horizon partner
holdmedium confidence
Portfolio fit is clean and no fatal flaw is confirmed, but the long-horizon case rests on a compounding asset that shows no accrual and is built on actively restricted platform data flows.
Would flip on
Evidence that core capture is first-party and portable, corroborated net revenue retention, and a fundable instrument with meaningful ownership would move them toward pursue; confirmation that capture depends on restricted re-indexing with no fallback would move them toward pass.

After the committee's evidence-request round, no partner changed their vote and all five remained at hold; the risk-reduction partner raised confidence from medium to medium-high because the platform-terms gap remained documented and unanswered, which is a move toward higher conviction on the same verdict. The agreement is evidential rather than social: the partners reviewed the evidence independently before reading each other, and five different lenses dead-ended on the same small set of company-controlled evidence gaps for different reasons, while their interpretive disagreements about whether platform restrictions are a kill path or a future moat remain live and unresolved.

Scenario Range

Scenario	What The Company Looks Like In 3-5 Years	Falsifiable Trigger To Watch	Earliest Evidence
Strikeout	A thin code-and-documents context wrapper or an acqui-hire; the flagship connectors are stripped or redesigned away, usage collapses to the launch cohort, and a vendor-native memory feature absorbs the rest.	The Slack and Gmail integrations are confirmed to persistently store and process platform data with no exemption and no compliant fallback, while cohort retention runs near zero past 60 to 90 days.	A connector data-flow showing non-compliant ingestion with no fallback, or a billing cohort that is predominantly free or trial.
Base	A useful but bounded org-context tool for small AI-forward teams, with modest paid retention and a capped-revenue or strategic-acquisition outcome rather than a substrate.	Net revenue retention stays roughly flat with small contract values, connectors are compliant only on a subset, and usage concentrates in code and documents rather than cross-tool context.	A revenue-and-retention bridge showing small but real paying cohorts and partner status on some but not all connectors.
Home run	The persistent cross-tool context system of record across companies' agent fleets, with a customer-fed, portable context graph that compounds switching costs and an action layer agents cannot operate without.	Cohort retention and agent dependency rise with account tenure independent of signups, the architecture degrades gracefully without Slack, and net revenue retention runs meaningfully above 100 percent on real paying teams.	Independent retention curves trending up with tenure, an architecture showing first-party portable capture, and at least one design partner treating Hyper as a non-removable system of record.

What Investors Will Test

What We Looked For	Current Read	Investor Implication	Founder Prep Priority
Independent proof outside the company's own surfaces.	The Y Combinator membership and the founders' early-builder history have external support; revenue, customer, memory-quality, and retention claims do not.	The first call should be a proof test, not a narrative pitch.	Bring billing, retention, connector-compliance, and reference evidence a skeptic can route and verify.
A fund-returning path rather than a large-market claim.	Public figures show the category can be large, but there is no evidence Hyper captures a compounding share.	Investors will not underwrite a category denominator as a company outcome.	Show the named home-run mechanism and the metric that would prove the context asset compounds.
Founder-market fit on the hardest build.	Early-builder DNA is corroborated; the senior autonomy and machine-learning scope behind the hardest build is not.	Team quality is a real lean-in factor but does not yet clear technical diligence.	Document prior shipped systems, scope, and colleagues at the prior employers.
Compliant, durable value capture above the platform layer.	The flagship connectors collide with documented platform terms, and durable take-rate above the model layer is unproven.	A non-compliant or easily absorbed layer caps the outcome regardless of team or market.	Bring the connector data-flow, partner or exemption status, and the security-assessment status.

Claim Reconciliation: Inconsistencies Investors Will Catch

Claim Or Metric	Where It Appears	Conflicting / Unreconciled Versions	Why Investors Flag It	How To Reconcile
Launch ranking.	Y Combinator profile Hacker News launch Product Hunt launch post	The company describes a top-of-leaderboard launch, while the observed Hacker News thread showed 79 points and the Product Hunt post showed 15 upvotes with zero reviews.	A self-contradicted headline metric reads as careless and lowers trust in every other narrative number.	Show dated leaderboard screenshots, or restate the launch outcome in the actual observed figures.
Connectors "available now" versus platform terms.	Hyper pricing Hyper FAQ Slack API Terms Google API Services User Data Policy	The company lists Slack and Gmail connectors as live, while the platforms' own terms restrict the persistent-store-and-model-use pattern those connectors imply.	Investors will check the terms, and a live connector built on revocable access is an existence risk.	Provide the per-connector data-flow, the legal basis, and the partner, exemption, or security-assessment status.
Security posture.	Hyper FAQ Hyper privacy policy	The pages assert AES-256 encryption, per-workspace scoping, and a CASA Tier 2 status, but no third-party attestation, SOC 2, or public security-assessment listing was found.	Enterprise procurement treats unverified security prose as a red flag, not a credential.	Provide the attestation, the data-processing agreement, the subprocessor list, and the assessment listing.
Founder prior roles.	Y Combinator profile Shalin Shah LinkedIn Kanyes Thaker LinkedIn	The accelerator bios describe senior autonomy and machine-learning roles, while the founders' public employment histories were empty in the profile data.	A diligence team cannot verify the hardest-build credentials from the public record.	Provide references, dates, scope, and shipped artifacts for the prior roles.

Diligence Findings: Issues To Fix Before You Raise

1 deal-breaker3 high3 medium

The flagship Slack and Gmail connectors may persistently store and model-process platform data in conflict with the platforms' terms, with no public exemption or fallback.
deal-breaker if confirmed non-compliant with no fallback.
Legal, technical, and platform diligence.
Fix
Provide a compliant or first-party data-flow, a partner or exemption status, and a security-assessment status.
Effectively all traction is company-reported, and the launch ranking is self-contradicted.
high
Commercial and financial diligence.
Fix
Provide a revenue bridge, a seat ledger, cohort retention, and named references.
There is no independent evidence the org-context asset compounds.
high
Product and commercial diligence.
Fix
Provide cohort retention or net revenue retention rising with account tenure.
Founder senior scope on the hardest build is unverified.
high
Team diligence.
Fix
Provide references, dates, scope, and a shipped artifact for each founder.
An identical same-batch competitor exists with the same pitch and integrations.
medium
Market and strategy diligence.
Fix
Provide a demonstrable data, retention, or distribution lead and a named insight.
Enterprise security and compliance are aspirational, with no attestation and access control on the roadmap.
medium
Security and procurement diligence.
Fix
Provide an attestation plan, a data-processing agreement, a subprocessor list, and a shipped access-control model.
Round terms, total raised, and ownership are not public.
medium
Financing diligence.
Fix
Provide the instrument, cap table, runway, and hiring plan.

Data Room Readiness Checklist

Procurement-readiness score: not ready.
Rationale: Hyper holds sensitive cross-tool company data, so a buyer's gatekeepers will demand a data-processing agreement, a security attestation, a subprocessor list, and access controls; the public record shows security prose and a roadmap rather than executed artifacts, and the connector-compliance question is unresolved.

Data Room Area	What Investors Expect	Current Read	Status	Priority
Company overview & corporate	One-pager, incorporation, good standing, structure	The Soda Machine Co. is named on legal pages, and Y Combinator membership is public (Hyper terms; Y Combinator profile).	partial	High
Financials	Monthly profit and loss, three-year model, burn, runway	No public financials, burn, or runway; only a company-reported revenue figure.	missing	High
Cap table & funding history	Clean cap table, prior rounds, SAFEs or notes, valuation	A Y Combinator SAFE is implied but no securities filing was found and terms are not public.	missing	High
Legal & IP	Bylaws, consents, intellectual-property assignments, material contracts	Terms and privacy pages exist; assignments, contracts, and connector legal basis are not public.	partial	High
Product & technology	Roadmap, architecture, security and compliance docs	Product claims and a security narrative exist; no architecture, attestation, or connector data-flow is public.	partial	Critical
Team	Org chart, key employment and advisor agreements, vesting	Two founders are public; no org chart, agreements, or vesting are visible, and senior prior scope is unverified.	partial	High
Customers & traction	Retention cohorts, revenue bridge, pipeline, references	No customer-controlled evidence; revenue and pilots are company-reported.	missing	Critical
Market & competition	Market model, competitive landscape, pricing	Category and competitor evidence is strong; Hyper's served-market and unit economics are not public.	partial	Medium

First-Call Agenda For The Startup

Time	Topic	Founder Goal	Evidence To Bring
0-10 minutes	Frame the durable asset.	Make clear whether the moat is the cross-tool context graph or the individual connectors.	An architecture map and a plain statement of what survives if Slack is removed.
10-25 minutes	Connector compliance.	Prove the flagship connectors can legally and durably exist.	A per-connector data-flow, the legal basis, and a partner, exemption, or security-assessment status.
25-40 minutes	Revenue and retention.	Convert traction from narrative into evidence.	A revenue bridge, a seat ledger, and cohort retention separating paid from trial.
40-50 minutes	Founder build depth.	Show the hardest system has a capable owner.	References, scope, and one shipped retrieval or infrastructure artifact each.
50-60 minutes	Differentiation and terms.	Distinguish from the same-batch peer and size the bet.	A named non-obvious insight, an evaluation or usage lead, and round terms.

Business Model And Revenue Signals

Token-based utility pricing with seat tiers and a short trial.
Company-controlled pricing page.high
SourceHyper pricing
List pricing only; no enterprise price is public.
Roughly $1,000 in monthly recurring revenue and 50 or more teams onboarded.
Accelerator narrative.low
SourceY Combinator profile
No billing, seat ledger, or retention; not underwritable.
Paid pilots with named enterprises.
Accelerator narrative.low
SourceY Combinator profile
No statement of work or customer confirmation found.

Public revenue and profit are not available; the company's revenue figure is a company claim and is treated as an estimate, not a fact.

Revenue Quality Checklist

Before this can move from hold to pursue, the company should be ready to show net monthly recurring revenue, paid-versus-trial seat counts, 60- and 90-day cohort retention, account concentration, and unit economics. Investors will rebuild customer acquisition cost, lifetime value, payback, gross revenue retention, net revenue retention, and churn from raw billing data, and those numbers must tie out across the pricing model, the seat ledger, and any data-room documents.

Funding And Ownership Context

Item	Public Read	Evidence Label	Diligence Request
Total raised / rounds	A Y Combinator SAFE is implied by batch membership; no amount or round is public.	`company claim`	Provide the round map and total raised.
Instruments (equity / SAFE / notes)	Not publicly disclosed.	`unknown`	Provide the instrument and conversion terms.
Investors	Y Combinator is the only publicly evidenced backer.	`source-backed fact` for membership.	Provide the full investor schedule.
Post-money valuation	Not publicly disclosed.	`unknown`	Provide valuation and available allocation.
Cap table / ownership	Not publicly disclosed.	`unknown`	Provide the fully diluted cap table and founder vesting.
Burn & runway	Not publicly disclosed.	`unknown`	Provide monthly burn, cash, and runway.
Next-round plan	Not publicly disclosed.	`unknown`	Provide the financing plan and expected round size.

The Securities and Exchange Commission's EDGAR system was checked for a Form D under Hyper, heyhyper, Shalin Shah, and The Soda Machine Co. and showed no matching filing. This absence does not disprove a Y Combinator SAFE, but it means public financing records do not support ownership or valuation modeling.

Founder And Team

Shalin Shah
CEO and co-founder; independently traceable early-builder history and a listed patent.
Shalin Shah LinkedIn Shalin Shah on X Business Insider, 2013
Evidencesource-backed fact for identity and early history.
Confidencehigh
Kanyes Thaker
President and co-founder; active founder-led go-to-market and prior student products.
Kanyes Thaker LinkedIn Kanyes Thaker on X
Evidencesource-backed fact for identity; company claim for prior scope.
Confidencehigh for identity, low for scope
Two-person team
Both founders are listed on the company page; no additional public employees were found.
Hyper on LinkedIn
Evidencesource-backed fact for the public roster.
Confidencemedium
Prior employer
Matic Robots exists as an independent robotics company.
Matic Robots
Evidencesource-backed fact for existence only.
Confidencehigh

Founder Competency Coverage

Domain depth
Shalin Shah
evidenced
Kanyes Thaker
claimed
What The Evidence Is
A listed patent and technical launch-thread replies corroborate Shalin's depth; Kanyes's depth rests on the accelerator bio and self-narrated activity.
Technical build capability
Shalin Shah
evidenced
Kanyes Thaker
claimed
What The Evidence Is
Shalin has an independent patent and early-builder press; Kanyes's projects are self-reported with no public repositories.
Product
Shalin Shah
claimed
Kanyes Thaker
claimed
What The Evidence Is
Product taste is asserted on company-controlled pages for both founders.
GTM / sales
Shalin Shah
absent
Kanyes Thaker
claimed
What The Evidence Is
No independent sales trace for Shalin; Kanyes's go-to-market hustle is self-narrated.
Leadership / hiring
Shalin Shah
claimed
Kanyes Thaker
claimed
What The Evidence Is
Leadership claims rest on accelerator bios with no third-party confirmation.
Fundraising history
Shalin Shah
evidenced
Kanyes Thaker
evidenced
What The Evidence Is
Y Combinator membership is an independent fundraising trace for both.
Prior founding outcomes
Shalin Shah
claimed
Kanyes Thaker
claimed
What The Evidence Is
Prior product and user-count outcomes are self-reported and not registry-verified.

Org-scale memory and retrieval infrastructure at production quality.
high
Team coverage today
Claimed through prior autonomy and machine-learning roles, but no senior scope is independently verified.
What would close it
References, scope, and one shipped comparable retrieval or infrastructure artifact each.
Multi-source ingestion and cross-tool conflict resolution.
high
Team coverage today
Described by the founders, with no independent usage or architecture evidence.
What would close it
An architecture walkthrough and evidence of live, compliant connectors.
Enterprise security and compliance.
high
Team coverage today
Not covered; security is prose and access control is on the roadmap.
What would close it
An executed data-processing agreement, an attestation plan, and a shipped access-control model.
Enterprise go-to-market.
medium
Team coverage today
Founder-led hustle is visible; an enterprise motion is not evidenced.
What would close it
Named, contracted design partners and account ownership.

Public Professional Footprint

These checks of public technical artifacts, professional social presence, and education and credential traces carry low decision weight by design; they corroborate or weaken the coverage table above and sharpen founder-call questions, but none alone changes the verdict.

Technical artifacts (repo level)
Shalin Shah
absent
Kanyes Thaker
absent
What The Public Record Shows
No public code repository was confidently tied to either founder; the listed patent is in a non-Hyper health-tech domain.
Professional social content
Shalin Shah
evidenced
Kanyes Thaker
evidenced
What The Public Record Shows
Both founders post substantively; the launch-thread replies are technical, and the go-to-market anecdotes are founder-authored, so their traction claims are self-origin and repetition is not validation.
Education / credentials
Shalin Shah
evidenced
Kanyes Thaker
evidenced
What The Public Record Shows
Both list a University of California, Berkeley affiliation around 2017 to 2021; the affiliation is traceable, but degree-field completion is not independently confirmed.
Publications / patents / certifications
Shalin Shah
evidenced
Kanyes Thaker
absent
What The Public Record Shows
Shalin lists one patent; no comparable artifact was found for Kanyes.

Net read: the footprint supports a first call because the early-builder DNA is real, but it leaves the verdict gated, because the public record does not prove the senior org-scale build credentials the hardest system requires.

Founder-Market Fit Read

What is promising: A corroborated decade of building, a granted patent, a real prior autonomy employer, and unusually aggressive founder-led go-to-market for a two-person team.
What is missing: Independent verification of senior scope at the prior employers and any public technical artifact for the hardest build.
What to prepare: References, dates, scope, shipped artifacts, and a representative architecture walkthrough.

The Soda Machine Co.
Operating legal entity named on Hyper's policies.
Hyper terms Hyper privacy policy
Evidencesource-backed fact for the entity name on company pages.
Confidencehigh
Follow-upConfirm incorporation and structure privately.
Matic Robots
Prior employer cited for both founders.
Matic Robots
Evidencesource-backed fact for existence; company claim for founder roles.
Confidencehigh for existence
Follow-upConfirm titles, dates, and scope through references.

Traction

Customer Status Table

Razorpay
Named as a paid design pilot on the accelerator profile (Y Combinator profile).
No.Claim onlyUnknownUnknownUnknownhigh that the only evidence is company-reported.
Snorkel AI
Named as a paid design pilot on the accelerator profile (Y Combinator profile).
No.Claim onlyUnknownUnknownUnknownhigh that the only evidence is company-reported.
"50 or more teams"
Aggregate onboarding figure on the accelerator profile (Y Combinator profile).
No.Claim onlyUnknownUnknownUnknownhigh that no customer-controlled evidence exists.

Company case-study pages and the Product Hunt listing were checked and showed no customer-controlled reference or review; the Product Hunt product showed zero reviews at capture. These absences mean no named customer can currently be corroborated outside the company's own materials.

Traction Signals

Launch thread showed 79 points and 76 comments.
source-backed facthigh
SourceHacker News launch
Whether engagement converted to retained usage.
Product Hunt product is live with 143 followers and zero reviews.
source-backed facthigh
SourceProduct Hunt product
Whether followers convert to paying teams.
Product Hunt launch post showed 15 upvotes.
source-backed factmedium
SourceProduct Hunt launch post
Independent daily-leaderboard placement.

GitHub organization and Securities and Exchange Commission Form D checks returned no public developer organization and no filing. These absences carry little weight on their own for an early-stage company, but they remove two common independent traction and financing proxies.

Hiring And Org Momentum

Public roster
source-backed fact for the public rosterOnly the two founders appear on the company page; no additional public employees were found.
SourceHyper on LinkedIn
The team reads as a two-person founding team with no evidenced senior hires for the hardest build or enterprise distribution.

Indeed, Glassdoor, LinkedIn Jobs, and the company careers page were checked and showed no matching open postings. These absences carry little weight since early teams hire informally and job boards are often incomplete, and employee sentiment remains unavailable.

Role-mix read: No public hiring signal; the company appears to be operating as a two-person team.
Momentum read (growth / steady / contraction / unknown): unknown, because there is no public hiring or headcount-growth signal.

Traction Quality Read

Traction Dimension	Current Status	Good Enough For First Call?	Needed For Deep Diligence
Launch engagement	Real but modest on community and marketplace channels.	Yes, as context, not as conviction.	Evidence the engagement converted to retained usage.
Customer proof	Company-reported only; no customer-controlled evidence.	Only if the call is gated on resolving it.	Routable references and a revenue-and-retention bridge.
Technical proof	Memory-quality claims with no public evaluation.	Only as a question.	A reproducible evaluation against baselines.
Team signal	Strong early-builder DNA; senior scope unverified.	Yes.	Verified scope and a shipped artifact each.
Revenue quality	Not independently available.	No.	Billing, retention, and concentration data.

Competitive Landscape

Segment	Examples	Customer Alternative	Pressure On Company
Direct same-batch peer	Memory Store.	Adopt a near-identical company-brain memory layer.	A peer with the same pitch and integrations can copy faster than Hyper distributes.
Agent-memory infrastructure	Mem0, Zep, Cognee.	Build on a developer-first memory API or open-source graph memory.	These set the price and developer-pull bar for the memory layer.
Enterprise work-AI incumbents	Glean, Microsoft 365 Copilot with Work IQ, Notion AI.	Use an incumbent that already holds the company's data.	Incumbents can bundle native memory and own the buyer relationship.
Adjacent and substitute	Slashy and manual retrieval stacks.	Use an inbox-memory tool or build context in-house.	These compete for overlapping context budgets.

Category Visibility Snapshot

Google Search / United States"company knowledge AI enterprise search Glean Notion AI Microsoft Copilot memory Mem0 Zep"

Captured page-one results (2026-06-24): Glean's own pages dominated the retrieved results, with Microsoft and Notion appearing indirectly through listicles.
Was the company present?: No.

Google Search / United States"AI agent memory layer Mem0 Zep Cognee company brain"

Captured page-one results (2026-06-24): Mem0, Zep, and Cognee appeared, alongside community and listicle domains.
Was the company present?: No.

Google Search / United States"company brain AI agents shared memory MCP"

Captured page-one results (2026-06-24): Generic blog, community, and informational domains appeared, with no named startup in the top results.
Was the company present?: No.

Google Search / United States"Hyper AI company brain YC"

Captured page-one results (2026-06-24): Hyper and Y Combinator surfaces appeared for the branded query.
Was the company present?: Yes.

Visibility read (inference, low confidence): Hyper has branded visibility but does not appear for generic category queries, where incumbents and the funded memory-infrastructure cohort own the page. A captured AI-assistant snapshot likewise described Hyper as a "promising emerging" option rather than placing it in its final ranking. Visibility is not market share; this is a low-confidence distribution read.

Pricing And Competitive Benchmark

Alternative	What It Offers	Public Price Signal	Price Vs. This Company	Evidence Label
Mem0	Developer-first memory API and SDK.	Free hobby tier, then roughly $19, $79, and $249 per month (Mem0 pricing).	Different model; Hyper sells token utility pricing rather than developer tiers.	`company claim`
Zep	Enterprise agent memory with context graphs.	Flex plan around $104 per month billed annually (Zep pricing).	Hyper's token model is not directly comparable without a usage profile.	`company claim`
Microsoft 365 Copilot	Native AI and memory inside the Microsoft stack.	Business tier around $18 per user per month (Microsoft 365 Copilot pricing).	An incumbent bundle that may satisfy buyers without a third-party layer.	`company claim`
Notion AI	Workspace AI, agents, and enterprise search.	Free tier plus paid plans (Notion AI).	A workspace substitute for teams that already live in Notion.	`company claim`
Slashy	Inbox memory and drafting.	Around $25 per user per month (Slashy).	Adjacent on email context, not a team agent brain.	`company claim`
Glean	Enterprise work-AI search and agents.	Demo-led enterprise pricing with no public self-serve price.	A different motion and buyer; no comparable list price.	`company claim`

Price positioning read: Hyper's token utility model is hard to benchmark against seat- and credit-based competitors without a usage profile, so total cost at 5-, 20-, and 100-person teams is a diligence gap.
Price claims to correct or substantiate: Any claim that token pricing is cheaper at team scale should be tied to a usage export at named seat counts.

Competitive Wedge

The defensible wedge, if it exists, is a customer-fed, portable cross-tool context graph plus an action and execution layer agents operate through, both harder for a read-only vendor memory feature to absorb. Today, both remain company claims, while the incumbent and same-batch-peer pressure and the platform-terms exposure are supported by public evidence.

Risks And Open Questions

Risk	Severity	Evidence	What To Ask
The flagship Slack and Gmail connectors depend on hostile-platform discretion.	high	Platform terms restrict the persistent-store-and-model-use pattern (Slack API Terms; Google API Services User Data Policy), and a larger peer was curtailed (Hunton analysis).	Show the compliant or first-party data-flow and the partner, exemption, or security-assessment status.
Effectively all traction is company-reported and partly self-contradicted.	high	Revenue and pilots are company narrative (Y Combinator profile); the launch ranking conflicts with observed counts.	Show a revenue bridge, a seat ledger, and cohort retention.
There is no evidence the context asset compounds.	high	No retention or accrual data is public.	Show cohort retention rising with account tenure.
Founder build depth for the hardest system is unverified.	medium	Identity and early history are traceable; senior scope is not.	Show references and a shipped artifact each.
A model or IDE vendor ships native cross-tool memory.	medium	Incumbents are extending native memory (Microsoft Annual Report 2025).	Show a defensible non-overlapping wedge that survives native memory.

Pre-Mortem: The Most Likely Obituary

Cause of death (one sentence): Hyper died when platform enforcement forced its flagship Slack and Gmail connectors into a redesign, collapsing the company brain back to a thin code-and-documents layer that a vendor-native memory feature then absorbed, before any compounding context asset had independently formed.
The causal chain (3-5 steps from today to the shutdown): Investors accept the staged-option framing and skip the cheap connector-compliance test; the company keeps re-indexing Slack and Gmail because that ingestion is what makes the product more than a code tool; platform enforcement tightens and the persistent-store model loses its feeds; the "compounding graph" turns out to have been the connectors, so usage drops and thin retention is exposed; a vendor or the same-batch peer ships good-enough native memory and the two-person team cannot out-build or out-distribute it.
The earliest observable warning sign: On the first call, the connector-compliance question is answered with privacy-policy language and no partner status or architecture, so the cheapest test comes back evasive rather than documented.
The question that defuses this chain today: Show the per-connector data-flow proving capture is first-party and portable, and show the product still works with Slack removed, answered before a check rather than after.

Decision-Critical Unknowns

Unknown	Why It Is Decision-Critical	Best Evidence	Decision Effect
Connector compliance and portability.	It determines whether the flagship surface can durably exist.	A per-connector data-flow, partner or exemption status, and a security-assessment status.	A compliant or first-party path would support advancing; confirmed non-compliance with no fallback would move the decision toward pass.
Independent revenue and retention.	It is the difference between real traction and launch optics.	A revenue bridge, a seat ledger, and a cohort curve.	A paying, retained cohort would support advancing; predominantly free or trial usage would move the decision toward pass.
Founder senior build scope.	The hardest system cannot rest on early-builder history alone.	References and a shipped artifact each.	Verified scope would support founder-market fit; an inability to name scope would move the decision toward pass.
Whether the moat is the graph or the connectors.	It determines whether the asset survives a connector loss.	An architecture showing portable, customer-fed context spanning tools.	A separable graph would strengthen the case; collapse on connector loss would move the decision toward pass.

Diligence Questions

First Call

Question	Why It Matters	Good Evidence
Show the per-connector Slack and Gmail data-flow and the partner, exemption, or security-assessment basis.	It is the cheapest near-fatal test.	A compliant or first-party data-flow and a partner or assessment status.
How many teams pay, what is net monthly recurring revenue, and what is 60- and 90-day cohort retention for paying versus trial seats?	The entire traction case is company-reported.	A billing bridge, a seat ledger, and a cohort curve.
What did each founder personally own at Matic Robots and Snorkel AI?	Founder-market fit on the hardest build is unverified.	References, scope, and a shipped artifact each.
Is the durable asset the context graph or the connectors, and does the product degrade gracefully without Slack?	It separates a substrate from a feature.	A portable architecture and usage surviving a connector loss.

Follow-Up

Question	Why It Matters	Good Evidence
What is the one non-obvious insight, and is it the memory store or the action layer?	A near-identical peer exists.	A specific mechanism plus an evaluation or workflow-dependency proof.
What independently distinguishes Hyper from Memory Store?	An indistinguishable position signals a feature race.	A demonstrable data, retention, or distribution lead.
At what step is the developer-machine hook disclosed and consented, and is it removable?	A silent install is a trust and procurement risk.	A consented flow, a hook specification, and an uninstall path.
What are the SAFE terms, total raised, runway, and ownership available at entry?	Ownership math sizes the bet.	The instrument, cap table, runway, and hiring plan.

Kill Criteria

Kill Criterion	Evidence That Would Trigger It
The flagship connectors are confirmed to persistently store and model-process platform data with no exemption and no compliant fallback.	A founder data-flow showing non-compliant ingestion with no fallback.
Traction is confirmed predominantly free or trial with no expansion.	A billing cohort that is predominantly non-paying.
Founders cannot evidence the hard build and references collapse.	An inability to name scope, projects, or colleagues, with no shipped artifact.
A model or IDE vendor ships native cross-tool org-memory good enough to make the layer redundant.	A vendor native-memory shipping announcement covering cross-tool context.
No founder call with the proof package occurs by 2026-09-24.	The pass-by date passes without the call and package.

Double-Down Criteria

Double-Down Criterion	Evidence That Would Justify More Diligence
A compliant or first-party, portable connector architecture is shown.	A data-flow that survives a single-connector loss plus partner or assessment status.
Independent retention rises with account tenure.	A cohort or net-revenue-retention curve on real paying teams.
Founder senior scope verifies.	References plus one shipped comparable artifact each.
A named, evaluation-backed insight distinguishes Hyper from the peer.	A specific mechanism with usage or evaluation support.

Founder Action Plan

Timeframe	Action	Output
Before the next investor call (by 2026-09-24)	Build a per-connector Slack, Gmail, and Drive data-flow showing storage, indexing, and model use plus the legal basis, and obtain partner, exemption, or security-assessment status.	A compliance and architecture one-pager.
Before the next investor call (by 2026-09-24)	Export a revenue-and-retention bridge separating paying from trial seats, and line up named customer references.	A verifiable traction package.
Early diligence	Arrange manager and colleague references for the prior employers and assemble one shipped retrieval or infrastructure artifact each.	A founder-market-fit evidence pack.
Early diligence	Run or publish a reproducible memory evaluation against baselines and document the one non-obvious insight.	An evaluation and insight memo.
Before a broader raise	Ship access control and isolation, execute a data-processing agreement and subprocessor list, and open a security-attestation engagement; publish the hook specification and uninstall path.	An enterprise-readiness and trust package.

Decision

Screen: hold.
Confidence: medium.
Rationale: The upside is large, no single flaw is confirmed fatal, and the team ships fast, but every load-bearing input is company-reported, the flagship connectors collide with documented platform terms, and there is no independent proof the context asset compounds.
What would move this to pursue: A compliant or first-party portable connector architecture that survives a single-connector loss, an independent billing-verified cohort showing retention rising with tenure, and verified founder scope with one shipped comparable artifact.
What would move this to pass: Any one confirmed fatal flaw, including non-compliant flagship connectors with no fallback, traction confirmed predominantly free or trial, founders unable to evidence the hard build, a vendor shipping native cross-tool org-memory, or no founder call with the proof package by 2026-09-24.
Recommended next step: A single, time-boxed first call contingent on the proof package, with a pre-committed pass-by date.
Founder preparation standard: Bring evidence a skeptical investor can route, verify, and model, not additional batch or category framing.

How We Would Miss This One

The miss scenario: Hyper could be the case where capture is genuinely first-party and portable, the context graph quietly compounds on real paying teams, and the founders' build depth verifies just after cautious investors step away, leaving the default agent-memory layer to a faster-moving competitor.
Flip conditions: A first-party, portable architecture surviving a connector loss; an independent retention curve rising with tenure; and verified founder scope with a shipped artifact would flip the case toward pursue.
Revisit trigger / date: Revisit by 2026-09-24, or immediately if the company produces the connector-compliance, retention, or founder-history evidence.

Source Log

Hyper homepage
heyhyper.ai
Positioning, product workflow, and integrations.
Retrieved 2026-06-24company-controlled pagehigh
Hyper pricing
heyhyper.ai
Token utility pricing, seat tiers, and listed integrations.
Retrieved 2026-06-24company-controlled pagehigh
Hyper FAQ
heyhyper.ai
Product mechanics, security narrative, and competitive framing.
Retrieved 2026-06-24company-controlled pagehigh
Hyper privacy policy
heyhyper.ai
Data-handling claims, entity name, and data-protection gaps.
Retrieved 2026-06-24company-controlled legal pagehigh
Hyper terms of service
heyhyper.ai
Operating entity, governing law, and data license.
Retrieved 2026-06-24company-controlled legal pagehigh
Y Combinator profile
ycombinator.com
Founder identity, batch membership, and company-reported traction.
Retrieved 2026-06-24accelerator page (Y Combinator)high for membership, low for metrics
Y Combinator launch
ycombinator.com
Launch narrative and product framing.
Retrieved 2026-06-24accelerator page (Y Combinator)medium
Hacker News launch
news.ycombinator.com
Launch engagement counts and founder replies.
Retrieved 2026-06-24community forum (Hacker News)high
Product Hunt product
producthunt.com
Product Hunt presence, followers, and zero reviews.
Retrieved 2026-06-24marketplace page (Product Hunt)high
Product Hunt launch post
producthunt.com
Launch-post upvotes.
Retrieved 2026-06-24marketplace page (Product Hunt)medium
Hyper on LinkedIn
linkedin.com
Public roster and founder posts.
Retrieved 2026-06-24public profile dataset (LinkedIn)medium
Shalin Shah LinkedIn
linkedin.com
Founder identity, education, and patent.
Retrieved 2026-06-24public profile dataset (LinkedIn)high
Kanyes Thaker LinkedIn
linkedin.com
Founder identity, education, and projects.
Retrieved 2026-06-24public profile dataset (LinkedIn)high
Shalin Shah on X
x.com
Founder public bio and affiliations.
Retrieved 2026-06-24public profile dataset (X)medium
Kanyes Thaker on X
x.com
Founder public bio and affiliations.
Retrieved 2026-06-24public profile dataset (X)medium
Matic Robots
linkedin.com
Existence of the prior employer.
Retrieved 2026-06-24public profile dataset (LinkedIn)high
Business Insider, 2013
businessinsider.com
Early-builder history of a founder.
Retrieved 2026-06-24business press (Business Insider)high
Slack API Terms of Service
slack.com
Platform restrictions on persistent storage and third-party model use of Slack data.
Retrieved 2026-06-24platform terms (Slack)high
Slack API terms update
docs.slack.dev
Confirmation of updated data-access and storage terms.
Retrieved 2026-06-24platform documentation (Slack)high
Google API Services User Data Policy
developers.google.com
Restricted-scope security-assessment requirement for Google user data.
Retrieved 2026-06-24platform policy (Google)high
Hunton analysis
hunton.com
Plain-language analysis of Slack data restrictions and the larger-peer precedent.
Retrieved 2026-06-24legal-update analysis (Hunton)medium
Memory Store
memory.store
Direct same-batch peer positioning and integrations.
Retrieved 2026-06-24competitor pagehigh
Memory Store on Y Combinator
ycombinator.com
Same-batch peer membership and framing.
Retrieved 2026-06-24accelerator page (Y Combinator)high
Mem0 homepage
mem0.ai
Memory-infrastructure positioning and developer-count claim.
Retrieved 2026-06-24competitor pagemedium
Mem0 pricing
mem0.ai
Published memory-API pricing tiers.
Retrieved 2026-06-24competitor pagehigh
Zep homepage
getzep.com
Enterprise agent-memory positioning.
Retrieved 2026-06-24competitor pagehigh
Zep pricing
getzep.com
Credit-based pricing anchor.
Retrieved 2026-06-24competitor pagehigh
Cognee homepage
cognee.ai
Open-source graph-memory positioning.
Retrieved 2026-06-24competitor pagemedium
Glean homepage
glean.com
Enterprise work-AI incumbent positioning.
Retrieved 2026-06-24competitor pagehigh
Notion AI
notion.com
Workspace-AI substitute positioning.
Retrieved 2026-06-24competitor pagehigh
Microsoft 365 Copilot pricing
microsoft.com
Incumbent seat-price anchor.
Retrieved 2026-06-24vendor pricing page (Microsoft)high
Slashy
slashy.com
Adjacent inbox-memory positioning and pricing.
Retrieved 2026-06-24competitor pagehigh
Gartner Market Guide for Enterprise AI Search
gartner.com
Category recognition and formation.
Retrieved 2026-06-24analyst report (Gartner)high
IDC via HPCwire
hpcwire.com
Broad AI-platforms software market forecast.
Retrieved 2026-06-24analyst report via trade press (IDC / HPCwire)medium
Market Research Future enterprise search
marketresearchfuture.com
Narrow adjacent-market directional estimate.
Retrieved 2026-06-24market-sizing aggregator (Market Research Future)low
Mordor Intelligence enterprise search
mordorintelligence.com
Narrow adjacent-market directional estimate.
Retrieved 2026-06-24market-sizing aggregator (Mordor Intelligence)low
Microsoft Annual Report 2025
microsoft.com
Incumbent scale and native-memory comparison.
Retrieved 2026-06-24public-company filing (Microsoft)high
Atlassian 2025 Annual Report
s206.q4cdn.com
Incumbent scale and teamwork-graph AI strategy.
Retrieved 2026-06-24public-company filing (Atlassian)high
Elastic FY2025 Form 10-K
sec.gov
Closest single-product search-AI scale comparator.
Retrieved 2026-06-24public-company filing (SEC)high
ServiceNow 2025 Annual Report
s205.q4cdn.com
Workflow-incumbent scale and AI-agent expansion.
Retrieved 2026-06-24public-company filing (ServiceNow)high
Census Statistics of U.S. Businesses
census.gov
Bottom-up firm denominator source.
Retrieved 2026-06-24government statistics (U.S. Census Bureau)high
Census 2022 SUSB annual data
census.gov
Firm and establishment denominator tables.
Retrieved 2026-06-24government statistics (U.S. Census Bureau)high

Access limitations: Public research could not retrieve Hyper's billing data, cohort retention, customer contracts, the per-connector data-flow and platform partner or exemption status, security attestations, the cap table or round terms, or independent verification of the founders' senior roles at prior employers; the founders' public employment histories were empty in the profile data, and the interactive sanctions and exclusions name searches were not run. Search-result checks and the AI-assistant snapshot were used only to mark gaps and visibility, not as client-safe proof. These limitations mean this report can support a gated first call, but it cannot validate revenue, retention, connector compliance, technical readiness, or customer adoption without founder-provided documents and reference checks.

Public disclaimer: This is an independent public teardown based solely on publicly available information retrieved on 2026-06-24. It is research support, not investment, legal, tax, or financial advice. Company-provided statements are labeled as claims, not verified facts. Hyper did not participate in or review this report. Errors and omissions are possible; final decisions remain with the reader.

What The Company Does#

Key Takeaways#

What Makes This Potentially Fundable#

The Four Holes To Close Before Fundraising#

Decision Snapshot#

IC Disagreement Map#

Scenario Range#

What Investors Will Test#

Claim Reconciliation: Inconsistencies Investors Will Catch#

Diligence Findings: Issues To Fix Before You Raise#

Data Room Readiness Checklist#

First-Call Agenda For The Startup#

Business Model And Revenue Signals#

Revenue Quality Checklist#

Funding And Ownership Context#

Founder, Team, And Related Entities#

Founder And Team#

Founder Competency Coverage#

Public Professional Footprint#

Founder-Market Fit Read#

Related Entities And Founder-Associated Companies#

Traction#

Customer Status Table#

Traction Signals#

Hiring And Org Momentum#

Traction Quality Read#

Competitive Landscape#

Category Visibility Snapshot#

Pricing And Competitive Benchmark#

Competitive Wedge#

Risks And Open Questions#

Pre-Mortem: The Most Likely Obituary#

Decision-Critical Unknowns#

Diligence Questions#

First Call#

Follow-Up#

Kill Criteria#

Double-Down Criteria#

Founder Action Plan#

Decision#

How We Would Miss This One#

Source Log#