Unvibe / investor brief
Engineering understanding
for the AI-written codebase.
Unvibe is the engineering knowledge layer for AI-assisted teams. It helps developers understand changes now—and helps organizations preserve what their engineers learn for later.
GitHub stores the code. Unvibe stores the understanding.

The category
AI made code creation abundant. Understanding is becoming scarce.
Faster implementation does not remove the need to review, explain, maintain, and transfer ownership. It increases it. The more code teams produce with AI, the more engineering knowledge can disappear into chats, pull requests, and individual memory.
Unvibe starts with the developer at the moment of change, then turns verified understanding into an organizational asset.
Personal understanding
Select code in any app, receive a context-aware explanation, test your understanding, and save the learning.
Team memory
Connect explanations to pull requests, decisions, concepts, and projects so knowledge survives beyond one person.
Knowledge intelligence
Give engineering leaders a quiet view of knowledge gaps, ownership risk, onboarding progress, and AI-heavy change.
What works now
A personal product with a natural path into teams.
The private beta already captures the core behavior: explain selected code in context, choose the right depth, ask a follow-up, test understanding, and keep a local record. That individual loop becomes the source material for team memory.
- Desktop overlay beside Cursor, VS Code, and other apps
- Five explanation levels, from New to Expert
- Follow-up questions and a lightweight comprehension check
- Secret filtering before any remote request
- Local history, concepts, progress, and saved explanations

Teams intelligence / roadmap
Measure knowledge risk without measuring people.
The B2B product is designed around simple, explainable signals—not employee scoring or surveillance. Founding pilots will shape which views create enough operational value to earn repeat use.
Where understanding is strong, missing, or concentrated
What changed, why it changed, and who verified it
Durable explanations tied to code and decisions
Simple, explainable signals for ownership and resilience
The concepts and decisions a new engineer needs next
Answers grounded in a team’s verified knowledge
Product in ninety seconds
A brief look at Unvibe in the editor.
Select code, get a streamed explanation with project context, then keep what you learned. Full Cursor walkthrough is on the homepage.
Operating support
Useful runway, stated plainly.
Startup-program subscriptions and credits reduce operating costs. They are not cash and are not presented as a funding round.
- Largest program line
- $144,000
- Program credits
- $231,900
- Cash committed
- $800
Founder
Building for ownership, not more generation.
Preston Susanto is a technical founder and EECS student building Unvibe from the product layer through distribution. The near-term company focus is design partners, retained product use, and evidence of paid B2B demand.
What we are proving next
Customer evidence over startup optics.
- 01
Habit Developers return because understanding compounds.
- 02
Team pull Engineering leaders ask for shared knowledge and risk views.
- 03
Willingness to pay Founding pilots convert operational value into paid usage.
Mac and Windows private beta · 30 explanations
v0.1.11
Apple silicon. 30 AI explanations, then it stops. No API key.
Paste in Terminal on an Apple silicon Mac (M1–M4).
$curl -fsSL https://unvibe.site/install.sh | bashInstall, open Unvibe, then select code and press ⌘U. After 30 explanations, the feedback form unlocks 1 week of Pro.
https://unvibe.site/feedback