Built so you can read every line of code.

Krewva is an AI agent crew that handles your messages — across iMessage, WhatsApp, Gmail, Slack, Calendar, Drive — so you live your life. Drafts wait for your nod. Nothing is sent without your approval.

Read the founder manifesto

Why we built it

Knowledge workers spend twelve-plus hours a week inside inboxes. Most of that volume is routine: scheduling, status, acknowledgments, a one-line confirmation that didn't need full attention. The replies are predictable, but the context-switching cost is enormous — every ping fragments a working hour.

Existing AI tools sit in another tab. They expect you to copy a thread out, paste a draft back in, and reconcile the two yourself. That isn't relief; that's another job. Krewva runs natively inside the inboxes you already use, drafts where the work lives, and waits for you to approve.

We don't believe AI should sit in another tab — it should live where the work already is.

What we hold to

Drafts wait for your nod

Agents draft. You approve. Nothing auto-sends until you've personally taught the system who and what to trust. Autonomy is earned, not assumed.

Your data isn't training fuel

Krewva makes money from subscriptions, not data sales. Your messages are never sold, brokered, or fed into a model that serves another customer.

Capability over personality

We build functions — Messaging, Finance, Research, Safety — not character names that change with marketing winds. Capabilities outlast brand refreshes.

Work where you already work

Krewva lives inside iMessage and Gmail and Slack. We don't ask you to switch apps, paste threads into a chatbot, or learn a new surface.

The team

Krewva is built by a small, opinionated team. The two founders below write or review every line of production code.

Zeming Liang

Founder & CEO

Full-stack engineer who burned out replying to messages 3 hours a day. Started building Krewva because no AI assistant actually closed the loop on his inbox. Wuvov Inc. founder, Krewva product lead. Based in NYC.

Haiyang Wu

CTO & Co-founder

Built Krewva's backend and connector runtime. 14 years shipping production systems. Believes in local-first architecture and slow-cooked code.

We're a small team. By design.

Small teams ship faster, keep the product opinionated, and answer their own support tickets. We don't plan to grow headcount past what the product actually needs.

We're hiring engineers and designers. If this product solves a problem you have, you'll know what to build. hiring@krewva.com

Why we're building Krewva now

A few independent shifts collided in 2024, and the window opened. The first: language models finally cleared the bar for drafting in someone's actual voice. Pre-trained baselines learned to mimic register, vocabulary, and rhythm well enough that a 200-message history could pin a draft to "this sounds like me" rather than "this sounds like a chatbot." That capability didn't exist a year earlier.

The second: the model-tax problem cracked open. DeepSeek's reasoning models and the Llama family pushed inference cost down by an order of magnitude, which means an agent crew that drafts on every inbound message stops being a luxury budget item and starts being viable for a $20/mo subscription. Krewva needs cheap inference to exist.

The third: chat apps fragmented past the point any single human can manage by hand. iMessage, WhatsApp, Slack, Gmail, Instagram DMs, Discord, Telegram, Signal — the average knowledge worker is in seven inboxes simultaneously, none of which talk to each other. The mental overhead alone is a tax. A unified queue across all of them is the only sane response.

The fourth: the trust dial finally became feasible. Programmable autonomy ladders — auto-reply for grandma, draft-only for the boss, never-reply for spam — require a substrate that can hold per-contact rules without leaking them across apps. That substrate is what we've been building. The combination of all four is what makes 2026 the right year for an inbox-native AI workforce, not 2022 and not 2030.

Where we're headed

Tied to our internal PRDs (docs/product development roadmap/). We only list what's actually scoped.

  1. Done ToC

    v0 — Visual design foundation

    Decision-card feed, platform-color moat, bottom-sheet pattern, 8 card types. The interaction contract every later release builds against.

  2. Now ToC

    v1 — Krewva Life on iOS + macOS

    Echo (messages + email) and Aria (child safety) across WhatsApp, iMessage, Instagram DMs, and Gmail. Gesture model (scroll, swipe, tap). Auto-generated voice profile from your own chat history.

  3. Next BOTH

    v2 — Life context + Biz office

    Krewva Life expands the unified agent across more personal apps. Krewva Biz deepens the 3D office, department-agent pending stacks, and Drive-backed operating context.

  4. Soon ToC

    v3 — Digital Twin Studio

    Edit your persona and tone files, see exactly which lines drove a draft, and watch the system learn from your approvals and corrections — with your sign-off on every change.

  5. Soon ToC

    v4 — Autonomy + Memory + Decision Log

    Per-contact rule buckets (Auto-reply / Needs approval / Cannot reply), a writable Memory Vault for the crew, and a full audit trail of every prompt and every agent action — exportable, user-owned.

  6. Future ToC

    v5 — Finn (money agent)

    Banking, subscriptions, credit cards, insurance, shopping, splitting — all in the same swipe model. Money actions are deliberately gated until the autonomy and memory layers are live.

  7. Future BOTH

    v6 — Security safeguards

    Tool-call permissions, Memory Vault file guards, and AI-powered prompt-injection detection across every connected source. Underpins regulated-industry use of both Life and Biz.

  8. Target Target

    Security review packet

    Documented controls, retention policy, and audit exports for business customers. Target only — not yet externally certified.

ToC = consumer / Krewva Life. BOTH = applies to Life and Krewva Biz. Target = security posture documentation, not an external certification claim. Versions ship in order — each release is hard-gated on the previous one's exit criteria.

Backed by

We're actively fundraising. Below is a placeholder grid for the backers we're in conversation with — we'll fill in real names when terms close.

  • Tier-1 fund In conversation
  • Tier-1 fund In conversation
  • Family office In conversation
  • Angel syndicate In conversation

"We use Krewva ourselves before charging anyone. The dogfood test."

— Zeming Liang, founder

Where we're based · Join us

Krewva is built by a remote team across NYC and Bangalore. We collaborate asynchronously, ship daily, and meet in person twice a year for product sprints.

We're not running an open careers page yet — hiring is small, deliberate, and founder-led. If you're a senior engineer, designer, or operator who wants to ship consumer AI with us, send an email with what you've built and what you want to build next.

Wuvov Inc. is a Delaware C-corp. #wuvov-inc on Linear. careers@krewva.com See /careers for future tracks.

Get in touch

We answer every email — usually within a day.

Press kit

Brand assets

Logos, color tokens, typography, and screenshot bundles for editorial use.

Open brand kit

Press inquiries

Quotes, embargoed previews, and product walkthroughs.

press@krewva.com

Founder availability

Zeming is available for podcast and press conversations.

zeming@wuvov.com

Recent press

First feature coming soon.